Loading

AWS NAT gateway

<div class="condensed-table">
| | |
| --- | --- |
| Version | 2.38.2 (View all) |
| Compatible Kibana version(s) | 8.16.2 or higher |
| Supported Serverless project types
What’s this? | Security
Observability |
| Subscription level
What’s this? | Basic |

</div>
The AWS NAT gateway integration allows you to monitor NAT gateways on Amazon Virtual Private Cloud.

Use the AWS NAT gateway integration to collect metrics related to your NAT gateways. Then visualize that data in Kibana, create alerts to notify you if something goes wrong, and reference metrics when troubleshooting an issue.

For example, you could use this integration to view the total number of concurrent, active TCP connections through the NAT gateway.

Important

Extra AWS charges on API requests will be generated by this integration. Check API Requests for more details.

The AWS NAT gateway integration collects one type of data: metrics.

Metrics give you insight into the state of your NAT gateways. Metrics collected by this integration include the number of connection attempts made through the NAT gateway, the total number of concurrent, active TCP connections through the NAT gateway, the number of times the NAT gateway could not allocate a source port, and more. See more details in the Metrics reference.

You need Elasticsearch for storing and searching your data and Kibana for visualizing and managing it. You can use our hosted Elasticsearch Service on Elastic Cloud, which is recommended, or self-manage the Elastic Stack on your own hardware.

Before using any AWS integration you will need:

  • AWS Credentials to connect with your AWS account.
  • AWS Permissions to make sure the user you’re using to connect has permission to share the relevant data.

For more details about these requirements, please take a look at the AWS integration documentation.

Use this integration if you only need to collect AWS NAT gateway metrics.

If you want to collect data from two or more AWS services, consider using the AWS integration. When you configure the AWS integration, you can collect data from as many AWS services as you’d like.

For step-by-step instructions on how to set up an integration, see the Getting started guide.

ECS Field Reference

Please refer to the following document for detailed information on ECS fields.