Over the past few days, I designed and deployed a personal cloud environment on AWS using Terraform, allowing me to connect the dots between infrastructure as code, automation, and cloud architecture. What I implemented: - VPC with a /26 CIDR block for scalability - Public subnet with Internet Gateway - EC2 instance with IAM role-based access (no static credentials) - Security Group with restricted SSH access - Terraform installed on EC2 for infrastructure management To validate the setup, I successfully provisioned an S3 bucket directly from the instance using Terraform. This project is designed to evolve — next steps include adding private subnets, RDS, and serverless components like Lambda, SNS, and SQS. 💻 Check out the code here: https://lnkd.in/e_6EnV3T #AWS #Terraform #CloudComputing #DevOps #InfrastructureAsCode #CloudEngineering
If you want to connect to your ec2 via ssh use AWS SSM instead. In that case, you don't need to open any ports to the public. This is best practice
What would you do if your /26 VPC runs out of space? at /26 you have about 64 hosts (well 62 since you have a gateway and broadcast address needed normally). You're app could sell well and then you have a flood of traffic that would really challenge your infrastructure then. Otherwise, very cool!