Multiple Environment Support in AWS SNS SMS

Viewed 519

Our services currently utilize AWS' SNS SMS for sending transactional texts to users (i.e., account confirmation, password resets, etc.). We also have at least two environments--Dev and Production--using the same SNS SMS service since both environments run in the same AWS account and region.

We are working on recording SMS bounce info in our database by ingesting the CloudWatch failure logs via Lambda; however, we have no way of differentiating bounces from Dev for testing purposes vs. legit bounces in Production from users based on those logs.

The goal is to be able to differentiate the bounces by environment so we can properly record them in the respective DBs; however, I am not seeing any way to do that in SNS or CloudWatch other than using separate accounts or potentially other regions.

Is anyone aware of a way to accomplish our goal without having to resort to separate accounts or even regions?

2 Answers

Frankly speaking you have to handle it on your own through code using message ID as stated above by Aws guy.

This is simple use case,I don't understand why AWS can support it.

Related