Safari Reading List Wiki Home About Schema Log Sources

Sources

"medium.com"

Sitemap

Open in app

Sign up

Sign in

Medium Logo

Get app

Write

Search

Sign up

Sign in

Unknown user

Pamela Uzodimma

Pamela Uzodimma

UX Researcher turned Cloud Professional

Follow writer

Member-only story

AWS

Cloud Security

Identity

Projects

Cloud Computing

Building a Secure AWS IAM and CloudTrail Setup: Lessons from the TechStart Project

Pamela Uzodimma

Pamela Uzodimma

Follow

5 min read

·

Aug 7, 2025

45

2

Listen

Share

Press enter or click to view image in full size

aws access and identity management IAM in a secure cloud environment

Source: Google Images

Cloud skills go beyond theory; they require real, practical implementation. This is what drove me to take on a hands-on project simulating the security setup for a fictional startup, TechStart Ltd, using AWS Identity and Access Management (IAM) and CloudTrail.

This article documents what I built, the steps I followed, challenges I encountered, and why this type of project is not just a learning exercise but a critical part of how modern organizations operate in the cloud.

Project Overview: A Simulated Tech Company Setup

The goal was to simulate the cloud security setup for a small but growing startup. As part of the project, I built a structure where different team members had different levels of access to AWS services following the principle of least privilege.

This project was guided by a structured 7-day plan, covering everything from planning and architecture to access testing and security logging. Here’s what I accomplished:

IAM Configuration and User Setup

On Day 2 of the project, I configured access control by doing the following:

  • Created IAM Groups:
  • AdminGroup
  • DevGroup
  • TestGroup
  • AuditGroup
  • Created IAM Users:
  • admin_user
  • dev_user1, dev_user2
  • test_user
  • audit_user
  • Enabled Multi-Factor Authentication (MFA) for each user to enhance account security.

Each group was assigned a custom IAM policy that defined what actions users could perform. For example:

  • Developers were given access to EC2 and S3
  • Testers had limited permissions
  • Auditors could only view resources (read-only)
  • Admin had full access

Create an account to read the full story.

The author made this story available to Medium members only.

If you’re new to Medium, create a new account to read this story on us.

Continue in app

Or, continue in mobile web

Sign up with Google

Sign up with Facebook

Sign up with email

Already have an account? Sign in

Pamela Uzodimma

Pamela Uzodimma

Follow

Written by Pamela Uzodimma

89 followers

· 29 following

UX Researcher turned Cloud Professional

Follow

Help

Status

About

Careers

Press

Blog

Store

Privacy

Rules

Terms

Text to speech

reCAPTCHA

Recaptcha requires verification.

protected by reCAPTCHA