AWS local-zones documentation change
Summary
Updated MTU size documentation for AWS Direct Connect and EC2 instances in specific Local Zones
Security assessment
The changes adjust network MTU size specifications without any mention of security vulnerabilities, patches, or security-related configurations. This appears to be a routine technical specification update.
Diff
diff --git a/local-zones/latest/ug/how-local-zones-work.md b/local-zones/latest/ug/how-local-zones-work.md index fe52634cf..096cc7896 100644 --- a//local-zones/latest/ug/how-local-zones-work.md +++ b//local-zones/latest/ug/how-local-zones-work.md @@ -53 +53 @@ To understand virtual private gateway and other AWS Site-to-Site VPN concepts, s - * 1468 bytes between AWS Direct Connect and a Local Zone. + * 1500 bytes between AWS Direct Connect and all Local Zones except: @@ -55 +55,3 @@ To understand virtual private gateway and other AWS Site-to-Site VPN concepts, s - * 1300 bytes between an Amazon EC2 instance in a Local Zone and an Amazon EC2 instance in the Region for most Local Zones except: + * 8500 bytes for `us-east-1-atl-2a`, `us-east-1-chi-2a`, `us-east-1-dfw-2a`, `us-east-1-iah-2a`, `us-west-2-lax-1a`, `us-west-2-lax-1b`, `us-east-1-mia-2a`, `us-east-1-nyc-2a`, and `us-west-2-phx-2a` + + * 1300 bytes between an Amazon EC2 instance in a Local Zone and an Amazon EC2 instance in the Region for all Local Zones except: