question AWS Credentials working in Sub-Prods but not in Production in Community Central forum

AWS Credentials working in Sub-Prods but not in Production

Anusha Reddy VK — Fri, 24 May 2024 06:43:26 GMT

Hello,

We have a requirement to feed resolved incident data into an AWS SQS queue. This implementation has been successfully tested and working in our Development & Test environments. However, after migrating these changes to our Production environment, we encountered an authorization error.

The specific error message is as follows: "User: anonymous is not authorized to perform: sqs:SendMessage on resource: arn:aws."

We have verified that the same aws credentials were used in both the Development and Production environments.

Could someone please assist us in resolving this authorization issue?

Thanks,
Anusha

Re: AWS Credentials working in Sub-Prods but not in Production

Mark Manders — Fri, 24 May 2024 07:13:50 GMT

Does the integration user on PROD have the same access as on DEV/TEST? Using the same credentials on different instances, doesn't mean they have the same access level.

Re: AWS Credentials working in Sub-Prods but not in Production

Ravi Chandra_K — Fri, 24 May 2024 07:18:54 GMT

Hello @Anusha Reddy VK

Are the ACLs same in all Instances ralated to module you are trying to access to ?you can try resetting the credentials that might resolve this issue.

Please mark this answer as helpful and correct if helped.

Kind Regards,

Ravi Chandra

Re: AWS Credentials working in Sub-Prods but not in Production

Anusha Reddy VK — Fri, 24 May 2024 12:02:05 GMT

@Mark Manders - We have authenticated using Access Key and Secret Key in credentials Table. We have not used any user credentials to authenticate.

Suggest what kind of access levels do I need to check on aws credentials?

Re: AWS Credentials working in Sub-Prods but not in Production

Anusha Reddy VK — Fri, 24 May 2024 12:05:21 GMT

@Ravi Chandra_K - Yes everything is Identical in Prod and Dev as they are recently cloned. Additionally, I have reset the credentials in Prod. Despite these measures, the issue persists.