bug: Creating secrets using secretManager ignores the region in localstack-pro

[hemachandran-kalaimani]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

When a secret is being created with awslocal in one region, it is always end up creating the secret in the default region.

Command used:

awslocal  \
          --region "us-west-2" \
          secretsmanager create-secret --name "my-secret" \
          --no-verify-ssl \
          --no-sign-request \
          --secret-string 'my-secret-string'

{
     "ARN": "arn:aws:secretsmanager:us-east-1:000000000000:secret:my-secret-SbhQdy",
     "Name": "my-secret",
     "VersionId": "e8c399b2-41e3-4e88-bbf8-e47293e0315d"
 }

Expected Behavior

Creating a secret in a region should result in a secret being created in the same region;

{
     "ARN": "arn:aws:secretsmanager:us-west-2:000000000000:secret:my-secret-SbhQdy",
     "Name": "my-secret",
     "VersionId": "e8c399b2-41e3-4e88-bbf8-e47293e0315d"
 }

How are you starting LocalStack?

With the localstack script

Steps To Reproduce

awslocal
--region "us-west-2"
secretsmanager create-secret --name "my-secret"
--no-verify-ssl
--no-sign-request
--secret-string 'my-secret-string'

Environment

- OS:
- LocalStack:

Anything else?

No response

[localstack-bot]

Welcome to LocalStack! Thanks for reporting your first issue and our team will be working towards fixing the issue for you or reach out for more background information. We recommend joining our Slack Community for real-time help and drop a message to LocalStack Pro Support if you are a Pro user! If you are willing to contribute towards fixing this issue, please have a look at our contributing guidelines and our contributing guide.