Ravindra BagaleCourses & study guides मराठी Track your progress

Connect Active Directory to AWS IAM Identity Center

Active Directory is where many companies already keep employees. You can connect that directory to IAM Identity Center — but a student laptop lab is not the same as a full on-prem AD join. We stay honest about what you can try tonight.

What you'll learn in this chapter

  • Why companies keep AD
  • Three AWS paths: Managed AD, AD Connector, external IdP
  • Identity Center + AD / Entra ID idea
  • What a student can do in a lab
  • What needs real org IT

1. Everyday example first

Why do we need this?

A Pune IT park company already has employee logins in Active Directory for laptops and Wi-Fi. They do not want a second password list only for AWS. Connecting AD (or Entra ID) to Identity Center means one hire / one fire updates AWS access too.

The company is a generic example — not a real client story.

What is it?

Active Directory (AD) is Microsoft’s directory of users and groups. On AWS you meet it in a few different products — do not mix the names.

OptionWhat it isStudent lab?
IAM Identity Center Identity StoreBuilt-in users/groups (no AD)Yes — previous chapter
External IdP (SAML/OIDC)Okta, Entra ID, Google… federate into Identity CenterDemo IdP possible; needs admin
AWS Managed Microsoft ADAD Domain Controllers run as AWS serviceCostly for class; usually skip
AD ConnectorProxy to your existing on-prem ADNeeds real corporate AD

2. Identity Center + directory

Why do we need this?

Changing the identity source is a one-way door in many orgs — plan before you click.

What is it?

  1. Default lab: keep Identity Center directory and create users there.
  2. Company path: set identity source to Active Directory (Managed AD or self-managed via connector/ fort) or to an external IdP like Microsoft Entra ID.
  3. Users then sign in with company credentials at the AWS access portal; permission sets still control AWS rights.
  4. SCIM provisioning (where supported) can auto-create/deactivate users from the IdP.

3. Honest student path

  • Do tonight: finish Identity Center with the built-in directory (previous lab). Understand AD vocabulary.
  • Do with trainer/org: watch an Entra ID or Okta federation demo; do not invent a second production directory.
  • Skip unless budgeted: AWS Managed Microsoft AD (Directory Service charges while it runs). Delete unused directories.

Ravindra Bagale's Tip

Students sometimes launch Managed Microsoft AD “just to see” and forget it for a week — that is an expensive surprise. Prefer screenshots from docs or a shared demo account.

4. Interview angles

Q. AD Connector vs Managed AD?

Connector proxies to existing AD; Managed AD is AD as an AWS service.

Q. Does AD replace permission sets?

No — AD authenticates who you are; permission sets authorize AWS actions.

Q. Entra ID with AWS?

Common external IdP for Identity Center via SAML/OIDC.

Q. Student without corporate AD?

Use Identity Center Identity Store — still valid SSO learning.

Try at home

  1. Write 5 lines: authentication (who) vs authorization (what) using AD + permission sets.
  2. Next: IAM administrator habits — root, MFA, break-glass.

In short

  1. AD holds company users; Identity Center can federate them.
  2. Managed AD, AD Connector, external IdP — different tools.
  3. Student lab = Identity Center directory is enough.
  4. Do not leave Managed AD running unused.

Practice Tasks

About this scenario

Goa Beach Stays is a hospitality business in Panaji. Rosario Fernandes looks after its IT and cloud work. They count money in INR and run their AWS resources in the ap-south-1 Region. In the tasks below you do real jobs for them using what this lesson teaches. All names, account IDs, IP addresses and numbers are made up for practice.

0 / 10

Easy Configure a named profile

Why: Profiles keep keys for different accounts apart.

What to do: Start the interactive setup for a profile named goabeachstays-prod.

How:
  1. Read the task and decide which AWS service it is about.
  2. Write aws, then the service name, then the operation (the action word).
  3. Add each needed flag (--name) followed by its value from the task.
  4. Flags can be in any order. Click Check answer.

Easy Check who you are logged in as

Why: Always confirm the account and identity before running changes.

What to do: Show the account ID and ARN of the identity your CLI is using.

How:
  1. Read the task and decide which AWS service it is about.
  2. Write aws, then the service name, then the operation (the action word).
  3. Add each needed flag (--name) followed by its value from the task.
  4. Flags can be in any order. Click Check answer.

Easy How many addresses in a /16?

Why: Picking a VPC size needs this count.

What to do: Goa Beach Stays plans the VPC 10.12.0.0/16. How many IP addresses does it hold in total?

How:
  1. Write down the numbers the task gives you.
  2. Work it out step by step on paper.
  3. Type only the final answer in the box.
  4. Click Check answer.

Easy Port for SSH

Why: Security group rules need the right port.

What to do: Which TCP port must the security group open for SSH?

How:
  1. Write down the numbers the task gives you.
  2. Work it out step by step on paper.
  3. Type only the final answer in the box.
  4. Click Check answer.

Easy Show where you are

Why: Before you copy or delete anything, you must know which folder you are in.

What to do: Rosario Fernandes logged in to the Goa Beach Stays server and is not sure which folder the terminal is in. Print the current folder path.

How:
  1. Find the Linux command that does this job.
  2. Add the options (like -r or -h) the task needs.
  3. Add the file names, folders or users in the right order.
  4. Use sudo if the job changes system files or users. Click Check answer.

Medium List Identity Center instances

Why: You need the instance ARN and identity store ID for SSO admin commands.

What to do: List the IAM Identity Center instances.

How:
  1. Read the task and decide which AWS service it is about.
  2. Write aws, then the service name, then the operation (the action word).
  3. Add each needed flag (--name) followed by its value from the task.
  4. Flags can be in any order. Click Check answer.

Medium Log in with SSO

Why: SSO gives short-lived keys, so no long-term access keys sit on your laptop.

What to do: Log in with IAM Identity Center for profile goabeachstays-dev.

How:
  1. Read the task and decide which AWS service it is about.
  2. Write aws, then the service name, then the operation (the action word).
  3. Add each needed flag (--name) followed by its value from the task.
  4. Flags can be in any order. Click Check answer.

Medium Set the default Region of a profile

Why: Setting region in the profile saves typing --region every time.

What to do: Set region to ap-south-1 for profile goabeachstays-prod using aws configure set.

How:
  1. Read the task and decide which AWS service it is about.
  2. Write aws, then the service name, then the operation (the action word).
  3. Add each needed flag (--name) followed by its value from the task.
  4. Flags can be in any order. Click Check answer.

Medium Create access keys for a user

Why: Access keys let a user run the AWS CLI. Store them safely and rotate them.

What to do: Create an access key for user rosario.

How:
  1. Read the task and decide which AWS service it is about.
  2. Write aws, then the service name, then the operation (the action word).
  3. Add each needed flag (--name) followed by its value from the task.
  4. Flags can be in any order. Click Check answer.

Hard Create a permission set

Why: A permission set is a role template that Identity Center creates in each account.

What to do: Create permission set ReadOnly-goabeachstays in instance arn:aws:sso:::instance/ssoins-1234567890abcdef with session duration PT8H.

How:
  1. Read the task and decide which AWS service it is about.
  2. Write aws, then the service name, then the operation (the action word).
  3. Add each needed flag (--name) followed by its value from the task.
  4. Flags can be in any order. Click Check answer.

Revision, comparison and interview cards

Revise this lesson in a few minutes. Save the cards on your phone or download them as PNG files. The QR code on each card opens this lesson.

Revision card: Active Directory and AWS. A Pune IT park company already has AD for laptops. A second password list only for AWS is how offboarding fails. Active Directory holds company users/groups. Identity Center can use its own Identity Store, or federate AD / Entra ID so hire/fire updates AWS access too. Pick an identity source in Identity Center: Identity Store (lab), or external IdP / AD integration for companies. Corporate AD groups map to Identity Center assignments so leaving the company removes AWS tiles.
Revision card: Active Directory and AWS · Download PNG · Open card page
Revision card: Managed AD vs Connector vs IdP. Students launch Managed Microsoft AD “to try SSO” and leave a billed directory running all month. AWS Managed Microsoft AD = AD as a service. AD Connector = proxy to existing on-prem AD. External IdP (e.g. Entra ID) often talks to Identity Center via SAML/OIDC. For class labs stay on Identity Center Identity Store. Use Managed AD only when you truly need AD and delete it after. Identity Store users can still learn SSO without any Managed AD charges.
Revision card: Managed AD vs Connector vs IdP · Download PNG · Open card page
Revision card: AD authenticates; permission sets authorize. Thinking “AD replaces IAM policies” leaves accounts either locked or wide open. AD (or Entra ID) proves who you are (authentication). Identity Center permission sets decide what you may do in AWS (authorization). Connect or federate the directory, then still create least-privilege permission sets and account assignments. Finance AD group gets Billing permission set only; Developers get PowerUser on the dev account only.
Revision card: AD authenticates; permission sets authorize · Download PNG · Open card page
Comparison: AD Connector vs AWS Managed Microsoft AD. AD Connector: Proxy to your existing on-prem Active Directory. AWS Managed Microsoft AD: AD delivered as an AWS-managed directory service.
Comparison: AD Connector vs AWS Managed Microsoft AD · Download PNG · Open card page
Interview card: AD Connector vs Managed Microsoft AD?. AD Connector proxies authentication to your existing on-prem AD. AWS Managed Microsoft AD is Active Directory delivered as an AWS-managed service (its own directory). Managed AD costs money even when idle. Students should not leave it running after a curiosity click. Class SSO learning: Identity Center Identity Store. Corporate already-on-AD: Connector or external IdP patterns — not “always Managed AD”.
Interview card: AD Connector vs Managed Microsoft AD? · Download PNG · Open card page
Interview card: Does AD replace permission sets?. No. AD (or Entra ID) authenticates who you are. Permission sets authorize what you may do in AWS after sign-in. Connecting AD without least-privilege permission sets can grant everyone broad AWS admin through a single group mistake. Map AD groups to tight permission sets per account (e.g. Developers → PowerUser on dev only).
Interview card: Does AD replace permission sets? · Download PNG · Open card page

More cards: Ravi Sir's Cards.