A comprehensive AWS infrastructure project built with AWS CDK (Cloud Development Kit) in TypeScript, implementing a three-tier architecture with VPC, EC2, and RDS components following AWS best practices.

• 🎯 Project Overview
• 🏗️ Architecture
• 🔧 Components
• 💰 Cost Estimation
• 🚀 Getting Started
• 📦 Deployment
• 🔐 Security Features
• 📊 Monitoring & Management
• 🧹 Cleanup
• 📚 Learning Resources

This project demonstrates the implementation of a scalable three-tier web architecture on AWS using Infrastructure as Code (IaC) principles. The architecture includes:

• Presentation Tier: Public subnets for load balancers and web servers
• Application Tier: Private subnets for application servers (EC2 instances)
• Data Tier: Isolated database subnets for RDS MySQL instances

• 🌐 Multi-AZ VPC with proper subnet segmentation
• 🖥️ EC2 instances in private subnets for security
• 🗄️ MySQL RDS database in isolated subnets
• 🔒 Security best practices implemented throughout
• 📊 Performance monitoring with CloudWatch integration
• 🏷️ Comprehensive tagging for resource management
• 💾 Automated backups and disaster recovery planning

┌─────────────────────────────────────────────────────────────┐
│                        AWS VPC                             │
│  ┌─────────────────┐  ┌─────────────────┐                 │
│  │  Availability   │  │  Availability   │                 │
│  │    Zone A       │  │    Zone B       │                 │
│  │                 │  │                 │                 │
│  │ ┌─────────────┐ │  │ ┌─────────────┐ │ Public Tier     │
│  │ │   Public    │ │  │ │   Public    │ │ (Load Balancer) │
│  │ │   Subnet    │ │  │ │   Subnet    │ │                 │
│  │ └─────────────┘ │  │ └─────────────┘ │                 │
│  │                 │  │                 │                 │
│  │ ┌─────────────┐ │  │ ┌─────────────┐ │ Private Tier    │
│  │ │   Private   │ │  │ │   Private   │ │ (EC2 App        │
│  │ │   Subnet    │ │  │ │   Subnet    │ │  Servers)       │
│  │ └─────────────┘ │  │ └─────────────┘ │                 │
│  │                 │  │                 │                 │
│  │ ┌─────────────┐ │  │ ┌─────────────┐ │ Database Tier   │
│  │ │  Database   │ │  │ │  Database   │ │ (RDS MySQL)     │
│  │ │   Subnet    │ │  │ │   Subnet    │ │                 │
│  │ └─────────────┘ │  │ └─────────────┘ │                 │
│  └─────────────────┘  └─────────────────┘                 │
└─────────────────────────────────────────────────────────────┘

Purpose: Creates the foundational network infrastructure

Resources Created:

• ✅ VPC with DNS resolution enabled
• ✅ Internet Gateway for public internet access
• ✅ Public subnets across 2 Availability Zones
• ✅ Private isolated subnets for applications
• ✅ Database subnets for RDS placement
• ✅ Route tables and security configurations

Key Features:

• Multi-AZ deployment for high availability
• Proper subnet segregation following AWS best practices
• CIDR planning for future scalability

Purpose: Deploys application servers in private subnets

Resources Created:

• ✅ EC2 instances in private subnets
• ✅ Security groups with restricted access
• ✅ IAM roles and policies
• ✅ Auto-scaling capabilities (if configured)

Security Configuration:

• No direct internet access (private subnet placement)
• Controlled communication via security groups
• IAM role-based permissions following least privilege principle

Purpose: Provides managed MySQL database service

• 🔐 AWS Secrets Manager integration for credential management
• 📊 Performance Insights enabled (7-day retention)
• 🔍 Enhanced Monitoring with 60-second intervals
• ⚙️ Custom Parameter Group for MySQL optimization
• 🏷️ Comprehensive tagging for resource management

-- InnoDB Buffer Pool optimized for t3.micro
innodb_buffer_pool_size = 75% of instance memory (~750MB)

💡 Free Tier Eligible: New AWS accounts can run this architecture within the free tier limits for 12 months!

• ✅ AWS Account with appropriate permissions
• ✅ AWS CLI configured with credentials
• ✅ Node.js (16.x or later)
• ✅ AWS CDK installed globally
• ✅ Git for version control

1. Clone the repository

git clone <git@github.com:TopCoderJP/AWS-CDK-Automation-Typescript.git>
cd vpc-cdk-project

2. Install dependencies

npm install

3. Configure AWS credentials

aws configure
# Enter your Access Key ID, Secret Access Key, Region, and Output format

4. Bootstrap CDK (first time only)

cdk bootstrap

vpc-cdk-project/
├── bin/
│   └── vpc-cdk-project.ts          # Main app entry point
├── lib/
│   ├── vpc-cdk-project-stack.ts    # VPC infrastructure
│   ├── ec2-stack.ts                # EC2 instances
│   └── rds-stack.ts                # RDS database
├── package.json                    # Dependencies
├── tsconfig.json                   # TypeScript config
└── README.md                       # This file

1. Validate the code

npm run build

2. Preview changes

cdk diff

3. Deploy all stacks

cdk deploy --all

Or deploy individually:

cdk deploy VpcCdkProjectStack  # Deploy VPC first
cdk deploy MyEC2Stack          # Deploy EC2 instances
cdk deploy MyRDSStack          # Deploy RDS database

After successful deployment, you'll receive:

• 🌐 VPC ID: For reference in other projects
• 🔗 RDS Endpoint: Database connection string
• 🔑 Secret ARN: Database credentials location
• 🆔 Database Identifier: RDS instance identifier

• 🛡️ Private Subnets: Application servers isolated from internet
• 🔒 Database Isolation: RDS in dedicated isolated subnets
• 🚪 Security Groups: Controlled traffic flow between tiers
• 🔐 NACLs: Additional network-level security (if configured)

• 🔐 Encryption at Rest: All RDS storage encrypted
• 🔑 Secrets Management: Database credentials in AWS Secrets Manager
• 🔄 Automated Rotation: Credential rotation capabilities
• 📋 IAM Policies: Least privilege access controls

• 🏷️ Resource Tagging: For governance and cost tracking
• 📊 CloudTrail Integration: API call logging (if enabled)
• 🔍 VPC Flow Logs: Network traffic monitoring (if enabled)

• 📈 Performance Insights: Database performance monitoring
• ⚠️ CloudWatch Alarms: Automated alerting (configurable)
• 📊 Custom Metrics: Application-specific monitoring
• 📝 Log Aggregation: Centralized logging

• 💾 Automated Backups: Daily RDS snapshots
• 🔄 Point-in-time Recovery: 7-day retention window
• 📦 Manual Snapshots: On-demand backup capability
• 🌍 Cross-region Backup: (Configurable for production)

# Destroy all stacks (be careful!)
cdk destroy --all

cdk destroy MyRDSStack         # Remove database first
cdk destroy MyEC2Stack         # Remove EC2 instances
cdk destroy VpcCdkProjectStack # Remove VPC last

⚠️ Warning: This will permanently delete all resources and data. Ensure you have backups if needed!

• 📖 AWS CDK Developer Guide
• 🌐 VPC Best Practices
• 🗄️ RDS Best Practices
• 🖥️ EC2 Best Practices

• 🏗️ AWS Well-Architected Framework
• 🔄 Three-Tier Architecture Pattern
• 🌐 Multi-AZ Deployments

• 💻 CDK Patterns
• 🎯 CDK Workshop
• 📚 TypeScript CDK Examples

1. Fork the repository
2. Create a feature branch (git checkout -b feature/amazing-feature)
3. Commit your changes (git commit -m 'Add amazing feature')
4. Push to the branch (git push origin feature/amazing-feature)
5. Open a Pull Request

Built with ❤️ by Topcoder using AWS CDK and TypeScript