The management account owns your AWS organization. Whoever controls it can create and close accounts, rewrite every guardrail and pull any account out of the organization. Many teams still treat it as an ordinary account: the first workload was deployed there, everyone signs in daily, and it has the same SSO access as everything else.
It is also the one account your guardrails cannot protect. Service control policies (SCPs) only affect member accounts. A Region restriction or a "nobody may stop CloudTrail" policy does nothing to users and roles in the management account, and AWS Control Tower's preventive controls skip it too.
So keep it empty, and make signing in a rare event.
IAM Identity Center's organization instance also lives here and cannot be moved. You can still administer it from another account.
No applications, servers, models or data. With nothing else in the account, the bill is also easier to read.
Do not give people SSO access for normal work. If someone needs in, such as a finance person who needs the payer's billing console, follow the Identity Center guidance. Create a permission set used only for the management account and assign it to named users, not groups. Anyone who can edit a group in your identity provider could otherwise add themselves to your most powerful account.
If you sign in for something routine, delegate that task instead.
Register your Log/Security account as the delegated administrator for:
SCPs still apply to the delegated administrator, which is the point of moving the work there. Registering a delegated administrator and enabling trusted access for a service cannot be delegated. Run both from the management account through the pipeline role.
Northwind's management account runs the production app. Every developer has the Admin permission set on it, and it is the GuardDuty administrator.
❌ Figure: Bad example - Bad example - The account with the most power has the most people in it and no SCPs
Northwind's management account holds Organizations and billing. Nobody has a standing SSO assignment to it. The security team runs GuardDuty, Security Hub CSPM, CloudTrail and Identity Center from the Log/Security account, and SCP changes go through a pull request.
✅ Figure: Good example - Good example - Months go by without anyone signing in to the management account