AWS Basics: IAM, EC2 and S3 for Developers
Understand identity, compute and object storage before deploying a cloud workload.
IAM: identity and permissions
IAM controls who can access AWS resources and what actions they can perform. Prefer roles and temporary credentials for workloads where possible. Apply least privilege and MFA for human users.
EC2: virtual servers
Before launching an EC2 instance, understand the AMI, instance type, VPC and subnet, security group, access method, storage and expected cost.
S3: object storage
S3 stores objects in buckets. Common uses include static assets, backups and exports. Block public access by default unless public access is intentional. Use bucket policies, encryption and lifecycle rules.
Safe first lab
1. Create a dedicated IAM role.
2. Launch a small test instance.
3. Allow only required inbound ports.
4. Store test files in a private S3 bucket.
5. Set a budget alert and terminate lab resources when finished.
Interview questions
What is the difference between an IAM user and role? What does an EC2 security group do? When would you choose S3 over block storage?
Try the concepts in a small project and verify version-specific details with official documentation.
More AWS resources