How can I attach an AWS Organization policy to a child account or Organizational Unit (OU)?

Search for a command to run...

No comments yet. Be the first to comment.
The Ops Fix Hub is a dynamic series designed to tackle real-world challenges in the DevOps and CloudOps domains. "Breaking Down Barriers, One Ops Fix at a Time."
Scenario: We encountered an issue while attempting to restore an EFS backup using AWS Backup. User: arn:aws:sts::123456789012:assumed-role/devops/dummy.com is not authorized to perform: backup:StartRestoreJob on resource: arn:aws:backup:ap-south-1:12...
This migration was performed on a production workload where cost reduction was prioritized over zone-level high availability.

1. Overview What I Designed I designed a hybrid infrastructure architecture: Terraform → Foundation Layer Crossplane → Dynamic Lifecycle Layer ArgoCD → GitOps Enforcement This created a continuou

Cross-cloud VM migration is not a disk copy task. It is: An access model transformation A replication lifecycle management exercise A downtime control operation A cost boundary decision We execu

When AWS introduced AWS DevOps Agent, I was less interested in feature lists and more interested in one practical question. Can it actually reduce investigation time during real production-style failu

Migrating object storage across cloud providers is not a copy task.It is a cost, network, and security boundary problem. We migrated 10+ TB of object data from Google Cloud Storage to Amazon S3 under

Scenario:-
To attach a policy to a child account or an Organizational Unit (OU) in AWS Organizations, follow these steps:
Log In to AWS Management Console:
Navigate to AWS Organizations:
Access Policies:
Select and Attach Policy:
Find the policy you want to attach and click on it.
Click Attach Policy, then select the target (OU or child account) from the list.
Confirm the action by clicking Attach again.
Review Effective Policies:
Navigate to the Accounts section in AWS Organizations.
Select the account or OU and click Effective Policies to verify the applied policies.
When you log in with a child account and attempt to add an organization-level policy, you receive the error:
This error occurs because organization-level policies can only be managed by the management account or delegated administrator accounts. Child accounts do not have default permissions to view or add these policies.
Verify Account Roles and Permissions:
Ensure you are logged in with a child account.
Check if there are Service Control Policies (SCPs) applied to the child account that restrict access.
Contact the Management Account Administrator:
Example SCP to allow policy viewing:
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"organizations:DescribePolicy",
"organizations:ListPolicies",
"organizations:AttachPolicy"
],
"Resource": "*"
}
]
}
Use the Management Account for Policy Management:
Delegate Access with IAM Roles:
The management account can create a role with necessary permissions and allow the child account to assume the role.
Example Role Policy for Delegation:
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"organizations:DescribePolicy",
"organizations:ListPolicies",
"organizations:AttachPolicy"
],
"Resource": "*"
}
]
}
Attach Policies Through Delegated Access:
Policies must be attached from the management account unless permissions are explicitly delegated.
SCPs applied at the root or OU level might restrict child account permissions.