So, the following architecture is a good start to get started with AWS Infrastructure: It has a V...So, the following architecture is a good start to get started with AWS Infrastructure: It has a V...
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
shivansh's avatar
shivansh sukhija
• Jan 6
So, the following architecture is a good start to get started with AWS Infrastructure:
It has a VPC ( Virtual Private Connection ) and has 3 subnets.
Public Subnet which has NAT Gateway, a Jump Server and an Application load balancer.
1st Private Subnet has a Jenkins CI/CD Server and 3 Application Server.
2nd Private Subnet has a database with a standby database.
Jump Server (Bastian Server) is being used to access the Application Server so we could configure it, and by configure it I mean you can access your Servers only through the Jump Server that’s the purpose of it.
User can access the application through the S3 Frontend which is connected to the CDN called Cloudfront which redirects the request towards the load balancer and load balancer redirects the request towards the Application server.
Cloud InfrastructureAWS
Post image
shivansh's avatar
shivansh sukhija
• Jan 6
First spin up the server there you need to pull your Git repository, install Docker. create an image of the following application or if your application is in the Docker registry already pull it. and create an image of the Application server. Now go to the auto scaling group,...
Back to feed
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started