diff --git a/pages/public-gateways/concepts.mdx b/pages/public-gateways/concepts.mdx index 26b3839dbd..cb7b669802 100644 --- a/pages/public-gateways/concepts.mdx +++ b/pages/public-gateways/concepts.mdx @@ -73,14 +73,15 @@ Private Networks attached to legacy Public Gateways must stay in the gateway's a **IPAM** Public Gateways are fully and natively integrated with the Scaleway IPAM without any workaround. Your gateway is in IPAM mode if: - You created it via the Scaleway console on or after 17 October 2023 -- You created it via the Scaleway API or developer tools using the `ipam_config` object, and the auto-calculated `is_legacy` [Gateway parameter](https://www.scaleway.com/en/developers/api/public-gateway/#path-gateways-create-a-public-gateway) has a value of `false`. - -You cannot "migrate" a legacy Public Gateway to become an IPAM-mode gateway. While legacy Public Gateways continue to function thanks to our [workaround](/vpc/reference-content/vpc-migration/#public-gateways-and-vpc), you cannot modify them to become natively integrated IPAM networks. If you wish to have an IPAM-mode Public Gateway, for example to benefit from IP management via Scaleway's [IPAM](https://www.scaleway.com/en/developers/api/vpc/) API as more features become available, or to use Kapsule with full isolation, you must create a new gateway. +- You created it via the Scaleway API or devtools using the `ipam_config` object, and the auto-calculated `is_legacy` [Gateway parameter](https://www.scaleway.com/en/developers/api/public-gateway/#path-gateways-create-a-public-gateway) has a value of `false`. +- You moved it from legacy mode to IPAM mode using the dedicated button in the console, or the dedicated API call. When creating a Kubernetes Kapsule cluster with [full isolation](/kubernetes/reference-content/secure-cluster-with-private-network/#can-i-use-a-public-gateway-with-my-private-network-to-exit-all-outgoing-traffic-from-the-nodes) you are required to attach a Public Gateway to the cluster's Private Network, and this **cannot** be a legacy Public Gateway - it must be an IPAM-mode gateway. +See also our dedicated documentation on [moving Public Gateways to IPAM-mode](/public-gateways/reference-content/understanding-v2/) to ensure compatibility with our new API v2. + ## Legacy gateway See [IPAM](#ipam). diff --git a/pages/public-gateways/faq.mdx b/pages/public-gateways/faq.mdx index abeea7d42d..e24cbf30e9 100644 --- a/pages/public-gateways/faq.mdx +++ b/pages/public-gateways/faq.mdx @@ -29,13 +29,33 @@ Moreover, the Public Gateway supports [static NAT](/public-gateways/how-to/confi On 12 July 2023, DHCP functionality moved from Public Gateways to Private Networks. See our [dedicated migration documentation](/vpc/reference-content/vpc-migration/) for full details. -Pre-existing static leases created via the Public Gateway were fully migrated and still work for your attached resources on a Private Network. Manual static lease configuration is still available via the API and other developer tools, but is no longer available via the Scaleway console. We recommend that you use [Scaleway IPAM](/ipam/) to reserve private IP addresses on specific Private Networks, which you can then use when attaching resources. +Pre-existing static leases created via the Public Gateway were fully migrated and still work for your attached resources on a Private Network. Manual static lease configuration is still available via the API v1 and other developer tools, but this functionality is now deprecated, and does not exist in v2 of the API. -## Why is my Public Gateway labelled as Legacy? +Read our [dedicated documentation](/public-gateways/reference-content/understanding-v2/) to learn how to put your gateway into IPAM-mode and replicate static DHCP reservation functionality with Scaleway IPAM. -**Legacy** Public Gateways use a [workaround](/vpc/reference-content/vpc-migration/#public-gateways-and-vpc) to ensure compatiblity with Scaleway's IPAM (**I** **P** **A**ddress **M**anagement) tool. IPAM acts as a single source of truth for the IP addresses of Scaleway resources +## Why is my Public Gateway labeled as Legacy? -Your gateway is probably a legacy gateway if you created it prior to 17 October 2023. These gateways will continue to function, but are not natively integrated with IPAM, and you cannot take advantage of features such as IP management via Scaleway [IPAM](/ipam/), or fully-isolated Kubernetes Kapsules. You should create a new gateway if you want to benefit from such features. +**Legacy** Public Gateways use a [workaround](/vpc/reference-content/vpc-migration/#public-gateways-and-vpc) to ensure compatibility with Scaleway's IPAM (**I** **P** **A**ddress **M**anagement) tool. IPAM acts as a single source of truth for the IP addresses of Scaleway resources + +Your gateway is a legacy gateway if you created it prior to 17 October 2023 and you never recreated it in IPAM mode. Legacy gateways are now deprecated, as they are incompatible with v2 of the Public Gateways API. Such gateways must be [moved to IPAM mode](/public-gateways/reference-content/understanding-v2/) before October 2025 to ensure ongoing functionality. + +## I received a message about v1 of the Public Gateways API being deprecated, do I need to take action? + +The Public Gateways API v1 is now deprecated, and will be removed on 1 October 2025. Only IPAM-mode gateways will be compatible with the new version of the API (v2). Whether or not you need to take action depends on the following two points: + +- Consider whether you manage your Public Gateway uniquely via the Scaleway console, or via calls to the API/devtools in code and scripts: + + - **Code and scripts**: If you have any code or scripts that call v1 of the API, or use devtool functionality that is [removed from v2](/public-gateways/reference-content/understanding-v2/) such as DHCP object or entries, **you must take action before 1 Oct 2025**. Update your code and scripts so they point to v2 of the API. [Follow the examples provided for tools such as Terraform](https://github.com/scaleway/terraform-provider-scaleway/blob/master/docs/guides/migration_guide_vpcgw_v2.md) to rewrite your devtool templates so they do not refer to removed functionalities. Do this in synchronization with moving your gateway to IPAM mode (if necessary). + + - **Console-only**: You do not need to take any action, except ensuring that your gateway is in IPAM mode. + +- Check in the [Scaleway console](https://console.scaleway.com/public-gateway/public-gateways) whether your Public Gateway is in IPAM mode or legacy mode: + + - **Legacy mode**: You must move the gateway to IPAM mode. Only IPAM mode gateways are compatible with v2. Use the **Move to IPAM mode** button in the console, the [dedicated API call](https://www.scaleway.com/en/developers/api/public-gateway/v1/#path-gateways-put-a-public-gateway-in-ipam-mode), or the `move_to_ipam` flag in [Terraform](https://github.com/scaleway/terraform-provider-scaleway/blob/master/docs/guides/migration_guide_vpcgw_v2.md). + + - **IPAM mode**: You do not have any action to take, except updating any code and scripts that you have (see above). + +See our [dedicated documentation](/public-gateways/reference-content/understanding-v2/) for full details. ## Do I need a Public Gateway for each Availability Zone (AZ)? diff --git a/pages/public-gateways/reference-content/assets/scaleway-pgw-listing.webp b/pages/public-gateways/reference-content/assets/scaleway-pgw-listing.webp new file mode 100644 index 0000000000..2f8cb3962d Binary files /dev/null and b/pages/public-gateways/reference-content/assets/scaleway-pgw-listing.webp differ diff --git a/pages/public-gateways/reference-content/index.mdx b/pages/public-gateways/reference-content/index.mdx new file mode 100644 index 0000000000..fc10d136e3 --- /dev/null +++ b/pages/public-gateways/reference-content/index.mdx @@ -0,0 +1,8 @@ +--- +meta: + title: Public Gateways - Additional Content + description: Explore detailed Scaleway configurations, best practices and troubleshooting for Scaleway Public Gateways. Optimize the configuration of your gateway with our comprehensive reference guides. +content: + h1: Public Gateways - Additional Content + paragraph: Explore detailed Scaleway configurations, best practices and troubleshooting for Scaleway Public Gateways. Optimize the configuration of your gateway with our comprehensive reference guides. +--- diff --git a/pages/public-gateways/reference-content/understanding-v2.mdx b/pages/public-gateways/reference-content/understanding-v2.mdx new file mode 100644 index 0000000000..4824106bab --- /dev/null +++ b/pages/public-gateways/reference-content/understanding-v2.mdx @@ -0,0 +1,222 @@ +--- +meta: + title: Understanding and preparing for Public Gateways v2 + description: Find out what to expect from Public Gateways v2, and get ready for deprecation of DHCP entries and the DHCP object, as well as new default behavior for IPAM mode. +content: + h1: Understanding and preparing for Public Gateways v2 + paragraph: Find out what to expect from Public Gateways v2, and get ready for deprecation of DHCP entries and the DHCP object, as well as new default behavior for IPAM mode. +tags: public-gateways dhcp dhcp-entries api v2 ipam-mode legacy +dates: + creation: 2025-01-23 + validation: 2025-01-23 +categories: + - network +--- + +Scaleway's VPC offering is evolving, and with this comes changes for the Public Gateway product. + +This document explains what to expect and how to prepare for the upcoming changes. + +## Summary (TL;DR) + +All Scaleway Public Gateways until now have been created and managed with the version 1 of the [Public Gateways API](https://www.scaleway.com/en/developers/api/public-gateway/v1/), either explicitly via the API itself, or implicitly behind the scenes of the Scaleway console or other developer tools. + +**We are now deprecating v1 of the API and transitioning to v2.** + +| | **PGW API v1** | **PGW API v2** | +|---|---|---| +| Supports [legacy-mode PGWs](/public-gateways/concepts/#ipam) | Yes ✅ | No ❌| +| Supports [IPAM-mode PGWs](/public-gateways/concepts/#ipam) | Yes ✅ | Yes ✅| +| Supports SSH bastion allowed IPs, and future new features | No ❌| Yes ✅ | +| Deprecated? | Yes ✅ | No ❌| +| Removal date | 1 Oct 2025 | --- | +| Compatible with PGW management via Scaleway console? | Only until 1 Oct 2025 | Yes ✅ | + +After a deprecation period ending on 1 Oct 2025, the Public Gateways API v1 and associated developer tools will be removed. + +**What you need to do before 1 Oct 2025:** + +- Ensure that your Public Gateway is in [IPAM mode](#ipam-mode-becomes-default). Only IPAM-mode gateways are compatible with v2. + +- Put any non-IPAM mode ([legacy](/network/public-gateways/concepts/#ipam)) Public Gateways in IPAM mode. You can do this in several ways: + - Use the **Move to IPAM mode** button in the console + - Use the [dedicated API call](https://www.scaleway.com/en/developers/api/public-gateway/v1/#path-gateways-put-a-public-gateway-in-ipam-mode). + - Use the `move_to_ipam` flag in [Terraform](https://github.com/scaleway/terraform-provider-scaleway/blob/master/docs/guides/migration_guide_vpcgw_v2.md) + +- Update any code or scripts you have that call version 1 of the Public Gateways API, so that they call version 2 instead, and do not refer to [removed functionalities](#introducing-public-gateways-api-v2). + + +If you manage your Public Gateway via Terraform, see our [dedicated guide](https://github.com/scaleway/terraform-provider-scaleway/blob/master/docs/guides/migration_guide_vpcgw_v2.md) + + +If your Public Gateway is already in IPAM mode, and you only manage it via the console, you will not be affected by these changes and you do not need to take any action. + +## Background: DHCP and IPAM + +When Scaleway originally introduced Public Gateways, they provided DHCP functionality for resources on attached Private Networks. With the [arrival of Scaleway VPC](/network/vpc/reference-content/vpc-migration/) in 2023, DHCP was moved from Public Gateways to Private Networks themselves. + +Scaleway also introduced [IPAM](/network/ipam/concepts/#ipam) to act as a single source of truth for the IP addressing of all Scaleway resources. DHCP uses IPAM to ensure consistent and reliable addressing across all Private Networks. + +When you [create a Private Network](/network/vpc/how-to/create-private-network/), you can either automatically generate a default IPv4 CIDR block, or define a custom block. A default IPv6 block is automatically created. When you attach resources to the Private Network, they automatically receive an IPv4 address (and, if compatible, an IPv6 address) from this block. Alternatively, you can [reserve a specific IP address](/network/ipam/how-to/reserve-ip/) from the block, and [specify this address](/network/ipam/how-to/reserve-ip/#how-to-attach-a-resource-to-a-private-network-using-a-reserved-ip-address) when attaching the resource. + +Whether you choose a custom or default CIDR block, automatic address assignment or use a reserved address, **the resource's private IP address does not risk changing** unless you detach the resource from the Private Network. To ensure that you can keep the same address for a resource even after detaching it, use the [reserve IP](/network/ipam/how-to/reserve-ip/) functionality. + +## Introducing Public Gateways API v2 + +Since the assignment and management of IP addresses on Private Networks is now managed by IPAM and the Private Networks themselves, we must complete the removal of the DHCP functionality from Public Gateways. This means releasing a new version (v2) of the [Public Gateways API](https://www.scaleway.com/en/developers/api/public-gateway/), which has until now retained a number of legacy DHCP functions. From this new version, you can observe: + +- IPAM mode becomes default +- Removal of the DHCP object +- Removal of the `address` field +- Removal of DHCP entries +- New SSH bastion feature: Allowed IPs + +Full details of each change are explained below. + +### IPAM mode becomes default + +Scaleway Public Gateways are either in **Legacy mode** or **IPAM mode**. You can see the mode of a given gateway by: + +- Checking its badge in the gateway listing page of the [Scaleway console](https://console.scaleway.com/public-gateway/public-gateways) (see screenshot below). +- Checking the value of the `is_legacy` field via the [Public Gateways API](https://www.scaleway.com/en/developers/api/public-gateway/#path-gateways-get-a-public-gateway). + + + + +All Public Gateways created via the Scaleway console since 17 October 2023 are necessarily in IPAM mode. + + +Legacy Public Gateways use a [workaround](/network/vpc/reference-content/vpc-migration/#public-gateways-and-vpc) to ensure IPAM compatibility. IPAM-mode Public Gateways are fully integrated with Scaleway's [IPAM](/network/ipam/concepts/#ipam), which manages the coherent assignment of IP addresses to the gateway itself, and resources on attached Private Networks. + +Legacy mode will be deprecated going forward, and will not be compatible with v2 of the Public Gateway API. It will no longer be possible to create legacy-mode Public Gateways, all new gateways will necessarily be in IPAM mode. + +If you still have a legacy gateway, you must [transition it to IPAM mode](#how-do-i-move-my-legacy-public-gateway-to-ipam-mode) so that it is compatible with v2 of the API. This will update the auto-calculated `is_legacy` field and put your gateway in IPAM mode. + +### Removal of the DHCP object + +The DHCP object has remained present in v1 of the API, despite the [migration of DHCP to Private Networks](/vpc/reference-content/vpc-migration/), which replaced DHCP on Public Gateways. + +**The DHCP object does not exist in v2 of the API**. Instead, IPAM configuration, where auto-configuration of `GatewayNetwork` is managed by IPAM and DHCP is managed by Private Networks, replaces any need for DHCP configuration via the Public Gateway. + +Remember that you can define a [custom CIDR block](/vpc/how-to/create-private-network/#how-to-configure-cidr) for a Private Network at the time of creation, and use [reserved IP addresses](/ipam/how-to/reserve-ip/#how-to-reserve-a-private-ip-address) with IPAM when attaching both standard and custom resources. + +### Removal of the address field + +For some time now, this functionality has been available via the API and developer tools only (not the Scaleway console). + +When attaching a Public Gateway to a Private Network (creating a [Gateway Network](https://www.scaleway.com/en/developers/api/public-gateway/v1/#path-gateway-networks-attach-a-public-gateway-to-a-private-network)) via the API, you could use the `address` field to define a single static IP address to assign to the Public Gateway on that Private Network. + +**The `address` field does not exist in v2 of the API**. Instead, you can pass an `ipam_ip_id` to specify a reserved IP address to use for a Public Gateway on a Private Network, if you wish. On the Scaleway console, you can select a [reserved IP](/ipam/how-to/reserve-ip/) to use when attaching a Public Gateway to a Private Network. Otherwise, use the default behaviour where IPAM auto-assigns an IP address from the Private Network's CIDR block to the Public Gateway at the moment of attachment. + +When you [use a dedicated method](#how-do-i-move-my-legacy-public-gateway-to-ipam-mode) to move a legacy Public Gateway to IPAM mode, it will keep its current IP address on all attached Private Networks. + +### Removal of DHCP entries + +For some time now, this functionality has been available via the API and developer tools only (not the Scaleway console). + +[DHCP entries](https://www.scaleway.com/en/developers/api/public-gateway/v1/#path-dhcp-entries-list-dhcp-entries) could be created, belonging to a specified `GatewayNetwork` (Public Gateway / Private Network attachment), holding dynamic DHCP leases or static, user-created DHCP reservations. They have effectively allowed the Public Gateway to assign certain IP addresses to certain resources on the Private Network. + +**DHCP entries do not exist in v2 of the API**. Instead, you can rely on the default IPAM/DHCP functionality as described [above](#background-dhcp-and-ipam). The default behavior will auto-assign IP addresses to resources on the Private Network from the network's CIDR block, or you can use the IP reservation functionality to specify the IP address(es) to assign to each resource. + +For custom resources, such as VMs hosted on Elastic Metal servers, we now provide [dedicated functionality](https://www.scaleway.com/en/docs/vpc/how-to/attach-resources-to-pn/) for attaching these to Private Networks. When choosing the **Custom Resource** type, you can specify a MAC address and hostname at the moment of attachment. + +We will automatically migrate any existing DHCP entries to IPAM for you, at the moment you put a legacy Public Gateway into IPAM mode. + +### SSH bastion allowed IPs + +Allowed IPs is a new functionality of the Public Gateways API v2, that will also be available to all IPAM-mode Public Gateways via the Scaleway console. This feature allows you to specify a list of IP address ranges which should be allowed to connect to the gateway's SSH bastion and the resources behind it. All other IP addresses will be blocked from connecting. Find out more in the [SSH bastion](/network/public-gateways/how-to/use-ssh-bastion/) documentation. + +## Timeline and action to take + +- **March 2025 - V2 release**: The Public Gateway v2 API is released, co-existing with v1. +- **8 April 2025 - V1 deprecation**: The Public Gateway v1 API is deprecated. Deprecation means that the API will still function, but it is slated for removal and we do not recommended that you keep using it. + + + You will be able to list and manage all gateways with the **Scaleway console**, which will adapt to use v1 or v2 of the API as necessary depending on whether or not the gateway is in IPAM mode. + + +- **8 April 2025 - 1 Oct 2025: Migration period**: You have a six month migration period to complete the following actions + + - Ensure that your Public Gateway is in [IPAM mode](/network/public-gateways/concepts/#ipam). Only IPAM mode gateways are compatible with v2. + - Put any non-IPAM mode ([legacy](/network/public-gateways/concepts/#ipam)) Public Gateways in IPAM-mode, by using the **Move to IPAM mode** button in the console, the [dedicated API call](https://www.scaleway.com/en/developers/api/public-gateway/v1/#path-gateways-put-a-public-gateway-in-ipam-mode), or the `move_to_ipam` flag in [Terraform](https://github.com/scaleway/terraform-provider-scaleway/blob/master/docs/guides/migration_guide_vpcgw_v2.md). + - Ensure that [DHCP is activated](/vpc/how-to/activate-dhcp/) on all Private Networks attached to your IPAM-mode Public Gateways. + - Update any code or scripts you have that call version 1 of the Public Gateways API, so that they call version 2 instead. This includes removing any use of the DHCP entries, DHCP objects or address fields as mentioned above. + + If your Public Gateway is already in IPAM mode, and you only manage it via the console, you will not be affected by these changes and you do not need to take any action. + +- **1 Oct 2025 - V1 removal**: The Public Gateway v1 API will be removed. Any code or scripts still pointing to v1 will cease to function. We will automatically put any existing legacy Public Gateways into IPAM mode. + +## FAQ + +### How do I know if I have to take action? + +- Consider whether you manage your Public Gateway uniquely via the Scaleway console, or via calls to the API/devtools in code and scripts: + + - **Code and scripts**: If you have any code or scripts that call v1 of the API, or use devtool functionality that is removed from v2 such as DHCP object or entries, **you must take action before 1 Oct 2025**. Update your code and scripts so they point to v2 of the API. [Follow the examples provided for tools such as Terraform](https://github.com/scaleway/terraform-provider-scaleway/blob/master/docs/guides/migration_guide_vpcgw_v2.md) to rewrite your devtool templates so they do not refer to removed functionalities. Do this in synchronization with moving your gateway to IPAM mode (if necessary). + + - **Console-only**: You do not need to take any action, except ensuring that your gateway is in IPAM mode. + +- Check in the [Scaleway console](https://console.scaleway.com/public-gateway/public-gateways) whether your Public Gateway is in IPAM mode or legacy mode: + + - **Legacy mode**: You must move the gateway to IPAM mode. Only IPAM mode gateways are compatible with v2. Use the **Move to IPAM mode** button in the console, the [dedicated API call](https://www.scaleway.com/en/developers/api/public-gateway/v1/#path-gateways-put-a-public-gateway-in-ipam-mode), or the `move_to_ipam` flag in [Terraform](https://github.com/scaleway/terraform-provider-scaleway/blob/master/docs/guides/migration_guide_vpcgw_v2.md). + + - **IPAM mode**: You do not have any action to take, except updating any code and scripts that you have (see above). + +### How do I move my legacy Public Gateway to IPAM mode? + +You can do this in several ways: + + - Use the **Move to IPAM mode** button in the console + - Use the [dedicated API call](https://www.scaleway.com/en/developers/api/public-gateway/v1/#path-gateways-put-a-public-gateway-in-ipam-mode). + - Use the `move_to_ipam` flag in [Terraform](https://github.com/scaleway/terraform-provider-scaleway/blob/master/docs/guides/migration_guide_vpcgw_v2.md) + +### What happens when I move my legacy Public Gateway to IPAM mode? + +We will detach your Public Gateway from all attached Private Networks, and reattach it in IPAM mode. You can expect downtime of about 10-20 seconds. We will ensure that the IP address used for the new attachment is the same as the old one. + +### My Public Gateway is already in IPAM mode, do I need to take any action? + +If you only manage your gateway via the Scaleway console, you do not need to take any action once your gateway is in IPAM mode. + +If you have any code or scripts that call v1 of the Scaleway Public Gateways API, you must update these to point towards [v2](https://www.scaleway.com/en/developers/api/public-gateway/) before 1 Oct 2025. + +### What if I want to keep using my custom gateway DHCP configuration from v1 of the API? + +After version 1 of the Public Gateways API is removed on 1 Oct 2025, these functionalities will no longer be available. + +Going forward, we expect users who were previously using custom DHCP with a Public Gateway to move to the standard set-up of IPAM and Private Networks' inbuilt DHCP for private IP assignment. Remember that you can define a [custom CIDR block](/vpc/how-to/create-private-network/#how-to-configure-cidr) for a Private Network at the time of creation, and use [reserved IP addresses](/ipam/how-to/reserve-ip/#how-to-reserve-a-private-ip-address) with IPAM when attaching both standard and custom resources. + +### I use Terraform to manage my Public Gateway, what should I do? + +If you use Terraform to manage your infrastructure as code, ensure that you are not using any functionality associated with v1 of the API (DHCP objects, DHCP entries or the `address` field). If necessary, modify your templates to reattach your Public Gateways in IPAM mode with the `move_to_ipam` flag, and use IPAM functionality to replace any DHCP configurations. + +``` +resource "scaleway_vpc_public_gateway" "main" { + name = "foobar" + type = "VPC-GW-S" + ip_id = scaleway_vpc_public_gateway_ip.main.id + move_to_ipam = true +} +``` + +Refer to our [Terraform migration guide](https://github.com/scaleway/terraform-provider-scaleway/blob/master/docs/guides/migration_guide_vpcgw_v2.md) for full details and help moving legacy gateways to IPAM mode. + +### Can't I just wait for Scaleway to force the move to IPAM mode? + +After 1 Oct 2025 we will carry out a forced action which will move all existing legacy Public Gateways to IPAM mode, and we will remove v1 of the Public Gateways API. + +We highly recommend that you move to IPAM mode **before** this date, so that you can plan a smooth and synchronized transition at a time that suits you. + +If you still have code or scripts pointing to v1 of the API after the 1 Oct 2025, these will cease to function. + +## Further help and support + +If you have any questions, get in touch with us on the `#public-gateway` channel on the [Scaleway Slack Community](https://www.scaleway.com/en/docs/tutorials/scaleway-slack-community/), or [open a support ticket](https://console.scaleway.com/support/tickets/create). + +The following documentation resources may be useful to you: + +- [Public Gateway API Documentation](https://www.scaleway.com/en/developers/api/public-gateway/) +- [Public Gateway Main Documentation](https://www.scaleway.com/en/docs/network/public-gateways/) +- [IPAM API Documentation](https://www.scaleway.com/en/developers/api/ipam/) +- [IPAM Main Documentation](https://www.scaleway.com/en/docs/network/ipam/) +- [Moving a Public Gateway from Legacy mode to IPAM mode with Terraform](https://github.com/scaleway/terraform-provider-scaleway/blob/master/docs/guides/migration_guide_vpcgw_v2.md)