Why IAM is foundational in GCP - See It in Action

Why IAM is foundational in GCP

📖 Scenario: You are starting a new project on Google Cloud Platform (GCP). You want to make sure only the right people and services can access your cloud resources securely.

🎯 Goal: Build a simple IAM setup that shows how to assign roles to users and service accounts to control access to a GCP project.

📋 What You'll Learn

Create a dictionary called members with exact entries for users and service accounts

Create a variable called role with the exact value roles/viewer

Use a loop with variables member and member_type to create a list of bindings

Create a final dictionary called iam_policy with the key bindings containing the list of bindings

💡 Why This Matters

🌍 Real World

IAM is the foundation of security in GCP. It ensures only authorized users and services can access cloud resources, protecting data and operations.

💼 Career

Understanding IAM is essential for cloud engineers, security specialists, and developers working with GCP to manage permissions and secure cloud environments.

1

Create the members dictionary

Create a dictionary called members with these exact entries: 'user:[e-mail]': 'user', 'user:[e-mail]': 'user', 'serviceAccount:[e-mail]': 'serviceAccount'

GCP

# Create the members dictionary with exact entries
# Your code here

Hint

Use curly braces to create a dictionary with the exact keys and values.

2

Set the role variable

Create a variable called role and set it to the exact string 'roles/viewer'

GCP

members = {
    'user:[e-mail]': 'user',
    'user:[e-mail]': 'user',
    'serviceAccount:[e-mail]': 'serviceAccount'
}
# Create the role variable with value 'roles/viewer'
# Your code here

Hint

Assign the string 'roles/viewer' to the variable named role.

3

Create the bindings list with a loop

Use a for loop with variables member and member_type to iterate over members.items(). Inside the loop, append a dictionary with keys 'role' set to role and 'members' set to a list containing member to a list called bindings. Initialize bindings as an empty list before the loop.

GCP

members = {
    'user:[e-mail]': 'user',
    'user:[e-mail]': 'user',
    'serviceAccount:[e-mail]': 'serviceAccount'
}
role = 'roles/viewer'

# Create an empty list called bindings
# Use a for loop with member and member_type to iterate over members.items()
# Append a dictionary with keys 'role' and 'members' to bindings
# Your code here

Hint

Remember to create the list before the loop and append dictionaries inside the loop.

4

Create the final IAM policy dictionary

Create a dictionary called iam_policy with a single key 'bindings' set to the bindings list.

GCP

members = {
    'user:[e-mail]': 'user',
    'user:[e-mail]': 'user',
    'serviceAccount:[e-mail]': 'serviceAccount'
}
role = 'roles/viewer'
bindings = []
for member, member_type in members.items():
    bindings.append({'role': role, 'members': [member]})

# Create iam_policy dictionary with key 'bindings' set to bindings
# Your code here

Hint

Use curly braces to create the dictionary with the key 'bindings'.

Practice

1. What is the main purpose of IAM in Google Cloud Platform?

easy

A. To monitor network traffic

B. To store data securely in the cloud

C. To create virtual machines automatically

D. To control who can access and manage cloud resources

Solution

1. Step 1: Understand IAM's role in GCP

   IAM stands for Identity and Access Management, which controls user permissions.

2. Step 2: Identify the main function

   IAM manages who can access and change cloud resources, ensuring security and organization.

3. Final Answer:

   To control who can access and manage cloud resources -> Option D

4. Quick Check:

   IAM controls access = C [OK]

Hint: IAM is about access control, not storage or monitoring [OK]

Common Mistakes:

• Confusing IAM with data storage services
• Thinking IAM manages network traffic
• Assuming IAM creates resources automatically

2. Which of the following is the correct way to assign a role to a user in GCP IAM?

easy

A. Grant the user a role using the IAM policy binding

B. Add the user to a Compute Engine instance

C. Create a new virtual machine for the user

D. Enable billing for the user account

Solution

1. Step 1: Review how roles are assigned in IAM

   Roles are assigned by adding users to IAM policy bindings on resources.

2. Step 2: Identify the correct method

   Granting a role via IAM policy binding is the proper way to assign permissions.

3. Final Answer:

   Grant the user a role using the IAM policy binding -> Option A

4. Quick Check:

   Role assignment = IAM policy binding [OK]

Hint: Roles are assigned via IAM policies, not VM or billing settings [OK]

Common Mistakes:

• Confusing user role assignment with VM creation
• Thinking billing enables permissions
• Adding users directly to instances instead of IAM

3. Consider this IAM policy snippet:

{
  "bindings": [
    {
      "role": "roles/storage.objectViewer",
      "members": ["user:[e-mail]"]
    }
  ]
}

What permission does Alice have?

medium

A. She can delete storage objects

B. She can create new storage buckets

C. She can view objects in Cloud Storage buckets

D. She can manage billing for storage

Solution

1. Step 1: Identify the role in the policy

   The role is "roles/storage.objectViewer", which grants read-only access to storage objects.

2. Step 2: Understand the permissions of the role

   This role allows viewing objects but not creating or deleting them.

3. Final Answer:

   She can view objects in Cloud Storage buckets -> Option C

4. Quick Check:

   objectViewer means read-only access [OK]

Hint: Viewer roles allow read-only access, not changes [OK]

Common Mistakes:

• Assuming viewer role allows object creation or deletion
• Confusing billing management with storage permissions
• Thinking role applies to bucket creation

4. You wrote this IAM policy but users report they cannot access the resource:

{
  "bindings": [
    {
      "role": "roles/editor",
      "members": ["user:[e-mail]"]
    }
  ]
}

What is the likely problem?

medium

A. The role "roles/editor" does not exist

B. The policy is missing the resource it applies to

C. The member email is incorrectly formatted

D. IAM policies cannot assign roles to users

Solution

1. Step 1: Check the policy structure

   The policy snippet shows bindings but does not specify the resource it applies to.

2. Step 2: Understand IAM policy application

   IAM policies must be attached to a specific resource (project, folder, or organization) to take effect.

3. Final Answer:

   The policy is missing the resource it applies to -> Option B

4. Quick Check:

   IAM policy needs resource context [OK]

Hint: IAM policies must be attached to resources to work [OK]

Common Mistakes:

• Assuming roles can be assigned without resource context
• Thinking role names are invalid
• Believing member emails are wrongly formatted

5. You want to give a team member permission to manage Compute Engine instances but not billing or project settings. Which IAM role should you assign?

hard

A. roles/compute.instanceAdmin

B. roles/owner

C. roles/billing.admin

D. roles/viewer

Solution

1. Step 1: Identify required permissions

   The team member needs to manage Compute Engine instances only, without billing or project-wide control.

2. Step 2: Match role to permissions

   roles/compute.instanceAdmin allows managing instances but not billing or project settings, unlike roles/owner or billing.admin.

3. Final Answer:

   roles/compute.instanceAdmin -> Option A

4. Quick Check:

   Instance admin role limits permissions correctly [OK]

Hint: Use specific roles, not owner or billing, for limited access [OK]

Common Mistakes:

• Assigning owner role gives too many permissions
• Using billing.admin grants billing rights unnecessarily
• Choosing viewer role does not allow managing instances