Scribd
Upload
79 views12 pages

Multi-Region AWS Infrastructure Deployment Using Terraform

The document outlines a multi-region AWS infrastructure deployment using Terraform, covering regions in US East (Ohio) and EU West (Ireland). Each region is equipped with EC2 instances, NAT gateways, application load balancers, and other essential components to ensure high availability and fault tolerance. The infrastructure is fully automated and managed through Terraform, with resources provisioned identically across both regions for service continuity.

Uploaded by

Madhavi M
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
79 views12 pages

Multi-Region AWS Infrastructure Deployment Using Terraform

The document outlines a multi-region AWS infrastructure deployment using Terraform, covering regions in US East (Ohio) and EU West (Ireland). Each region is equipped with EC2 instances, NAT gateways, application load balancers, and other essential components to ensure high availability and fault tolerance. The infrastructure is fully automated and managed through Terraform, with resources provisioned identically across both regions for service continuity.

Uploaded by

Madhavi M
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 12

🚀 Multi-Region AWS Infrastructure

Deployment
Multi-Region AWS Infrastructure Deployment using Terraform

👤 Submitted by: Utsav Patel​


📅 Date: June 2025
📌 Project Architecture Diagram
This diagram visually represents the multi-region AWS infrastructure built using Terraform.
Each region (US East and EU West) includes:

●​ Two Availability Zones​

●​ Public and Private Subnets​

●​ EC2 Instances behind Application Load Balancers​

●​ NAT Gateways for private subnet internet access​

●​ VPC peering via AWS Transit Gateway


●​ This project demonstrates how to build a highly available, fault-tolerant, and
automated infrastructure on AWS using Terraform. We provisioned identical
resources across two regions:

●​ 🌎 US East (Ohio) – us-east-2​


●​ 🌍 Europe (Ireland) – eu-west-1​
This setup ensures service continuity even if one region becomes unavailable.

🌎 Region: US East (Ohio)


• EC2 Instances

●​ 2 running (t2.micro)​
●​ Availability Zones: us-east-2a, us-east-2b​

●​ ✅ Health checks passed​

• Elastic IPs (EIP)

●​ 3.135.5.185, 3.140.149.208​
●​ Reserved for NAT Gateways (Not associated)​

• Key Pairs

●​ key1, utsav_east2
• Load Balancer

●​ Name: tf-lb-20250618060609300000000001​

●​ Type: Application Load Balancer​

●​ Status: ✅ Active​
●​ Spread across 2 AZs​

• Network Interfaces

●​ Distributed across private/public subnets​


●​ Managed by Terraform​

• Security Groups

●​ Group Names: us-east-web-sg, us-east-alb-sg​

●​ Attached to EC2, ALB, NAT Gateway​


• Target Groups

●​ Name: tf-20250618060558030000000001​

●​ Protocol: HTTP | Port: 80 | Type: Instance​

• EBS Volumes

●​ 2 Volumes (gp2, 8 GiB each)​

●​ Snapshots created on launch​


🌍 Region: Europe (Ireland)
• EC2 Instances

●​ 2 running (t2.micro)​

●​ Availability Zones: eu-west-1a, eu-west-1b​

●​ ✅ Health checks passed​


• Elastic IPs (EIP)

●​ 18.203.41.16, 54.247.69.94​

●​ Reserved for NAT Gateways​

• Key Pair
●​ utsav_eu​

• Network Interfaces

●​ Attached in AZs eu-west-1a, eu-west-1b​

●​ Managed

by Terraform​
• Security Groups

●​ Group Names: eu-west-web-sg, eu-west-alb-sg​

●​ Properly attached to services​

• Target Groups

●​ Name: tf-20250618060602180000000001​
●​ Protocol: HTTP | Port: 80 | Type: Instance​

✅ Summary & Next Steps


●​ ✅ Two AWS regions deployed (Ohio & Ireland)​
●​ 📌 Each region includes EC2, EIPs, NAT, ALB, and target groups.​
●​ 🔁 All resources are provisioned with Terraform

You might also like