Why account management matters in AWS - See It in Action

Why Account Management Matters in AWS

📖 Scenario: You are working as a cloud administrator for a small company. The company wants to organize its AWS resources properly to keep things secure and easy to manage. You will create a simple AWS account structure using AWS Organizations to separate billing and permissions.

🎯 Goal: Build a basic AWS Organizations setup with a master account and two member accounts named Development and Production. This will help the company manage accounts securely and clearly.

📋 What You'll Learn

Create a master AWS Organization account

Add two member accounts named Development and Production

Assign a tag Environment with values Dev and Prod to the member accounts

Enable consolidated billing for all accounts

💡 Why This Matters

🌍 Real World

Companies use AWS Organizations to manage multiple AWS accounts securely and efficiently, separating environments like development and production.

💼 Career

Cloud administrators and architects must understand account management to control costs, permissions, and security in cloud environments.

1

Create the AWS Organization master account

Create a variable called master_account and assign it the string value 'MasterAccount' to represent the AWS Organization master account.

AWS

# Create a variable called master_account with value 'MasterAccount'
# Your code here

Hint

Think of the master account as the main folder that holds all other accounts.

2

Define member accounts for Development and Production

Create a dictionary called member_accounts with two keys: 'Development' and 'Production'. Assign each key a dictionary with a single key 'Environment' and values 'Dev' for Development and 'Prod' for Production.

AWS

master_account = 'MasterAccount'
# Create member_accounts dictionary with Development and Production keys and Environment tags
# Your code here

Hint

Use a dictionary inside a dictionary to store account names and their environment tags.

3

Enable consolidated billing for all accounts

Create a variable called consolidated_billing_enabled and set it to True to indicate that billing is consolidated under the master account.

AWS

master_account = 'MasterAccount'
member_accounts = {
    'Development': {'Environment': 'Dev'},
    'Production': {'Environment': 'Prod'}
}
# Enable consolidated billing
# Your code here

Hint

Setting this to true means all accounts pay through the master account.

4

Summarize the AWS Organization setup

Create a dictionary called aws_organization with keys 'MasterAccount', 'MemberAccounts', and 'Billing'. Assign master_account to 'MasterAccount', member_accounts to 'MemberAccounts', and consolidated_billing_enabled to 'Billing'.

AWS

master_account = 'MasterAccount'
member_accounts = {
    'Development': {'Environment': 'Dev'},
    'Production': {'Environment': 'Prod'}
}
consolidated_billing_enabled = True
# Create aws_organization dictionary summarizing the setup
# Your code here

Hint

This dictionary shows the full AWS Organization setup in one place.

Practice

1. Why is account management important in AWS cloud environments?

easy

A. It helps keep resources safe and organized.

B. It automatically fixes all security issues.

C. It makes cloud services free to use.

D. It removes the need for user permissions.

Solution

1. Step 1: Understand the role of account management

   Account management organizes cloud resources and controls who can access them.

2. Step 2: Identify the correct benefit

   Keeping resources safe and organized is a key benefit of account management.

3. Final Answer:

   It helps keep resources safe and organized. -> Option A

4. Quick Check:

   Account management = safety and organization [OK]

Hint: Account management = safety + organization [OK]

Common Mistakes:

• Thinking it fixes security automatically
• Believing cloud services become free
• Assuming no need for permissions

2. Which AWS service is used to manage multiple AWS accounts centrally?

easy

A. AWS Organizations

B. AWS IAM

C. Amazon S3

D. AWS Lambda

Solution

1. Step 1: Identify the service for account grouping

   AWS Organizations is designed to manage multiple AWS accounts centrally.

2. Step 2: Differentiate from other services

   AWS IAM manages users and permissions within an account, not multiple accounts.

3. Final Answer:

   AWS Organizations -> Option A

4. Quick Check:

   Multiple account management = AWS Organizations [OK]

Hint: Multiple accounts? Use AWS Organizations [OK]

Common Mistakes:

• Confusing IAM with account management
• Choosing unrelated services like S3 or Lambda
• Thinking IAM manages multiple accounts

3. Given this AWS IAM policy snippet, what does it allow?

{
  "Effect": "Allow",
  "Action": "s3:ListBucket",
  "Resource": "arn:aws:s3:::example-bucket"
}

medium

A. Allows listing objects inside example-bucket

B. Allows listing the example-bucket itself

C. Allows listing all buckets in the account

D. Allows deleting example-bucket

Solution

1. Step 1: Understand the Action and Resource

   The action 's3:ListBucket' allows listing the bucket itself, which includes metadata and the ability to list objects inside.

2. Step 2: Differentiate from other permissions

   This permission allows listing the bucket (its contents), but not listing all buckets (which requires s3:ListAllMyBuckets) or deleting.

3. Final Answer:

   Allows listing the example-bucket itself -> Option B

4. Quick Check:

   s3:ListBucket on bucket ARN = list bucket contents [OK]

Hint: s3:ListBucket on bucket = list bucket contents [OK]

Common Mistakes:

• Thinking it lists objects inside the bucket only
• Confusing with s3:ListAllMyBuckets for all buckets
• Assuming it allows deletion

4. You created an AWS Organization but users in member accounts cannot access shared resources. What is the likely issue?

medium

A. You forgot to enable consolidated billing

B. Member accounts are not linked to AWS IAM

C. AWS Organizations does not support resource sharing

D. You did not set proper IAM permissions for cross-account access

Solution

1. Step 1: Check AWS Organizations capabilities

   AWS Organizations supports resource sharing but requires permissions set correctly.

2. Step 2: Identify permission setup issue

   Without proper IAM permissions, users cannot access resources across accounts.

3. Final Answer:

   You did not set proper IAM permissions for cross-account access -> Option D

4. Quick Check:

   Cross-account access needs IAM permissions [OK]

Hint: Cross-account access needs IAM permissions [OK]

Common Mistakes:

• Assuming billing controls access
• Believing Organizations can't share resources
• Thinking member accounts lack IAM

5. You want to track costs separately for different teams using AWS accounts. What is the best practice to manage this?

hard

A. Use one AWS account and tag resources by team.

B. Share one AWS account login among all teams.

C. Create separate AWS accounts for each team under AWS Organizations.

D. Disable AWS Organizations and use IAM groups instead.

Solution

1. Step 1: Understand cost tracking needs

   Separate accounts allow clear cost separation and billing for each team.

2. Step 2: Compare with tagging and shared accounts

   Tagging helps but can be error-prone; sharing accounts mixes costs and risks security.

3. Step 3: Evaluate AWS Organizations role

   AWS Organizations lets you manage multiple accounts easily and consolidate billing.

4. Final Answer:

   Create separate AWS accounts for each team under AWS Organizations. -> Option C

5. Quick Check:

   Separate accounts = clear cost tracking [OK]

Hint: Separate accounts per team for clear cost tracking [OK]

Common Mistakes:

• Using one account with tags only
• Sharing login credentials
• Disabling Organizations for this purpose