Create a Virtual Private Cloud¶
We advise you to create a new Virtual Private Cloud for these labs
These labs assume you are starting with an account that has no Virtual Private Cloud (VPC) resources defined when you start the lab. If your account has existing VPC resources then it is up to you to decide whether to use those existing resources when available or whether to create new resources for all parts of the labs. Using existing resources may help to avoid incurring costs, but at the risk of inadvertently impacting existing users of these resources- an essential consideraton if these resources are being used in production! You'd also have to take extra care when deleting resources at the end of the labs.
Navigate to IBM Cloud and log in to the IBM Cloud Web UI.
Click on the Navigation Menu icon (often informally referred to as the "hamburger" icon) in the upper left of the IBM Cloud Web UI. From there, navigate to VPC Infrastructure and VPC Layout as shown here:
The labs are written with the assumption that all resources used for the labs are created in the lab and then deleted at the end of the lab. You'll have to tailor your implementation of the lab directions appropriately if you do use existing resources.
Here's a screen snippet showing the VPC Layout screen when the account has no existing VPC infrastructure at the start of the labs:
Click the Create a VPC link.
Choose one of the following six locations which support Hyper Protect Virtual Server for IBM Cloud VPC: London, Madrid, Sao Paulo, Tokyo, Toronto or Washington, D.C. These labs' instructions and screen snippets will show the Washington, D.C. region (us-east) in use, but you may use one of the other aforementioned regions as well- tailor your implementation of the directions appropriately if you do.
The screen snippet below shows after we've chosen the Washington DC region in the North America geography and given the new VPC the name lab-was-vpc. Throughout the labs we will often be using the naming convention lab-region-resource type-optional description. If you perform the lab in the Washington, D.C., region you will be able to use the instructions almost verbatim. If you choose to use another region you can choose to use our naming convention and tailor the
Scroll down to see the list of subnets offered to you- by default you will be offered three subnets- one for each of the three availability zones within a region. For our labs, in an effort to minimize costs, we've deleted two of the three subnets as we will limit our lab activities to a single availability zone. If you wish to do likewise then click the rightmost icon of the two subnets you want to get rid of, as indicated in the below screen snippet:
Your subnet section will look similar to this if you choose to work with only one subnet:
You are now ready to click the blue Create virtual private cloud button on the lower right of your page. If this button is not enabled then you probably forgot to enter some required information such as a name for your VPC:
After clicking the button, your new VPC will be created and you'll be taken to a screen like this. Notice that a Default Access Control List (ACL) and a Default Security Group will be created for you, both of which will have meaningless randomly-generated names. You can accept them as-is for the labs.
Click the Next link at the lower right of this page so you can move to the next section where you will create a public gateway within your new VPC.
Created: June 2, 2023