CloudGuild · Blog · Cheat sheets · Lessons · Certifications
Understanding Encryption in Microservices with AWS API Gateway
Explore a common exam question about securing communications in microservices using AWS API Gateway. Learn why mutual TLS is the right choice.
A company is deploying a microservices architecture on AWS and wants to ensure that communications between services are encrypted. They are considering using Amazon API Gateway. What feature should they use to secure the communications?
A. Enable CORS for the API
B. Use AWS IAM roles for service-to-service communication
C. Implement mutual TLS authentication
D. Use Amazon Cognito for user authentication
Think before you scroll
Consider the specific needs for securing communications between microservices. Focus on encryption and the ability to verify identities in a microservices environment. Each option addresses different aspects of security and communication, so weigh their relevance carefully.
The answer
The correct option is C. Implement mutual TLS authentication. This feature encrypts communications and verifies both client and server identities, ensuring a secure connection between services.
Why the other options lose
A. Enable CORS for the API: CORS (Cross-Origin Resource Sharing) is primarily a browser security feature that allows or restricts web pages from making requests to a different domain. It does not provide encryption for communications between services.
B. Use AWS IAM roles for service-to-service communication: While IAM roles are essential for managing permissions and access control, they do not encrypt communications. IAM roles govern who can access resources but do not secure the data in transit.
D. Use Amazon Cognito for user authentication: Cognito is great for user authentication and managing user identities, but it does not directly secure communications between microservices. It focuses on user-level security rather than service-to-service encryption.
The concept behind it
Mutual TLS (mTLS) authentication is a method where both the client and server authenticate each other using certificates. This process not only encrypts data in transit but also ensures that both parties are legitimate, enhancing overall security in microservices architectures.
Exam trap to remember
Always remember: Encryption for communications requires mutual TLS, not just authentication or access control mechanisms.