
Day 40: AWS Organizations and IAM Identity Center – Managing Multiple Accounts and People
Day 40 of my 90-day AWS challenge, with 50 days to go: how AWS Organizations groups accounts, applies guardrails with service control policies, and consolidates billing, and how IAM Identity Center gives people sign-in access to those accounts.
Day 40 of 90
Forty days in, 50 to go. So far everything I built lived in a single AWS account. Real organizations use many accounts, for example separate ones for development, testing, and production, or one per team. Two services make that manageable: AWS Organizations for the accounts and IAM Identity Center for the people.
Why more than one account?
- Isolation: a mistake in a development account can't touch production
- Security boundaries: an AWS account is the strongest isolation boundary in AWS
- Cost tracking: each account's spending is easy to see (Day 26)
- Limits: service quotas apply per account
- Control: different rules can apply to different groups of accounts
AWS Organizations
Organizations lets me create and manage a group of accounts centrally.
Concept | What it is |
|---|---|
Organization | The whole group of accounts, with one management account |
Management account | The account that creates the organization and pays the bill. It should not run workloads |
Member account | Any other account in the organization |
Organizational unit (OU) | A folder of accounts, such as Dev , Prod , or Security . OUs can be nested |
Root | The top of the hierarchy that contains all OUs and accounts |
What it provides
- Consolidated billing: one bill for all accounts, with combined usage for volume discounts and shared Savings Plans (Day 26)
- Account creation: create new member accounts with an API call or from the console
- Policies that apply to accounts or OUs
- Integration with other services, such as an organization trail in CloudTrail that logs every account (Day 20)
Service control policies (SCPs)
An SCP sets the maximum permissions that identities in an account can have. It does not grant anything. Even if an IAM policy allows an action, an SCP that denies it wins. Some details:
- SCPs affect the IAM users, roles, and root user of member accounts, but not the management account
- Attach them to the root, an OU, or an account, and they are inherited down the tree
- Like IAM, an explicit deny always wins (Day 2)
An example guardrail that blocks use of Regions I don't plan to use:
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "DenyOutsideAllowedRegions",
"Effect": "Deny",
"NotAction": ["iam:*", "organizations:*", "route53:*", "cloudfront:*", "support:*"],
"Resource": "*",
"Condition": {
"StringNotEquals": {
"aws:RequestedRegion": ["ap-south-1", "us-east-1"]
}
}
}
]
}The Regions are examples. The
NotAction list keeps global services working, and any SCP should be tested on a test OU before it is applied widely.Other policy types
Tag policies, backup policies, and policies that control how AWS AI services may use content.
AWS Control Tower
Control Tower builds on Organizations to set up a well-organized landing zone, a multi-account environment, with pre-built controls (guardrails) and an account factory.
IAM Identity Center
IAM Identity Center (formerly AWS Single Sign-On) is the recommended way to give people access to multiple AWS accounts and applications with one sign-in.
Concept | What it is |
|---|---|
Identity source | Where users live: the built-in directory, an external identity provider such as Okta or Microsoft Entra ID, or Active Directory |
User and group | The people and the teams they belong to |
Permission set | A collection of IAM policies that defines what someone can do, such as ReadOnlyAccess or AdministratorAccess |
Assignment | Giving a user or group a permission set in one or more accounts |
Access portal | A web page where users sign in and choose an account and role |
When someone picks an account and role, Identity Center gives them temporary credentials, so there are no long-lived access keys to leak. For the CLI:
aws configure sso
aws sso login --profile my-profileBest practices
- Don't use the management account for workloads, and protect its root user with MFA (Day 1)
- Use groups and permission sets, not individual IAM users in every account
- Apply least privilege (Day 2), and give broad permissions only where necessary
- Turn on an organization-wide CloudTrail (Day 20) and set a budget per account (Day 26)
- Roll out infrastructure across accounts with CloudFormation StackSets (Day 16)
Cost
Organizations and IAM Identity Center have no additional charge. The resources inside each account are billed as usual, and every new account needs its own unique email address.
What I practiced today
- Enabled AWS Organizations for my account, which made it the management account
- Looked at the structure and created an OU
- Read an example SCP and learned why it would have no effect on the management account itself
- Enabled IAM Identity Center, and created a user and a group
- Created a permission set based on read-only access and assigned it
- Signed in through the access portal and checked the temporary session
- Removed the practice users and permission sets afterwards
Key takeaways
- Multiple accounts are the base of a safe, well-organized AWS environment
- SCPs are guardrails: they limit permissions but never grant them
- Identity Center replaces per-account IAM users with one sign-in and temporary credentials
- Keep the management account for administration only, and protect it with MFA
Up next: Day 41
Connecting networks: VPC peering, Transit Gateway, VPN, Direct Connect, and PrivateLink.
Learning AWS too? Follow along and share what you're building. #90DaysOfAWS
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article