Identity Access Management (IAM)

  1. IAM is an AWS service that allows humans and programs to securely access AWS services and infrastructure.
  2. IAM provides very granular control over the resources. You can specify:
    1. Who can access
    2. What resource
    3. Perform what Action on that resource
    4. From where? a specific ip/CIDR
    5. When? At a specific time range.
  3. IAM is not OS level user management tool. For OS level user management use LDAP or Active Directory Services.
  4. AWS is not application level user management tool. For application level user management such as the users that registered on your eCommerce website, use Application User Repositories or in case of Mobile apps, use AWS Cognito.
  5. IAM principal is an IAM entity (human or application) that can access AWS resources. Three types of principals:
    1. Root user
      1. use email/password to access
      2. can use root user keys to access AWS services from applications but strongly NOT recommended
      3. Should enable MFA (Multi Factor Authentication) for better security
    2. IAM users
      1. Can be person or application
      2. Can have userid/password
      3. Can have Security Access Key ID/Secret Access Key combination (ID is 20 char and Secret Access Key is 40 char)
      4. Access Key Rotation for security purposes
        1. Every principal can have two sets of access keys.
        2. You start with one key set
        3. After some time you create a new key set
        4. Keep both old and new key sets active for some time while your programs update your keys.
        5. Later delete old key set.
      5. Can be associated with policies containing permissions to ALLOW/DENY access to specific AWS resources
    3. IAM roles/temporary security tokens
      1. Roles are used to provide specific privileges to specific IAM principals for a set duration (time window) of min 15 min to 36 hours
      2. Following use cases of Roles are important to remember
        1. EC2 roles can be assigned to give access to processes on the EC2 to access AWS resources.
          1. In fact it is a best practice to use the EC2 roles as opposed to using the Access Key (Access ID/Secret Access Key combo) inside the config files or hard coding in side the program code.
          2. Also with this practice, no need to worry about access key rotation which is highly recommended otherwise.
          3. Roles can be changed and policies can be modified without stopping the EC2 instances. New privileges will be effective immediately.
        2. Cross Account Access: Provide access to IAM principals from another account. This is better practice than distributing Access Keys.
        3. Federation:
          1. Users of trusted external systems such as Google/Facebook users can be granted access to AWS resources thru roles and temp security tokens. OpenId Connect (OIDC) protocol is used.
          2. Users of LDAP/Active Directory are federated thru Security Assertion Markup Language (SAML)



<<< Introduction to Amazon Web Services (AWS)IAM Policy >>>
Copyright 2005-2016 KnowledgeHills. Privacy Policy. Contact .