![]() Accessing private resources using AWS Client VPN.Step (2) pretty much like connecting to remote server, but in this case both the EC2s are in the same ![]() This corresponds to step (1) and (2) in the below diagram. To connect to the EC2 in the private subnet we need to launch a Bastion box in the public subnet, connect to it and from there connect to the EC2 in the private subnet. So, how do we connect to it for activities like updating databases, creating tables etc? This is where Jump box or the Bastion box comes into play. This EC2 can't be reached directly from outside the Cloud as it doesn't have any public IP. The private subnet EC2 will have only private IP and no public IP, backend applications like databases ore installed on this EC2. Also, this EC2 can be reached from outside the Cloud using the public IP for any maintenance. Any EC2 in the public subnet will have public and private IP and so front end or customer facing applications like web applications are installed on this EC2. ![]() AWS VPC supports creating public and private subnets.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |