aws-vpc-monitoring-integration.mdx

title	tags	metaDescription	redirects	freshnessValidatedDate
Amazon VPC monitoring integration	Integrations Amazon integrations AWS integrations list	New Relic's Amazon VPC monitoring integration: how to enable it, and the data it reports.	/docs/integrations/amazon-integrations/aws-integrations-list/aws-vpc-monitoring-integration /docs/aws-vpc-integration /docs/infrastructure/infrastructure-integrations/amazon-integrations/aws-vpc-integration /docs/infrastructure/amazon-integrations/amazon-integrations/aws-vpc-monitoring-integration	never

Enable the [AWS CloudWatch Metric Streams integration](/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-metric-stream/) to monitor all CloudWatch metrics from your AWS services, including custom namespaces. Individual integrations are no longer our recommended option.

New Relic infrastructure integrations include an integration for reporting your Amazon VPC data to New Relic. This document explains how to activate the integration and describes the data reported.

Features [#features]

The Amazon Virtual Private Cloud (VPC) is a virtual network that utilizes the scalable infrastructure of Amazon Web Services (AWS). With New Relic's VPC integration, you can gain visibility into configuration event changes that are overlaid across your Amazon services.

VPC data is available in pre-built dashboards, and you can create custom queries and charts. You can also create alert conditions to notify you about changes in the VPC.

Additionally, Enhanced Amazon VPC Flow Logs enables you to capture information about IP traffic to and from network interfaces in your VPC.

Activate [#activate]

To enable this integration follow standard procedures to Connect AWS services to New Relic.

Configuration and polling [#polling]

You can change the polling frequency and filter data using configuration options.

Default polling information for the Amazon VPC integration:

• Default New Relic polling interval: 15 minutes
• Amazon CloudWatch data interval: 1 minute

Find and use data [#find-data]

To find your integration data, go to one.newrelic.com > All capabilities > Infrastructure > AWS and select one of the VPC integration links.

You can query and explore your data using the PrivateNetworkSample event type, with provider values of:

• VpcNatGateway
• VpcVpnTunnel

By default, collection of VpcNatGateway, VpcVpnTunnel, and VpcVpnConnection data is disabled.

This is because if you have many NAT gateways or many VPNs (connections and tunnels), it might lead to an increase on your CloudWatch bill. For this reason, the integration provides configuration settings to set whether you want to fetch that data.

For more on how to use your data, see Understand integration data.

Metric data [#metrics]

VPC NAT Gateway data [#vpc-nat-gateway]

This integration collects the following data from PrivateNetworkSample with a provider value of VpcNatGateway:

For full descriptions, see [Amazon VPC NAT Gateway Metrics and Dimensions](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/nat-gateway-metricscollected.html).

  <th>
    Description
  </th>
</tr>

  <td>
    The total number of concurrent active TCP connections through the NAT gateway.
  </td>
</tr>

<tr>
  <td>
    `bytesInFromDestination`
  </td>

  <td>
    The number of bytes received by the NAT gateway from the destination.
  </td>
</tr>

<tr>
  <td>
    `bytesInFromSource`
  </td>

  <td>
    The number of bytes received by the NAT gateway from clients in your VPC.
  </td>
</tr>

<tr>
  <td>
    `bytesOutToDestination`
  </td>

  <td>
    The number of bytes sent out through the NAT gateway to the destination.
  </td>
</tr>

<tr>
  <td>
    `bytesOutToSource`
  </td>

  <td>
    The number of bytes sent through the NAT gateway to the clients in your VPC.
  </td>
</tr>

<tr>
  <td>
    `connectionAttemptCount`
  </td>

  <td>
    The number of connection attempts made through the NAT gateway.
  </td>
</tr>

<tr>
  <td>
    `connectionEstablishedCount`
  </td>

  <td>
    The number of connections established through the NAT gateway.
  </td>
</tr>

<tr>
  <td>
    `errorPortAllocation`
  </td>

  <td>
    The number of times the NAT gateway could not allocate a source port.
  </td>
</tr>

<tr>
  <td>
    `idleTimeoutCount`
  </td>

  <td>
    The number of connections that transitioned from the active state to the idle state. An active connection transitions to idle if it was not closed gracefully and there was no activity for the last 350 seconds.
  </td>
</tr>

<tr>
  <td>
    `packetsDropCount`
  </td>

  <td>
    The number of packets dropped by the NAT gateway.
  </td>
</tr>

<tr>
  <td>
    `packetsInFromDestination`
  </td>

  <td>
    The number of packets received by the NAT gateway from the destination.
  </td>
</tr>

<tr>
  <td>
    `packetsInFromSource`
  </td>

  <td>
    The number of packets received by the NAT gateway from clients in your VPC.
  </td>
</tr>

<tr>
  <td>
    `packetsOutToDestination`
  </td>

  <td>
    The number of packets sent out through the NAT gateway to the destination.
  </td>
</tr>

<tr>
  <td>
    `packetsOutToSource`
  </td>

  <td>
    The number of packets sent through the NAT gateway to the clients in your VPC.
  </td>
</tr>

Name
`activeConnectionCount`

VPC VPN Tunnel

This integration collects the following data from PrivateNetworkSample with a provider value of VpcVpnTunnel:

For full descriptions, see [Amazon VPC VPN Metrics and Dimensions](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/vpn-metricscollected.html).

  <th>
    Description
  </th>
</tr>

  <td>
    The state of the tunnel. 0 indicates DOWN and 1 indicates UP.
  </td>
</tr>

<tr>
  <td>
    `tunnelDataIn`
  </td>

  <td>
    The bytes received through the VPN tunnel. Each metric data point represents the number of bytes received after the previous data point. Use the Sum statistic to show the total number of bytes received during the period.
  </td>
</tr>

<tr>
  <td>
    `tunnelDataOut`
  </td>

  <td>
    The bytes sent through the VPN tunnel. Each metric data point represents the number of bytes sent after the previous data point. Use the Sum statistic to show the total number of bytes sent during the period.
  </td>
</tr>

Name
`tunnelState`