A company is designing a microservice-based architecture tor a new application on AWS. Each microservice will run on its own set of Amazon EC2 instances. Each microservice will need to interact with…

Question

Options

• AAssign an IAM user to each micro-service. Use access keys stored within the application code to
• BCreate a single IAM role that has permission to access all AWS services. Associate the IAM role
• CUse AWS Organizations to create a separate account for each microservice. Manage
• DCreate individual IAM roles based on the specific needs of each microservice. Associate the IAM

• A
  6% (4)
• B
  13% (9)
• C
  3% (2)
• D
  78% (52)

Explanation

When designing a microservice architecture where each microservice interacts with different AWS services, it's essential to follow the principle of least privilege. This means granting each microservice only the permissions it needs to perform its tasks, reducing the risk of unauthorized access or accidental actions. The recommended approach is to create individualIAM roleswith policies that grant each microservice the specific permissions it requires. Then, these roles should be associated with the EC2 instances that run the corresponding microservice. By doing so, each EC2 instance will assume its specific IAM role, and permissions will be automatically managed by AWS. IAM roles provide temporary credentials via the instance metadata service, eliminating the need to hard-code credentials in your application code, which enhances security.

No community discussion yet for this question.