Concept and mechanism
Capacity is more than nominal connection bandwidth. It includes supported packet size, available quotas, concurrency, destination, and failure behavior. In detailed Direct Connect guidance, transit VIF supports jumbo MTU of 8500 bytes; do not generalize the private VIF’s 9001 limit. Confirm every segment before sending larger packets. For expansion, inspect quotas actually allocated to the account and Region. A public default may differ from your account’s value, and an adjustable limit does not mean an increase is already approved. Allow time to request capacity and verify availability before the implementation window.
Guided application
A failover rehearsal should measure the operation on the surviving path. If BGP converges but the batch misses its deadline because of saturation, functional resilience still has a gap. Define load, duration, stop signals, and return to initial state. For cost, add resources, transfer, observation, and operational effort across the complete design. Savings of 180 with additional costs of 230 and 40 represent a net increase of 90, using fictional values. Do not announce a reduction by counting only retired equipment. Finally, preserve tool limitations: for TCP analysis crossing a TGW route table, documentation limits analysis to the forward direction. Verify return paths and functional recovery separately.
The alternative route exists but supports only half the required load. The plan needs additional capacity or an approved degraded mode.
Common pitfalls
Adjustable quota as immediate; route as SLA; partial savings; forward analysis as proven return.
Related topics: Encryption and DNS controls · Inspection, auditing, and retirement
Measure the surviving service and present total cost with assumptions.
Reference: ANS-C01 domain 3 · ANS-C01