Week 3 Worklog
Week 3 Objectives:
- Master AWS Compute services with focus on EC2 fundamentals
- Understand EC2 instance types, storage options, and lifecycle management
- Learn AWS Backup strategies and disaster recovery concepts
- Explore Storage Gateway for hybrid cloud storage solutions
- Deploy static websites using S3 and CloudFront
Tasks to be carried out this week:
| Day | Task | Start Date | Completion Date | Reference Material |
|---|
| 1 | - Study Compute VM on AWS
+ EC2 Instance Types and use cases
+ Amazon Lightsail overview
+ EFS/FSx file systems
+ AWS MGN for migrations | 2025/09/22 | 2025/09/22 | https://aws.amazon.com/ec2/instance-types/ |
| 2 | - Deep dive into EC2 components:
+ AMI creation and management
+ Backup strategies
+ Key Pair authentication
+ Elastic Block Store (EBS) types
+ Instance Store characteristics | 2025/09/23 | 2025/09/23 | https://docs.aws.amazon.com/ec2/ |
| 3 | - Learn EC2 advanced features:
+ User Data for bootstrapping
+ Instance Metadata service
+ EC2 Auto Scaling configuration
- Lab 13: Deploy AWS Backup
+ Create backup plans
+ Test restore procedures | 2025/09/24 | 2025/09/24 | https://000013.awsstudygroup.com/ |
| 4 | - Lab 24: Storage Gateway implementation
+ Create S3 bucket
+ Deploy EC2 for Storage Gateway
+ Configure File Gateway
+ Create File Shares | 2025/09/25 | 2025/09/25 | https://000024.awsstudygroup.com/ |
| 5 | - Lab 57: Static Website Hosting
+ Create S3 bucket and load data
+ Enable static website feature
+ Configure public access
+ Test website functionality | 2025/09/26 | 2025/09/26 | https://000057.awsstudygroup.com/ |
| 6 | - Continue Lab 57:
+ Block public access
+ Configure CloudFront distribution
+ Enable bucket versioning
+ Configure cross-region replication | 2025/09/27 | 2025/09/27 | https://000057.awsstudygroup.com/ |
| 7 | - Weekly review and cleanup
- Complete all lab resource cleanup
- Document learnings and best practices | 2025/09/28 | 2025/09/28 | |
Week 3 Achievements:
EC2 Mastery:
- Understood different instance types: General Purpose (T3, M5), Compute Optimized (C5), Memory Optimized (R5)
- Learned instance lifecycle: Launch, Stop, Terminate, Hibernate
- Configured User Data scripts for automated instance setup
- Accessed Instance Metadata for dynamic configuration
Storage Solutions:
- Compared EBS volume types: gp3, io2, st1, sc1
- Understood Instance Store vs EBS trade-offs
- Created and managed AMIs for backup and replication
- Implemented EBS snapshots and lifecycle policies
AWS Backup Implementation (Lab 13):
- Deployed infrastructure with EC2 and RDS instances
- Created backup plans with retention policies
- Successfully tested restore procedures
- Verified backup compliance and recovery time objectives
Storage Gateway Configuration (Lab 24):
- Deployed File Gateway on EC2 instance
- Connected on-premises applications to S3 via NFS/SMB
- Configured file shares with appropriate permissions
- Tested hybrid cloud storage workflows
Static Website Hosting (Lab 57):
- Configured S3 bucket for static website hosting
- Implemented CloudFront for global content delivery
- Enabled versioning for content rollback capability
- Set up cross-region replication for disaster recovery
- Optimized costs by blocking direct S3 public access
Auto Scaling:
- Configured Launch Templates with proper AMI and instance settings
- Created Auto Scaling Groups with min/max/desired capacity
- Set up scaling policies based on CloudWatch metrics
- Tested scale-out and scale-in behaviors
Challenges Encountered:
- Instance Type Selection: Confused between T3 and T3a instances → Learned T3a uses AMD processors at lower cost
- User Data Execution: Script didn’t run on first boot → Added proper shebang (
#!/bin/bash) and verified logs in /var/log/cloud-init-output.log - Backup Restore Time: RDS restore took longer than expected → Understood that larger databases require more time for restoration
- Storage Gateway Activation: Gateway failed to activate → Ensured proper security group rules for ports 80, 443, 1026-1028, 2049
- CloudFront Propagation: Distribution took 15-20 minutes to deploy → Learned this is normal for global edge location updates
- S3 Versioning Costs: Noticed increased storage costs → Implemented lifecycle policies to delete old versions after 30 days
- Auto Scaling Delays: Instances took time to become healthy → Adjusted health check grace period to 300 seconds
References:
AWS Official Documentation:
AWS Workshops & Labs:
Technical Articles: