You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
✨ edge subnets/gateway: add gateway routing for Local Zones
✨ edge subnets/routes: supporting custom routes for Local Zones
Isolate the route table lookup into dedicated methods for private and
public subnets to allow more complex requirements for edge zones, as
well introduce unit tests for each scenario to cover edge cases.
There is no change for private and public subnets for regular
zones (standard flow), and the routes will be assigned accordainly
the existing flow: private subnets uses nat gateways per public zone,
and internet gateway for public zones's tables.
For private and public subnets in edge zones, the following changes is
introduced according to each rule:
General:
- IPv6 subnets is not be supported in AWS Local Zones,
zone, consequently no ip6 routes will be created
- nat gateways is not supported, default gateway's route for private
subnets will use nat gateways from the zones in the Region
(availability-zone's zone type)
- one route table by zone's role by zone (standard flow)
Private tables for Local Zones:
- default route's gateways is assigned using nat gateway created in
the region (availability-zones).
Public tables for Local Zones:
- default route's gateway is assigned using internet gateway
The changes in the standard flow (without edge subnets' support) was
isolated in the PR #4900
✨ edge subnets/nat-gw: support private routing in Local Zones
Introduce the support to lookup a nat gateway for edge zones when
creating private subnets.
Currently CAPA requires a NAT Gateway in the public subnet for each zone
which requires private subnets to define default nat gateway in the
private route table for each zone.
NAT Gateway resource isn't globally supported by Local Zones, thus
private subnets in Local Zones are created with default route gateway
using a nat gateway selected in the Region (regular availability zones)
based in the Parent Zone* for the edge subnet.
*each edge zone is "tied" to a zone named "Parent Zone", a zone type
availability-zone (regular zones) in the region.
return"", errors.Errorf("no nat gateways available in %q for private subnet %q, current state: %+v", sn.AvailabilityZone, sn.GetResourceID(), azGateways)
375
+
return"", errors.Errorf("no nat gateways available in %q for private edge subnet %q, current state: %+v", sn.AvailabilityZone, sn.GetResourceID(), azGateways)
0 commit comments