Deploying Infrastructure of WordPress and MySql in self-created VPC with self-created resources

Deploying Infrastructure of WordPress and MySql in self-created VPC with self-created resources

TASK4 DESCRIPTION

1. Write an Infrastructure as code using Terraform, which automatically creates a VPC.

2. In that VPC we have to create 2 subnets:

  1.  public subnet [ Accessible for Public World! ] 

  2.  private subnet [ Restricted for Public World! ]

3. Create a public-facing internet gateway to connect our VPC/Network to the internet world and attach this gateway to our VPC.

4. Create a routing table for Internet gateway so that instance can connect to the outside world, update and associate it with the public subnet.

5. Create a NAT gateway for connecting our VPC/Network to the internet world and attach this gateway to our VPC in the public network

6. Update the routing table of the private subnet, so that to access the internet it uses the nat gateway created in the public subnet

7. Launch an ec2 instance that has WordPress setup already having the security group allowing port 80 so that our client can connect to our WordPress site. Also, attach the key to the instance for further login into it.

8. Launch an ec2 instance that has MYSQL setup already with security group allowing port 3306 in a private subnet so that our WordPress VM can connect with the same. Also, attach the key with the same.

Note: WordPress instance has to be part of the public subnet so that our client can connect our site. MySQL instance has to be part of a private subnet so that the outside world can't connect to it.

STEP 1: Write an Infrastructure as code using Terraform, which automatically creates a VPC.

No alt text provided for this image
No alt text provided for this image

STEP 2: Create 2 subnets: (a) public subnet [ Accessible for Public World! ], and (b)  private subnet [ Restricted for Public World! ]

No alt text provided for this image
No alt text provided for this image

STEP 3: Create a public-facing internet gateway

No alt text provided for this image
No alt text provided for this image

STEP 4: Create a routing table for Internet gateway

No alt text provided for this image

STEP 5: Create a NAT gateway for connecting our VPC/Network to the internet world and attach this gateway to our VPC in the public network. Update the routing table of the private subnet, so that to access the internet it uses the nat gateway created in the public subnet

No alt text provided for this image
No alt text provided for this image

STEP 6: Launch an ec2 instance that has WordPress setup already having the security group allowing port 80 so that our client can connect to our WordPress site. Also, attach the key to the instance for further login into it.

No alt text provided for this image
No alt text provided for this image
No alt text provided for this image

STEP VII:  Launch an ec2 instance that has MYSQL setup already with security group allowing port 3306 in a private subnet so that our WordPress VM can connect with the same. Also, attach the key with the same.

No alt text provided for this image
No alt text provided for this image
No alt text provided for this image

OUTPUT :

No alt text provided for this image

Thus, it is completed!

REMEMBER: All the steps are written as a code in a .tf file and executed using terraform apply cmd using CLI.

To view or add a comment, sign in

More articles by Ruchi Verma

Others also viewed

Explore content categories