1

I am working on serverless architecture using AWS lambda where multiple modules/lambdas communicate via SNS (simple notification service).

Due to compliance requirement that data in transit should be secure and encrypted, do I need to do that manually or SNS natively supports it?

Vipin Goel
  • 21
  • 3

2 Answers2

1

Just came to know that we can enable ssl in all SNS requests by setting sslEnabled flag to true (in case of node sdk). this.sns = new AWS.SNS({ sslEnabled: true });

Vipin Goel
  • 21
  • 3
0

AWS services communication between them are secure by design because happens within the Amazon’s network.

SNS documentation

Amazon SNS provides access control mechanisms to ensure that topics and messages are secured against unauthorized access. Topic owners can set policies for a topic that restrict who can publish or subscribe to a topic. Additionally, topic owners can ensure that notifications are encrypted by specifying that the delivery mechanism must be HTTPS.

Hope it helps

Ele
  • 33,468
  • 7
  • 37
  • 75
  • Additionally, topic owners can ensure that notifications are encrypted by specifying that the delivery mechanism must be HTTPS. - As per my understanding, this is valid only in case of https subscribers. In my case subscriber is a Lambda. – Vipin Goel Jan 11 '18 at 14:58
  • @VipinGoel an invocation from SNS to Lambda is executed through API calls for sure. Those API calls make https requests internally, so your data travels from one service to others encrypted by default. – Ele Jan 11 '18 at 15:11
  • You may be right, but is there any proof to validate this statement. – Vipin Goel Jan 16 '18 at 08:23
  • Just came to know that we can enable ssl in all SNS requests by setting sslEnabled flag to true (in case of node sdk). – Vipin Goel Jan 22 '18 at 07:10