Skip to content

Conversation

@Trish-Muyambiri
Copy link

Summary

This PR improves the documentation around NAT Gateway configurations by clearly outlining the behavior of:

  • single_nat_gateway
  • one_nat_gateway_per_az
  • Their interaction and precedence when both are enabled

What Changed

  • Updated the NAT Gateway config section in README.md to:
    • Use consistent bullet formatting
    • Include clear, labeled scenarios
    • Add a visible note explaining precedence when both flags are set
  • Removed a redundant sentence that was covered by the new warning block

Why

This helps users understand how NAT Gateway settings affect behavior in common setups, especially when optimizing for cost or availability.

Closes #1196

@Trish-Muyambiri Trish-Muyambiri force-pushed the docs/clarify-nat-gateway-behavior branch from fcbd4db to d125bb8 Compare June 28, 2025 16:06
@Trish-Muyambiri Trish-Muyambiri changed the title docs: clarify NAT gateway behavior and precedence of single_nat_gateway vs one_nat_gateway_per_az docs: Clarify NAT gateway behavior and precedence of single_nat_gateway vs one_nat_gateway_per_az Jun 28, 2025
@Trish-Muyambiri Trish-Muyambiri force-pushed the docs/clarify-nat-gateway-behavior branch from d125bb8 to 5a006fe Compare June 28, 2025 16:33
@Trish-Muyambiri Trish-Muyambiri force-pushed the docs/clarify-nat-gateway-behavior branch from 5a006fe to 2484ef3 Compare June 29, 2025 07:29
@github-actions
Copy link

This PR has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this PR will be closed in 10 days

@github-actions github-actions bot added the stale label Jul 30, 2025
@github-actions
Copy link

This PR was automatically closed because of stale in 10 days

@github-actions github-actions bot closed this Aug 10, 2025
@github-actions
Copy link

github-actions bot commented Sep 9, 2025

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 9, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

One NAT per subnet docs update or code fix ?

1 participant