IAM best practices in AWS - Time & Space Complexity

Time Complexity: IAM best practices

O(n)

Understanding Time Complexity

We want to understand how the time to manage permissions grows as we add more users and roles in IAM.

How does the number of permission checks or policy updates change when the system grows?

Scenario Under Consideration

Analyze the time complexity of the following IAM operations.

# Create multiple IAM users
for i in range(1, n+1):
    iam.create_user(UserName=f'user{i}')

# Attach policies to each user
for i in range(1, n+1):
    iam.attach_user_policy(UserName=f'user{i}', PolicyArn='arn:aws:iam::aws:policy/ReadOnlyAccess')

# Check permissions for each user
for i in range(1, n+1):
    iam.simulate_principal_policy(PrincipalArn=f'arn:aws:iam::123456789012:user/user{i}', ActionNames=['s3:GetObject'])
    

This sequence creates users, attaches policies, and checks permissions for each user.

Identify Repeating Operations

• Primary operation: Creating users, attaching policies, and simulating permission checks.
• How many times: Each operation runs once per user, so n times.

How Execution Grows With Input

As you add more users, the number of API calls grows directly with the number of users.

Input Size (n)	Approx. Api Calls/Operations
10	30 (10 create + 10 attach + 10 check)
100	300 (100 create + 100 attach + 100 check)
1000	3000 (1000 create + 1000 attach + 1000 check)

Pattern observation: The total operations increase linearly as the number of users increases.

Final Time Complexity

Time Complexity: O(n)

This means the time to manage IAM users and policies grows directly with the number of users.

Common Mistake

[X] Wrong: "Adding more users won't affect how long permission checks take because policies are shared."

[OK] Correct: Each user requires separate API calls for creation, attaching policies, and permission checks, so time grows with users.

Interview Connect

Understanding how IAM operations scale helps you design systems that stay efficient as they grow, a key skill in cloud roles.

Self-Check

What if we changed from attaching policies to each user individually to using groups? How would the time complexity change?

Practice

1. What is the main reason to follow the principle of least privilege in AWS IAM?

easy

A. To create permanent access keys for all users

B. To allow users full access to all AWS services

C. To give users only the permissions they need to do their job

D. To disable multi-factor authentication (MFA) for easier access

Solution

1. Step 1: Understand least privilege concept

   Least privilege means giving users only the permissions they need, nothing more.

2. Step 2: Identify correct option

   To give users only the permissions they need to do their job matches this concept by limiting permissions to what is necessary.

3. Final Answer:

   To give users only the permissions they need to do their job -> Option C

4. Quick Check:

   Least privilege = minimal permissions [OK]

Hint: Least privilege means minimal needed permissions only [OK]

Common Mistakes:

• Giving users full access unnecessarily
• Using permanent keys instead of temporary credentials
• Ignoring MFA setup

2. Which of the following is the correct way to assign permissions to an AWS service using IAM?

easy

A. Create an IAM role and assign it to the AWS service

B. Generate permanent access keys and embed them in the service code

C. Create an IAM user and attach policies directly to the user

D. Use root account credentials for the service

Solution

1. Step 1: Understand IAM roles for services

   IAM roles allow AWS services to assume permissions temporarily without permanent keys.

2. Step 2: Identify best practice

   Assigning an IAM role to the service is the recommended way to grant permissions securely.

3. Final Answer:

   Create an IAM role and assign it to the AWS service -> Option A

4. Quick Check:

   Use roles for services, not permanent keys [OK]

Hint: Use roles for AWS services, not permanent keys [OK]

Common Mistakes:

• Attaching policies directly to users for services
• Embedding permanent keys in code
• Using root account credentials

3. Consider this IAM policy snippet attached to a user:

{
  "Version": "2012-10-17",
  "Statement": [{
    "Effect": "Allow",
    "Action": ["s3:ListBucket"],
    "Resource": ["arn:aws:s3:::example-bucket"]
  }]
}

What can this user do?

medium

A. Upload files to example-bucket

B. List the contents of the example-bucket

C. Delete files from example-bucket

D. Access all S3 buckets

Solution

1. Step 1: Analyze the policy actions

   The policy allows only the "s3:ListBucket" action on the specific bucket resource.

2. Step 2: Determine allowed operations

   "s3:ListBucket" lets the user see the list of objects but not upload or delete.

3. Final Answer:

   List the contents of the example-bucket -> Option B

4. Quick Check:

   Action = s3:ListBucket means list only [OK]

Hint: Check the Action field to know allowed operations [OK]

Common Mistakes:

• Assuming upload or delete permissions from list permission
• Thinking the policy applies to all buckets
• Ignoring the specific resource ARN

4. You created an IAM user with full S3 access but forgot to enable MFA. What is the best way to fix this?

medium

A. Attach an MFA policy and require MFA for sensitive actions

B. Delete the user and create a new one with MFA enabled

C. Remove all permissions from the user

D. Share the root account credentials with the user

Solution

1. Step 1: Understand MFA enforcement

   MFA can be required by attaching policies that enforce MFA for sensitive actions.

2. Step 2: Apply best practice

   Attaching an MFA policy is better than deleting the user or removing permissions.

3. Final Answer:

   Attach an MFA policy and require MFA for sensitive actions -> Option A

4. Quick Check:

   Enable MFA via policy, don't delete users [OK]

Hint: Use policies to enforce MFA, not user deletion [OK]

Common Mistakes:

• Deleting users unnecessarily
• Removing all permissions without MFA
• Sharing root credentials

5. Your company wants to allow temporary access to AWS resources for contractors without creating permanent IAM users. Which approach follows best IAM practices?

hard

A. Give contractors permanent access keys with admin permissions

B. Create permanent IAM users with full access for contractors

C. Share your root account credentials with contractors

D. Create IAM roles with limited permissions and let contractors assume them

Solution

1. Step 1: Identify temporary access method

   IAM roles allow temporary credentials that contractors can assume without permanent users.

2. Step 2: Match best practice

   Creating roles with limited permissions follows least privilege and avoids permanent keys.

3. Final Answer:

   Create IAM roles with limited permissions and let contractors assume them -> Option D

4. Quick Check:

   Temporary roles for contractors = best practice [OK]

Hint: Use roles for temporary access, avoid permanent users [OK]

Common Mistakes:

• Creating permanent users for contractors
• Sharing root credentials
• Giving admin permissions unnecessarily