AWS Infrastructure as Code

Define Cloud Infrastructure and Reusable Components Using AWS CloudFormation

This lab was built around a FinTechBuddy scenario and focused on defining cloud infrastructure in code instead of building it by hand. The goal was to use CloudFormation and StackSets to provision reusable networking and application components across multiple AWS regions.

Core tasks

The work started by creating the administration and execution roles needed for AWS CloudFormation. After the IAM roles were in place, the next step was to create a networking StackSet and then build the application infrastructure stack on top of it.

The application layer used CloudFormation StackSets to provision public EC2 instances in both Northern Virginia and Oregon. That made the deployment more repeatable and showed how reusable components help standardize infrastructure across regions.

Update and improvement

The lab also included an update step where the EC2 instance type was changed from t2.micro to t2.small. That part stood out because it showed the value of Infrastructure as Code pretty clearly. Instead of rebuilding everything manually, the template could be revised and the stack could be updated in a controlled way.

Why it matters

This project reinforced the idea that cloud work is stronger when it is repeatable, documented, and easy to update. For security and operations roles, that kind of consistency matters.