- Newest
- Most votes
- Most comments
Hello,
Did you check the SG and allow the same in the SNS for the new application to access ? Are you using the correct IAM role for the application or Does that IAM role have access to SNS ?
Link- https://docs.aws.amazon.com/sns/latest/dg/sns-authentication-and-access-control.html -- [1]
You can use X-Ray with Amazon SNS to trace and analyze the messages that travel through your application.
Can you please create a separate Security Group for the SNS VPC end-point that allows HTTPS (443) inbound from the security group of the machine where your application is running? Also make sure that the VPC endpoint for SNS is in the correct region. As Chirag has mentioned, I would also make sure IAM permissions allow the role of the application to send SNS messages.
Relevant content
- asked 2 years ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 years ago
Yes, both the web server and the sns vpe endpoint are using the same security group. We do not use xray at this time, maybe that can be another debugging option, though we can see rejected traffic in the Eni vpc flow logs.