shubham0297 / aws_cloudformation-deploying_highly_available_webapp Goto Github PK

In this project, I deployed a sample application to to the Apache Web Server running on EC2 instances inside a Private Subnet using the CloudFormation Template ie. Infrastructure as a Code. Some of the properties used in this project are as follows :

(back to top)

Following is the Architecture Diagram of the Infrastructure that was deployed using the CloudFormation Template 👇

(back to top)

(back to top)

(back to top)

Here are the steps needed to successfully finish this project.

1. AWS account: You would require to have an AWS account to be able to build cloud infrastructure.
2. AWS CLI - You need to have AWS CLI installed and profile configured in order to run the AWS commands. You can download the AWS-CLI here
3. VS code editor: This editor is helpful to visualize image as well as the code. You can download VS Code editor here
4. An account on LucidChart: In order to draw the Architecture Diagrams, you need to have a user account on Lucid Chart

1. Create Script

# Ensure that the AWS CLI is configured before running the command below
./create.sh stackName templateFile.yml variableFile.json

2. Update Script

# Ensure that the AWS CLI is configured before running the command below
./update.sh stackName templateFile.yml variableFile.json

3. Delete Script

# Ensure that the AWS CLI is configured before running the command below
./delete.sh stackName

1. Creating Network Stack.
   Firstly, we create the Network stack using the following command :

# Ensure that the AWS CLI is configured before running the command below
./create.sh networkStack network.yml parameters-network.json

# This should give back the ARN of the created Stack

2. Creating Server Stack.
   Once network stack is created, we then create the server stack which using some of the resources created in the Network Stack.

# Ensure that the AWS CLI is configured before running the command below
./create.sh serverStack servers.yml parameters-server.json

# This should give back the ARN of the created Stack

(back to top)

• Once both the stacks are created, we can use the LoadBalancer DNS Name to access the website that is deployed on the EC2 instances in private subnets.
• To demonstrate the working of LoadBalancer, I have displayed the Private IP of the webserver on the top of the page.
• We can see that the IP address is changing which shows that the LoadBalancer is distributing the traffic across all the web servers 👇

(back to top)

Name: Shubham Kandwal
Email: [email protected]
Project Link: Deploying_Highly_Available_WebApp_Using_CloudFormation

(back to top)