Skip to main content

Triage AWS NAT Gateway Usage NATGATEWAY_NOT_AVAILABLE

  1. Configure AWS NAT Gateway Usage
  2. Use Case for AWS NAT Gateway Usage
  3. Triage Guides by Violation Type
    1. Triage AWS NAT Gateway Usage NATGATEWAY_NOT_AVAILABLE
    2. Triage AWS NAT Gateway Usage NATGATEWAY_UNUSED

NAT Gateway Not Available

Understand​

This alert indicates that the NAT Gateway is not in the available state. This could be due to ongoing maintenance, errors, or it may be in a transient state.

Validate​

  1. Verify the Alert: Check the AWS console or use the AWS CLI to describe the NAT Gateway state. Confirm the state is not available. bash aws ec2 describe-nat-gateways --nat-gateway-ids YOUR_NAT_GATEWAY_ID
  2. Data Source: The data is fetched using the DescribeNatGateways API call.
  3. Evaluation: This policy runs on a scheduled basis (every 6 hours). Ensure the timing is apt for your use case.

Triage​

  • Impact: If the NAT Gateway is required for operational purposes, you might experience network issues.
  • Worsening Factors: Problems could escalate if left unaddressed, leading to persistent network failures.
  • Remediation Risks: Restarting or changing a NAT Gateway might affect network traffic momentarily.

Act​

  1. Action: Bring the NAT Gateway back to the available state if required.
  2. AWS CLI: bash aws ec2 create-nat-gateway --subnet-id YOUR_SUBNET_ID

Reflect​

  • Feedback: If this alert repeatedly causes unnecessary noise, consider revisiting the policy thresholds.
  • Disable Policy: If not required, adjust or disable the policy.