A new solution tutorial covering virtual private cloud with public and private subnets.
We're excited to announce our new tutorial covering a scenario that includes a virtual private cloud (VPC) with a public subnet installed with an outward facing web server and a private subnet with a restricted access backend database.
This post is an excerpt from the latest solution tutorial covering public and private subnets. In a virtual private cloud (VPC) scenario, you may want to use the public subnet for resources that must be exposed to the outside world (such as a web server) and the private subnet for resources with restricted access that should never be directly accessed from the outside world. Instances on such a subnet could be your backend database or some secret store that you do not want to be publicly accessible. You will define security groups to allow or deny traffic to the virtual server instances.
Following the instructions in the tutorial will allow you to do the following:
- Understand the infrastructure objects available for virtual private clouds.
- Learn how to create a virtual private cloud, subnets, and server instances.
- Know how to apply security groups to secure access to the servers.
Follow the steps mentioned in securely access remote instances with a bastion host for secured maintenance of the servers, such as installing a web server like Nginx or Lynx on the public subnet and a database like MySQL or Db2 on the private subnet, using a bastion host which acts as a
jump server and a maintenance security group.
Comments, suggestions, and ideas for future tutorials
The tutorials section has a feedback form on the side where you can comment on the content. If you have suggestions on the existing tutorials or ideas for future additions, please submit your feedback.