diff --git a/pages/vpc/assets/scaleway-create-vpc.webp b/pages/vpc/assets/scaleway-create-vpc.webp new file mode 100644 index 0000000000..2ba4aa6bd4 Binary files /dev/null and b/pages/vpc/assets/scaleway-create-vpc.webp differ diff --git a/pages/vpc/assets/scaleway-vpc-basics.webp b/pages/vpc/assets/scaleway-vpc-basics.webp new file mode 100644 index 0000000000..73486cac13 Binary files /dev/null and b/pages/vpc/assets/scaleway-vpc-basics.webp differ diff --git a/pages/vpc/quickstart.mdx b/pages/vpc/quickstart.mdx index a0aae960b6..0ad21c57f4 100644 --- a/pages/vpc/quickstart.mdx +++ b/pages/vpc/quickstart.mdx @@ -7,17 +7,29 @@ content: paragraph: This page shows you how to get started with Scaleway Virtual Private Cloud (VPC). tags: vpc virtual-private-cloud regional private network dhcp private-ip dates: - validation: 2025-02-20 + validation: 2025-04-24 posted: 2022-02-06 categories: - network --- -VPC allows you to build your own **V**irtual **P**rivate **C**loud on top of Scaleway's shared public cloud. One default VPC per region is automatically created per Scaleway [Project](/organizations-and-projects/concepts/#project), and you can create more if you wish. Within each VPC, you can create **Private Networks** and attach Scaleway resources (Instances, Elastic Metal servers, Load Balancers etc.) to them, as long as the resources are within the network's region. +VPC allows you to build your own **V**irtual **P**rivate **C**loud on top of Scaleway's shared public cloud. - +One **default VPC** per region is automatically created per Scaleway [Project](/organizations-and-projects/concepts/#project), and you can create more VPCs if you wish. -Attached resources can then communicate between themselves in an isolated and secure virtual layer 2 network, away from the public internet. More features and resources will be coming to the VPC product in the future. +Within each VPC, you can create **Private Networks** and attach Scaleway resources (Instances, Elastic Metal servers, Load Balancers etc.) to them, as long as the resources are within the network's region. Resources attached to a Private Network can communicate between themselves in an isolated and secure virtual layer 2 network, away from the public internet. + +**VPC routing** facilitates the automatic routing of traffic between the Private Networks of a VPC, as well as the ability to define custom routes between resources. Finely control and limit routing between resources in a VPC via the Network Access Control List (currently available only via the VPC API). + +Attach a **Public Gateway** to your VPC to give your resources controlled access to the public internet via the Private Network. + + + +This quickstart walks you through the process of getting started with Scaleway VPC. + + +If you are looking for detailed guidance on constructing your private infrastructure according to best practices, see our [basic VPC use case](/vpc/reference-content/use-case-basic/) and [Getting the most from Private Networks](/vpc/reference-content/getting-most-private-networks/) documentation. + @@ -37,13 +49,35 @@ You see three default VPCs, one for each of the following regions: - Amsterdam `AMS` - Warsaw `WAW` -Any new Private Networks that you create will be added to the default VPC for their region, unless you override this by specifying a different VPC. +Any new Private Networks that you create will be added to the default VPC for their region, unless you override this by [creating](#how-to-create-a-vpc) and specifying a different VPC. + +## How to create a VPC + +If you want to create more VPCs beyond the default ones created for you, you can do so via the following steps: + +1. Click **VPC** in the **Network** section of the Scaleway console side menu. + +2. Click **Create a VPC**. The VPC creation wizard displays. + + + +3. Choose a **region** in which to create your VPC. + +4. Enter a **name** for your VPC (or use the wand icon to generate a random name). Optionally, you can also add **tags** to help organize your VPCs. Each tag should be separated by a space. + + + + You can create Private Networks in this VPC after you have created the VPC itself. However, you can not move an existing Private Network from one VPC to another. + +5. Click **Create VPC** to finish. + + Your VPC is created, and you are redirected to its **Overview** page. ## How to create a Private Network -1. Click **VPC** in the **Network** section of the side menu. The list of your VPCs displays: +You can create multiple Private Networks within each VPC. Resources attached to each Private Network will be able to communicate between themselves via their private IP addresses or private hostnames, away from the public internet. - Each Private Network must be created within a VPC. +1. Click **VPC** in the **Network** section of the side menu. The list of your VPCs displays. 2. Click the VPC you wish to create your Private Network in. @@ -61,11 +95,11 @@ Any new Private Networks that you create will be added to the default VPC for th 5. Click **Create Private Network** to finish. Your Private Network is created. -1. Click **VPC** in the **Network** section of the side menu. Your VPC [dashboard](https://console.scaleway.com/vpc/vpc) displays: +## How to attach resources to a Private Network -2. Click the VPC containing the Private Network to which you want to attach a resource. +1. Click **VPC** in the **Network** section of the side menu. Your VPC [dashboard](https://console.scaleway.com/vpc/vpc) displays. - A list of Private Networks in this VPC displays: +2. Click the VPC containing the Private Network to which you want to attach a resource. A list of Private Networks in this VPC displays. 3. Click the Private Network to which you want to attach a resource. @@ -119,9 +153,25 @@ Any new Private Networks that you create will be added to the default VPC for th You are returned to the list of attached resources, where the newly-attached resource now displays. - - **Viewing the resource's private IP**: When you attach a resource to a Private Network, it gets a private IPv4 address on that network (and also an IPv6 address, if supported by the resource). Private IPs are assigned from the CIDR block defined at the time of the Private Network's creation, either via auto-assignment or specification of a particular [reserved IP](/ipam/how-to/reserve-ip/). You can view a resource's IPv4 or v6 address in the **Attached Resources** tab of the Private Network itself (follow steps 1 - 5 above). It can also be viewed via the **Private Networks** tab of the resource's own dashboard. - +## How to address resources on a Private Network + +Resources on a Private Network can be addressed via their **private IP address** or their **hostname**. + +### Private IP address + +When you attach a resource to a Private Network, it gets a private IPv4 address on that network (and also an IPv6 address, if supported by the resource). + +Private IPs are assigned from the CIDR block defined at the time of the Private Network's creation, either via auto-assignment or specification of a particular [reserved IP](/ipam/how-to/reserve-ip/). + +You can view a resource's IPv4 or v6 address in the **Attached Resources** tab of the Private Network itself (follow steps 1 - 5 above). It can also be viewed via the **Private Networks** tab of the resource's own dashboard. + +### Hostname + +In addition to using its private IP address, you can also access a resource on a Private Network via its hostname, thanks to VPC’s inbuilt private DNS. + +A resource’s hostname is equivalent to the name you gave the resource when creating it. For example, if you have an Instance with the name `instance123` attached to a Private Network named `prodpn`, its address on that network is `instance123.prodpn.internal`. The `.internal` is important to allow Scaleway DNS to distinguish public and private hostnames. + +For full information on Scaleway internal DNS and hostname formats, including troubleshooting advice, see our [dedicated DNS documentation](/vpc/reference-content/dns/). ## How to manage routing @@ -143,11 +193,15 @@ When your route table starts to populate, it will look something like this: -For help with understanding the route table and how to read it, refer to our documentation about route tables. + +For help with understanding the route table, refer to our full [routing documentation](/vpc/reference-content/understanding-routing/). For guidance on creating custom routes, see the [routing how-to](/vpc/how-to/manage-routing/#how-to-create-a-custom-route). + + +You can use the VPC's **N**etwork **A**ccess **C**ontrol **L**ist to limit and restrict certain routes within a VPC, but this feature is currently available via the [VPC API only](/vpc/reference-content/understanding-nacls/) only. ## How to delete a Private Network -You must [detach](/vpc/how-to/attach-resources-to-pn/#how-to-detach-a-resource-from-a-private-network) all resources from the Private Network before you can delete it. +You must [detach](/vpc/how-to/attach-resources-to-pn/#how-to-detach-a-resource-from-a-private-network) all resources and release all reserved IPs from the Private Network before you can delete it. 1. Click **VPC** in the **Network** section of the side menu. @@ -169,4 +223,8 @@ You must [detach](/vpc/how-to/attach-resources-to-pn/#how-to-detach-a-resource-f 4. Type **DELETE** and click **Delete Private Network**. - Your Private Network is deleted. \ No newline at end of file + Your Private Network is deleted. + + + If you encounter errors when attempting to delete a Private Network, see our [troubleshooting guide](/vpc/troubleshooting/cant-delete-vpc-pn/). + \ No newline at end of file