The Guidance for the Identity Management & Access Control (IMAC) capability will help you build and monitor permissions in your environment. This Guidance will help you to structure your organization and organize your resources within defined isolated groups following the principal of least privilege (PoLP). This Guidance will help your team develop a framework to manage your environment and provide access to your services.

Architecture Diagram

Download the architecture diagram PDF 

Implementation Resources

When you are building your environment, access to your platform, your resources, and your applications needs to be established. First to build the environment, and second to operate the environment using the established capabilities and services that you build.

As you structure your environment, you should delegate administrative tasks to different teams and separate responsibilities across different functions. For example, implementing security tooling, managing the network, or creating central repositories.

Access to your environment should be secured to all users, regardless of the function they will be responsible for. Enabling a form of multi-factor authentication (MFA) for every user is a requirement to meet a minimum-security standard.

 Capability Details
  • Name: Identity Management & Access Control (IMAC)
  • Category: Security
 Supporting Capabilities

For additional information on this capability, read the whitepaper.

Disclaimer

The sample code; software libraries; command line tools; proofs of concept; templates; or other related technology (including any of the foregoing that are provided by our personnel) is provided to you as AWS Content under the AWS Customer Agreement, or the relevant written agreement between you and AWS (whichever applies). You should not use this AWS Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the AWS Content, such as sample code, as appropriate for production grade use based on your specific quality control practices and standards. Deploying AWS Content may incur AWS charges for creating or using AWS chargeable resources, such as running Amazon EC2 instances or using Amazon S3 storage.