Create a Virtual Cloud Network (VCN)
Create a virtual cloud network (VCN) to provide a private, customizable cloud network.
You can manually create the VCN and its features or you can use the networking quickstart option to set up a VCN with the necessary gateways, a public subnet, a private subnet, routing tables, and security lists.
You can add subnets and security rules as necessary. For example, you can use the provisioned private subnet for the Function service, and create a second private subnet to house the database.
Use a Wizard to Create a Virtual Cloud Network
You can use a predefined workflow to quickly create a virtual cloud network (VCN) with internet connectivity.
The wizard creates a virtual cloud network contains with the following elements:
-
An internet gateway, a NAT gateway, and a service gateway for the VCN
-
A regional public subnet with routing to the internet gateway
Instances in a public subnet may optionally have public IP addresses.
-
A regional private subnet with routing to the NAT gateway and service gateway (and therefore the Oracle Services Network)
Instances in a private subnet cannot have public IP addresses.
- Basic security list rules for the two subnets, including SSH access
To use the wizard to create a virtual cloud network:
- In the Console, click the Oracle Cloud icon at the top of the page to go to the Console home page.
- Click the quick action for Networking: Set up a network with a wizard.
- Select VCN with Internet Connectivity, and then click Start Workflow.
- Specify a friendly name for the VCN. It doesn't have to be unique, however it can't be changed later in the Console (but you can change it with the API). Avoid entering confidential information.
- Use the default Compartment or select a different compartment.
- Use the default CIDR blocks listed for the VCN and subnets, or specify a different range.
- Click Next.
- Review the information and click Previous to make changes or click Create to create the VCN.
Create a Private Subnet
Create a private subnet to house resources for which you do no want to provide access through public IP addresses.
Subnets act as a unit of configuration within the virtual cloud network (VCN). All virtual network interface cards (VNICs) in a given subnet use the same route table, security lists, and DHCP options. When you designate a subnet as private, VNICs in the subnet can't have public IP addresses.