AWS Builder Center
Secure Your New AWS Account in 60 Minutes: A Practical Beginner's Security Checklist

Secure Your New AWS Account in 60 Minutes: A Practical Beginner's Security Checklist

A step-by-step checklist for locking down a fresh AWS account: protect the root user, set up least-privilege access, turn on logging and threat detection, and add spending guardrails. Built for students and first-time builders.

I'm a student at the ECU Sri Lanka Campus.
A brand-new AWS account is wide open in one important way: it is only as secure as the settings you choose in the first hour. Compromised accounts often come from a few common mistakes, such as a root user with no MFA, leaked access keys, or no logging to show what happened.
This checklist covers the essentials. Each step takes a few minutes.

1. Lock down the root user

The root user has unrestricted access to everything in the account, so treat it like a break-glass credential.
  • Enable MFA on the root user (a passkey, security key, or authenticator app).
  • Delete any root access keys. Root should never have programmatic credentials.
  • Use a long, unique password stored in a password manager.
  • Set up a separate email alias for the root account and monitor it.
After this, do not use root for daily work.

2. Use IAM Identity Center (or IAM roles) for everyday access

Create a non-root identity for yourself and give it only the permissions it needs.
  • IAM Identity Center is the recommended way to manage human access. It gives you short-lived credentials and centralized MFA.
  • If you use IAM users, attach permissions through groups and never attach  AdministratorAccess  casually.
  • Prefer roles and temporary credentials over long-lived access keys. If you must create keys, rotate them and never commit them to Git.
Least privilege means starting with the minimum permissions and adding only what you need. IAM Access Analyzer can generate a policy from the activity it sees in CloudTrail, so you can tighten broad permissions later.

3. Turn on CloudTrail

You cannot investigate what you did not record. CloudTrail logs API activity across your account.
  • The default event history only keeps 90 days of management events.
  • Create a multi-region trail that delivers logs to an S3 bucket for long-term retention.
  • Enable log file validation so you can detect tampering.
aws cloudtrail create-trail \
--name baseline-trail \
--s3-bucket-name <your-log-bucket> \
--is-multi-region-trail \
--enable-log-file-validation
aws cloudtrail start-logging --name baseline-trail
The log bucket needs a policy that allows CloudTrail to write to it. The console's trail wizard sets this up for you, which is easier for a first trail.

4. Enable threat detection

  • Amazon GuardDuty analyzes CloudTrail, VPC Flow Logs, and DNS logs for suspicious behavior, such as unusual API calls or traffic to known malicious IPs. It takes one click to enable and includes a free trial.
  • IAM Access Analyzer flags resources shared outside your account, like public S3 buckets or overly permissive role trust policies.
  • AWS Security Hub brings findings together and checks your account against security best practices.

5. Block public S3 access by default

Publicly exposed S3 buckets are a classic cause of data leaks. Enable Block Public Access at the account level:
aws s3control put-public-access-block \
--account-id <your-account-id> \
--public-access-block-configuration \
BlockPublicAcls=true,IgnorePublicAcls=true,BlockPublicPolicy=true,RestrictPublicBuckets=true
Also turn on default encryption for buckets that hold anything sensitive.

6. Set up spending guardrails

Security incidents often show up first as unexpected charges, such as crypto-mining instances launched with stolen credentials.
  • In AWS Budgets, create a budget with email alerts. The zero-spend template is good for learning accounts.
  • Enable Cost Anomaly Detection for automatic alerts on unusual spikes.

7. Keep the blast radius small

  • Use separate accounts for experiments and anything important (AWS Organizations makes this manageable).
  • Turn off or restrict Regions you do not use.
  • Tag resources so you know who owns what.

Quick checklist

  • [ ] Root MFA enabled, root access keys deleted
  • [ ] Daily access via Identity Center or least-privilege IAM
  • [ ] Multi-region CloudTrail writing to S3
  • [ ] GuardDuty and IAM Access Analyzer enabled
  • [ ] S3 Block Public Access on at the account level
  • [ ] Budget and anomaly alerts configured

Final thoughts

None of these steps are advanced. Together they cover a large share of the mistakes behind real-world cloud incidents. Once the basics are done, the next steps are Service Control Policies, centralized logging, and automated remediation with EventBridge and Lambda.
What is the first thing you do when you open a new AWS account? Share your checklist in the comments.
Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article