Centrally managing root entry for purchasers utilizing AWS Organizations

AWS Id and Entry Administration (IAM) is launching a brand new functionality permitting safety groups to centrally handle root entry for member accounts in AWS Organizations. Now you can simply handle root credentials and carry out extremely privileged actions.

Managing root consumer credentials at scale
For a very long time, Amazon Net Companies (AWS) accounts have been provisioned with extremely privileged root consumer credentials, which had unrestricted entry to the account. This root entry, whereas highly effective, additionally posed important safety dangers. Every AWS account’s root consumer needed to be secured by including layers of safety like multi-factor authentication (MFA). Safety groups have been required to handle and safe these root credentials manually. The method concerned rotating credentials periodically, storing them securely, and ensuring that the credentials complied with safety insurance policies.

As our clients expanded their AWS environments, this handbook method turned cumbersome and liable to error. For instance, giant enterprises working tons of or 1000’s of member accounts struggled to safe root entry constantly throughout all accounts. The handbook intervention not solely added operational overhead but additionally created a lag in account provisioning, stopping full automation and growing safety dangers. Root entry, if not correctly secured, might result in account takeovers and unauthorized entry to delicate sources.

Moreover, at any time when particular root actions comparable to unlocking an Amazon Easy Storage Service (Amazon S3) bucket coverage or an Amazon Easy Queue Service (Amazon SQS) useful resource coverage have been required, safety groups needed to retrieve and use root credentials, which solely elevated the assault floor. Even with rigorous monitoring and robust safety insurance policies, sustaining long-term root credentials opened doorways to potential mismanagement, compliance dangers, and handbook errors.

Safety groups started in search of a extra automated, scalable answer. They wanted a solution to not solely centralize the administration of root credentials but additionally programmatically handle root entry with no need long-term credentials within the first place.

Centrally handle root entry
With the brand new skill to centrally handle root entry, we deal with the longstanding problem of managing root credentials throughout a number of accounts. This new functionality introduces two important capabilities: the central administration of root credentials and root classes. Collectively, they provide safety groups a safe, scalable, and compliant solution to handle root entry throughout AWS Organizations member accounts.

Let’s first talk about the central administration of root credentials. With this functionality, now you can centrally handle and safe privileged root credentials throughout all accounts in AWS Organizations. Root credentials administration means that you can:

• Take away long-term root credentials – Safety groups can now programmatically take away root consumer credentials from member accounts, confirming that no long-term privileged credentials are left weak to misuse.
• Forestall credential restoration – It not solely removes the credentials but additionally prevents their restoration, safeguarding in opposition to any unintended or unauthorized root entry sooner or later.
• Provision secure-by-default accounts – As a result of now you can create member accounts with out root credentials from the beginning, you not want to use extra safety measures like MFA after account provisioning. Accounts are safe by default, which drastically reduces safety dangers related to long-term root entry and helps simplify the whole provisioning course of.
• Assist to remain compliant – Root credentials administration permits safety groups to display compliance by centrally discovering and monitoring the standing of root credentials throughout all member accounts. This automated visibility confirms that no long-term root credentials exist, making it simpler to fulfill safety insurance policies and regulatory necessities.

However how can we be sure it stays doable to carry out chosen root actions on the accounts? That is the second functionality we launch right this moment: root classes. It affords a safe different to sustaining long-term root entry. As an alternative of manually accessing root credentials at any time when privileged actions are required, safety groups can now achieve short-term, task-scoped root entry to member accounts. This functionality makes certain that actions comparable to unlocking S3 bucket insurance policies or SQS queue insurance policies will be carried out securely with out the necessity for long-term root credentials.

Root classes key advantages embrace:

• Activity-scoped root entry – AWS allows short-term root entry for particular actions, adhering to the most effective practices of least privilege. This limits the scope of what will be accomplished and minimizes the length of entry, decreasing potential dangers.
• Centralized administration – Now you can carry out privileged root actions from a central account with no need to log in to every member account individually. This streamlines the method and reduces the operational burden on safety groups, permitting them to give attention to higher-level duties.
• Alignment with AWS greatest practices – By utilizing short-term credentials, organizations align themselves with AWS safety greatest practices, which emphasize the precept of least privilege and the usage of short-term, non permanent entry the place doable.

This new functionality doesn’t grant full root entry. It gives non permanent credentials for performing one in all these 5 particular actions. The primary three actions are doable with central administration of root accounts. The final two come when enabling root classes.

• Auditing root consumer credentials – Learn-only entry to evaluation root consumer data
• Re-enabling account restoration – Reactivating account restoration with out root credentials
• Deleting root consumer credentials – Eradicating console passwords, entry keys, signing certificates, and MFA gadgets
• Unlocking an S3 bucket coverage – Modifying or deleting an S3 bucket coverage that denies all principals
• Unlocking an SQS queue coverage – Modifying or deleting an Amazon SQS useful resource coverage that denies all principals

Easy methods to receive root credentials on a member account
On this demo, I present you how one can put together your administration account, create a member account with out root credentials, and acquire non permanent root credentials to make one of many 5 approved API name on the member account. I assume you’ve gotten a company already created.

First, I create a member account.

aws organizations create-account    
     --email stormacq+rootaccountdemo@amazon.com 
     --account-name 'Root Accounts Demo account'
{
    "CreateAccountStatus": {
        "Id": "car-695abd4ee1ca4b85a34e5dcdcd1b944f",
        "AccountName": "Root Accounts Demo account",
        "State": "IN_PROGRESS",
        "RequestedTimestamp": "2024-09-04T20:04:09.960000+00:00"
    }
}

Then, I allow the 2 new capabilities on my administration account. Don’t fear, these instructions don’t alter the habits of the accounts in any method aside from enabling use of the brand new functionality.

➜  aws organizations enable-aws-service-access 
        --service-principal iam.amazonaws.com

➜  aws iam enable-organizations-root-credentials-management
{
    "OrganizationId": "o-rlrup7z3ao",
    "EnabledFeatures": [
        "RootCredentialsManagement"
    ]
}

➜  aws iam enable-organizations-root-sessions
{
    "OrganizationId": "o-rlrup7z3ao",
    "EnabledFeatures": [
        "RootSessions",
        "RootCredentialsManagement"
    ]
}

Alternatively, I may also use the console on the administration account. Underneath Entry administration, I choose Account settings.

Now, I’m able to make requests to acquire non permanent root credentials. I’ve to go one of many 5 managed IAM insurance policies to scope down the credentials to a particular motion.

➜  aws sts assume-root 
       --target-principal <my member account id> 
       --task-policy-arn arn=arn:aws:iam::aws:coverage/root-task/S3UnlockBucketPolicy 

{
    "Credentials": {
        "AccessKeyId": "AS....XIG",
        "SecretAccessKey": "ao...QxG",
        "SessionToken": "IQ...SS",
        "Expiration": "2024-09-23T17:44:50+00:00"
    }
}

As soon as I receive the entry key ID, the key entry key, and the session token, I take advantage of them as common with the AWS Command Line Interface (AWS CLI) or an AWS SDKs.

For instance, I can go these three values as atmosphere variables.

$ export AWS_ACCESS_KEY_ID=ASIA356SJWJITG32xxx
$ export AWS_SECRET_ACCESS_KEY=JFZzOAWWLocoq2of5Exxx
$ export AWS_SESSION_TOKEN=IQoJb3JpZ2luX2VjEMb//////////wEaCXVxxxx

Now that I obtained the non permanent credentials, I could make a restricted API name as root on the member account. First, I confirm I now have root credentials. The Arn subject confirms I’m working with the foundation account.

# Name get Caller Id and observe I am root within the member account
$ aws sts get-caller-identity
{
   "UserId": "012345678901",
   "Account": "012345678901",
   "Arn": "arn:aws:iam::012345678901:root"
}

Then, I take advantage of the delete-bucket-policy from S3 to take away an incorrect coverage that has been utilized to a bucket. The invalid coverage eliminated all bucket entry for everyone. Eradicating such coverage requires root credentials.

aws s3api delete-bucket-policy --bucket my_bucket_with_incorrect_policy

When there is no such thing as a output, it means the operation is profitable. I can now apply an accurate entry coverage to this bucket.

Credentials are legitimate just for quarter-hour. I wrote a brief shell script to automate the method of getting the credentials as JSON, exporting the proper atmosphere variables, and issuing the command I need to run as root.

Availability
Central administration of root entry is offered at no extra price in all AWS Areas besides AWS GovCloud (US) and AWS China Areas, the place there is no such thing as a root account. Root classes can be found in every single place.

You can begin utilizing it by means of the IAM console, AWS CLI or AWS SDK. For extra data, go to AWS account root consumer in our documentation and comply with greatest practices for securing your AWS accounts.

— seb