Mods
AWS

Policy: AWS > Well-Architected Tool > AWS Well-Architected Framework > Security > SEC 02. How do you manage identities for people and machines?

There are two types of identities you need to manage when approaching operating secure AWS workloads. Understanding the type of identity you need to manage and grant access helps you ensure the right identities have access to the right resources under the right conditions. Human Identities: Your administrators, developers, operators, and end users require an identity to access your AWS environments and applications. These are members of your organization, or external users with whom you collaborate, and who interact with your AWS resources via a web browser, client application, or interactive command-line tools. Machine Identities: Your service applications, operational tools, and workloads require an identity to make requests to AWS services - for example, to read data. These identities include machines running in your AWS environment such as Amazon EC2 instances or AWS Lambda functions. You may also manage machine identities for external parties who need access. Additionally, you may also have machines outside of AWS that need access to your AWS environment.

See SEC 02. How do you manage identities for people and machines? for more information.

Resource Types

This policy targets the following resource types:

Primary Policy

This policy is used with the following primary policy:

Controls

Policy Specification

Schema Type
string
Default
Skip
Valid Values [YAML]
  • Skip
    
  • Check: Choices based on sub policies
    
  • Check: None of these
    
  • Check: Question does not apply to this workload
    
  • Enforce: Choices based on sub policies
    
  • Enforce: None of these
    
  • Enforce: Question does not apply to this workload
    
Examples [YAML]
  • Skip
    

Category

In Your Workspace

Developers