AWS Secrets Manager requires AWS_REGION variable to always be present even when region is configured per secret

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Proposal

The AWS Secrets Manager integration recently released in GitLab 18.3 is a great addition for using AWS secrets, but it seems to always require the AWS_REGION variable to be set even if the region field is configured per secret. For example, this job doesn't work:

test-aws-secrets:
  secrets:
    TEST_SECRET:
      aws_secrets_manager:
        secret_id: test-secret
        field: some-field
        region: us-east-2
      file: false

The error it shows on the job failure page is The secrets provider can not be found. Check your CI/CD variables and try again.. To make it work currently, the variable AWS_REGION has to be provided like this:

test-aws-secrets:
  variables:
    AWS_REGION: us-east-2
  secrets:
    TEST_SECRET:
      aws_secrets_manager:
        secret_id: test-secret
        field: some-field
        region: us-east-2
      file: false

It would be nice if the AWS_REGION wasn't required when region is set in the secret configuration, or at least the error message should be updated with wording indicating that the failure is caused by the lack of an AWS_REGION variable being present.