AWS Builder Center
Starting My Cloud Security Journey

Starting My Cloud Security Journey

When starting to learn AWS, it is tempting to jump straight into launching instances and testing databases. However, coming from a cybersecurity interest, my first priority was making sure my AWS account was secure from day one. Here are three foundational security steps I configured immediately after creating my AWS Free Tier account.

Root account restriction:
The root user has unrestricted access to everything in the account. To protect it:
I enabled multi-factor authentication (MFA). I stopped using the root account for day-to-day tasks; instead, I created a dedicated administrator user for routine work to minimize the impact of accidental errors.
Creating a zero-spend billing alarm:
Security also involves protecting the budget against configuration errors or compromised credentials that could lead to the deployment of unauthorized resources:
I accessed Billing and Cost Management and set up a CloudWatch billing alarm to receive an email notification if costs exceed $1. This acts as an early warning system in case a service is left running or an unauthorized resource is deployed.
Avoiding the static credentials trap:
One of the most common mistakes beginners make is hardcoding access keys directly into source code and accidentally exposing them in public repositories.
I established a rule never to upload  .env  files or credential files to GitHub. I focus on using IAM roles and AWS CloudShell directly from the console, rather than storing static keys on my local machine.
What I learned: Cloud security doesn't start with complex architectures, but with good security hygiene from the very first login.
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