Skip to content

Blog

aws-root-manager: Manage AWS root access in your organization

In AWS, managing root credentials has always been a friction point for organization administrators. Every time a new account was created, we had to configure MFA for root access following best practices and the maturity model. However, enabling MFA is a manual step, and with AWS Organizations, this problem scaled. We could ignore it, apply an SCP to block actions performed with the root user, and deal with the failed check reported by all security tools.

In 2023, AWS announced that MFA would become mandatory, and the time is near. On March 24, 2025, registering an MFA will be required when using the root user.

To address this issue, on November 15, 2024, AWS announced a new feature that allows centralized root access management within an organization without having to manually intervene in each account. However, if we have a large number of accounts, performing the actions one by one is not the most convenient approach.

To simplify this management, we have created aws-root-manager , a tool that efficiently and automatically manages the state of root credentials across all accounts in an organization.

logo

IAM policy mishaps: Case 2 - SNS

Did you think we had forgotten about the IAM series? Well, you were right. Sorry for the delay, but here we are again.

Today, we are going to talk about Amazon Simple Notification Service (SNS).

Info

Remember that if you want to try the examples we are presenting, check out our repo .

We have prepared the different scenarios in Terraform .

Deploy IAM Roles across an AWS Organization as code

In environments with multiple AWS accounts, managing roles can be a challenge. AWS IAM offers us a robust solution for managing roles within each account, but when it comes to consistently implementing roles across all accounts in an organization, the task can become complex.

In this post, we will see how to automatically deploy IAM roles across all accounts in an AWS organization as code, using CloudFormation, Organizations, and Terraform.

architecture architecture

  • in aws, iam, s3
  • 7 min read

IAM policy mishaps: Case 1 - S3

Continuing with the series of posts related to IAM misconfigurations, we are going to delve a bit into its use focused on the AWS S3 service.

To do this, we will look at the different ways we can control the security of the service and how dangerous it is to apply a policy without clearly understanding what it does.

Info

If you want to directly try the examples we are going to present, take a look at our repo .

We have prepared different scenarios in Terraform .

  • in aws, iam
  • 6 min read

IAM policy mishaps: Intro to IAM

This post is based on the introduction of the talk IAM policy mishaps: A cautionary tale of cloud misconfigurations that we presented on Saturday, January 27th, at Sh3llCON (Reinosa). It is going to be the first in a series about IAM misconfigurations (yes, unfortunately, it's a topic that provides enough material for a series).