Skip to content

Implementation of own secure architecture on AWS Cloud. Creating own Public and Private Subnet and launching front-end application on Public and backend database on private subnet.

License

Notifications You must be signed in to change notification settings

raktim00/AWS-WordPress

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

6 Commits
 
 
 
 
 
 

Repository files navigation

The Full procedure of doing this practical you can find in below link :

“Secure Architecture on AWS ( Hosting WordPress on Public and Database on Private Subnet )” by Raktim Midya - https://link.medium.com/7R7TZnmfbab

Problem Statement :

We have to create a web portal for our company with all the security as much as possible.

So, we use WordPress software with dedicated database server.Database should not be accessible from the outside world for security purposes. We only need to public the WordPress to clients.

So here are the steps for proper understanding!

    1. Write an Infrastructure as code using terraform, which automatically create a VPC.
    1. In that VPC we have to create 2 subnets:
    1. public subnet - Accessible for Public World!
    1. private subnet - Restricted for Public World!
    1. Create a public facing internet gateway for connect our VPC/Network to the internet world and attach this gateway to our VPC.
    1. Create a routing table for Internet gateway so that instance can connect to outside world, update and associate it with public subnet.
    1. Create a NAT gateway for connect our VPC/Network to the internet world and attach this gateway to our VPC in the public network
    1. Update the routing table of the private subnet, so that to access the internet it uses the NAT gateway created in the public subnet
    1. Launch an ec2 instance which 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 instance for further login into it.
    1. Launch an ec2 instance which has MYSQL setup already with security group allowing port 3306 in 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 public subnet so that our client can connect our site. MySQL instance has to be part of private subnet so that outside world can’t connect to it.
Don’t forgot to add auto ip assign and auto dns name assignment option to be enabled.

About

Implementation of own secure architecture on AWS Cloud. Creating own Public and Private Subnet and launching front-end application on Public and backend database on private subnet.

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages