feat(vpc): add use case final doc

Author: RoRoJ

menu/navigation.json

@@ -2919,6 +2919,10 @@
                   {
                     "label": "Getting the most from Private Networks",
                     "slug": "getting-most-private-networks"
+                  },
+                  {
+                    "label": "VPC use case 1: basic infrastructure",
+                    "slug": "use-case-basic"
                   }
                 ],
                 "label": "Additional Content",

network/vpc/how-to/create-private-network.mdx

@@ -48,6 +48,10 @@ While DHCP is built into all new Private Networks, it may not be automatically a
 
 6. Click **Create Private Network** to finish. Your Private Network is created.
 
+<Message type="tip">
+See our [Basic VPC use case](/network/vpc/reference-content/use-case-basic/) documentation for full details of how to create a simple infrastructure that leverages the advantages of Private Networks, including accompanying Terraform templates.
+</Message>
+
 ## How to configure CIDR
 
 Private Networks have built-in **D**ynamic **H**ost **C**onfiguration **P**rotocol (DHCP). DHCP manages the allocation of private IP addresses to resources attached to the network. For this purpose, a **C**lassless **I**nter-**D**omain **R**outing (CIDR) block is defined for each Private Network, from which IP addresses will be assigned. In fact, both an IPv4 and an IPv6 CIDR block are defined.

network/vpc/index.mdx

@@ -6,9 +6,11 @@ meta:
 
 <Alert
   sentiment="info"
-  title="Getting the most from your Private Networks"
+  title="VPC Basic Use Case"
 >
-  Learn how to optimize your Scaleway VPCs, Private Networks and resource connectivity with [our new guide](/network/vpc/reference-content/getting-most-private-networks/) detailing tips and best practices.
+  Read our [Basic VPC use case](/network/vpc/reference-content/use-case-basic/) documentation for full details of how to create a simple infrastructure that leverages the advantages of Private Networks, including accompanying Terraform templates.
+</Message>
+
 </Alert>
 
 <ProductHeader 

network/vpc/reference-content/getting-most-private-networks.mdx

@@ -49,6 +49,10 @@ For example, you may use one Private Network for frontend resources and another
 
 When [creating a Private Network](/network/vpc/how-to/create-private-network/), you can let Scaleway automatically generate a CIDR block for it that is guaranteed to be unique in this VPC. All resources attached to the Private Network get a private IP address from this block. However, you also have the option to define your own CIDR block for the network. Ensure you choose a prefix and network size that is appropriate for your needs, does not overlap with that of any other Private Network in the VPC, and contains enough IP addresses for all resources that will be attached to the Private Network.
 
+<Message type="tip">
+See our [Basic VPC use case](/network/vpc/reference-content/use-case-basic/) documentation for full details of how to create a simple infrastructure that leverages the advantages of Private Networks, including accompanying Terraform templates.
+</Message>
+
 ## Attaching resources to Private Networks
 
 When you attach a resource (e.g. an Instance, an Elastic Metal server) to a Private Network, you can either:

network/vpc/reference-content/use-case-basic.mdx

@@ -33,6 +33,8 @@ This is a basic infrastructure to leverage VPC isolation:
 - Administrators can access the Instances via the [Public Gateway](/network/public-gateways/concepts/#public-gateway).
 - External services are accessed by the Instances via the Public Gateway.
 
+Full [Terraform templates](#terraform) are available for this infrastructure.
+
 ## Detail
 
 User requests go via a domain name, whose DNS record points to the public flexible IP of a Scaleway Load Balancer. This Load Balancer is attached to a **Private Network** in a **VPC**. It distributes user traffic to multiple **Instances** which are also attached to the Private Network, and do not have their own public/flexible IP addresses. These Instances are accessible only from within the VPC. The Instances can store data to and retrieve data from **Block Storage** and a **Managed Database** attached to the same Private Network and not exposed to the internet. 
@@ -89,8 +91,42 @@ Follow the steps below to create this infrastructure using the [Scaleway console
 
 ## Terraform
 
-A Terraform template for this architecture is provided in full on our [Terraform Scaleway Provider pages](TODO-LINK). Terraform allows you to create Infrastructure as Code (IaC) to build, configure and manage your infrastructure with configuration files, rather than with the Scaleway console. The following snippet shows an extract of the configuration file:
+Terraform templates for this architecture are provided in full on our [Scaleway Terraform Examples repo](https://github.com/scaleway/terraform-examples/tree/main/demo-vpc-app/). Terraform allows you to create Infrastructure as Code (IaC) to build, configure and manage your infrastructure with configuration files, rather than with the Scaleway console. 
+
+The templates include an example "Task Tracker" application to show how the infrastructure is used. The application is containerized using Docker, deployed on an Instance in the Private Network and leverages PostgreSQL for data storage. Full instructions are provided for creating the infrastructure with Terraform and deploying the test application.
+
+The following snippet shows an extract of the configuration file:
 
 ```
-SNIPPET
-```
+resource "scaleway_vpc" "vpc01" {
+  name = "vpc_${var.app_name}"
+}
+
+resource "scaleway_vpc_private_network" "pn01" {
+  name   = "pn_${var.app_name}"
+  vpc_id = scaleway_vpc.vpc01.id
+  ipv4_subnet {
+    subnet = local.subnet
+  }
+}
+
+resource "scaleway_vpc_public_gateway_ip" "gwip01" {
+}
+
+resource "scaleway_vpc_public_gateway" "pgw01" {
+  type            = "VPC-GW-S"
+  name            = "pgw_${var.app_name}"
+  ip_id           = scaleway_vpc_public_gateway_ip.gwip01.id
+  bastion_enabled = true
+  bastion_port    = 61000
+}
+
+resource "scaleway_ipam_ip" "vpcgw_ip" {
+  address = cidrhost(local.subnet, 2)
+  source {
+    private_network_id = scaleway_vpc_private_network.pn01.id
+  }
+}
+```
+
+[See the full Terraform templates](https://github.com/scaleway/terraform-examples/tree/main/demo-vpc-app/)