A low-traffic test environment needs outbound access from private subnets for a short period.
Prioritize low cost and accept lower availability and more operational responsibility.
Choose TWO appropriate design elements.
A small EC2 NAT instance can be cheaper than a NAT Gateway when the team accepts patching and availability trade-offs; compare those trade-offs explicitly.
Detailed explanation
A NAT instance transfers scaling, patching, and failure handling to the customer, so the trade-off must be accepted.
A NAT instance transfers scaling, patching, and failure handling to the customer, so the trade-off must be accepted.
A single instance creates a failure point and can add cross-AZ dependency in production.
A single instance creates a failure point and can add cross-AZ dependency in production.
Exposing credentials is unsafe and does not reduce network cost.
Exposing credentials is unsafe and does not reduce network cost.
For low traffic and short-lived environments, an EC2 NAT instance can reduce fixed managed-gateway cost.
For low traffic and short-lived environments, an EC2 NAT instance can reduce fixed managed-gateway cost.
Check official documentation
Compare the following points with the official documentation.
AWS VPC NAT GatewayとNAT instanceの公式説明を確認する。
What to confirm
NAT GatewayとNATインスタンスの料金・運用・可用性を比較できる。
Key points
- NAT instance
- NAT Gateway
- Operational responsibility
Notes
- Environment: AWS公式VPCドキュメントの確認
- Confirm current AWS pricing and service behavior in the official documentation.
Foundation review
Environment fit
A low-traffic, disposable test environment may accept a NAT instance's operational burden.
Availability trade-off
A single self-managed instance can become a failure point and may require multi-AZ design in production.