Skip to content

Use StandardV2 NAT Gateways #81

Description

@doshitan

Context

See TODO:

# TODO: at the moment we create a single NAT Gateway for the Virtual Network, in
# AWS we create a different one for each availability zone. Do we want to do
# that here? We'll have to create unique subnets for each zone though, and put
# zonal resources into the right subnet.
#
# https://learn.microsoft.com/en-us/azure/nat-gateway/nat-overview#availability-zones
# https://learn.microsoft.com/en-us/azure/nat-gateway/nat-availability-zones

The StandardV2 SKU is automatically zone redundant and supports IPv6 (as well as being higher performance), for the same cost: https://learn.microsoft.com/en-us/azure/nat-gateway/nat-sku

Support added in azurerm provider v4.67.0: https://github.com/hashicorp/terraform-provider-azurerm/releases/tag/v4.67.0

Implementation

Acceptance Criteria

  • NAT Gateways use StandardV2 SKUs by default

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions