Monitoring AWS Interconnect API calls using AWS CloudWatch

You can monitor AWS Interconnect using CloudWatch, which collects raw data and processes it into readable, near real-time metrics. These statistics are kept for 15 months, so that you can access historical information and gain a better perspective on how your web application or service is performing. You can also set alarms that watch for certain thresholds, and send notifications or take actions when those thresholds are met. For more information, see the Amazon CloudWatch User Guide.

Once your workloads start generating traffic, use the ConnectionUtilizationIngress, ConnectionUtilizationEgress, ConnectionBpsEgress, and ConnectionBpsIngress metrics to confirm expected levels of utilization and adjust your Interconnect’s bandwidth as needed to prevent congestion. Consider setting CloudWatch alarms at your preferred utilization thresholds to allow changing an Interconnect’s bandwidth setting before a congestion event occurs.

The following tables list the metrics and dimensions for AWS Interconnect.

Metric	Description
ConnectionUtilizationEgress	The percentage utilization of your Interconnect for outbound data from the AWS side of the connection. The metric is calculated as a percentage of your Interconnect’s configured bandwidth. The number reported is the aggregate (average) over the specified time period (5 minutes by default, 1 minute minimum). You can change the default aggregate. This metric might be unavailable for a new connection, or when a device reboots. The metric starts when the connection is used to send or receive traffic. Units: Percentage
ConnectionUtilizationIngress	The percentage utilization of your Interconnect for inbound data to the AWS side of the connection. The metric is calculated as a percentage of your Interconnect’s configured bandwidth. The number reported is the aggregate (average) over the specified time period (5 minutes by default, 1 minute minimum). You can change the default aggregate. This metric might be unavailable for a new connection, or when a device reboots. The metric starts when the connection is used to send or receive traffic. Units: Percentage
ConnectionBpsEgress	The bitrate for outbound data from the AWS side of the connection. The number reported is the aggregate (average) over the specified time period (5 minutes by default, 1 minute minimum). You can change the default aggregate. This metric might be unavailable for a new connection, or when a device reboots. The metric starts when the connection is used to send or receive traffic. Units: Bits per second
ConnectionBpsIngress	The bitrate for inbound data to the AWS side of the connection. This metric might be unavailable for a new connection, or when a device reboots. The metric starts when the connection is used to send or receive traffic. Units: Bits per second
ConnectionPpsEgress	The packet rate for outbound data from the AWS side of the connection. The number reported is the aggregate (average) over the specified time period (5 minutes by default, 1 minute minimum). You can change the default aggregate. This metric might be unavailable for a new connection, or when a device reboots. The metric starts when the connection is used to send or receive traffic. Units: Packets per second
ConnectionPpsIngress	The packet rate for inbound data to the AWS side of the connection. The number reported is the aggregate (average) over the specified time period (5 minutes by default, 1 minute minimum). You can change the default aggregate. This metric might be unavailable for a new connection, or when a device reboots. The metric starts when the connection is used to send or receive traffic. Units: Packets per second

The ConnectionUtilizationEgress and ConnectionUtilizationIngress metrics report the percentage utilization of an Interconnect relative to its configured bandwidth. This metric is derived automatically, and does not require you to apply CloudWatch Math.

When you change an Interconnect’s allocated bandwidth, you might see a step change in the percentage utilization shown by the metrics ConnectionUtilizationIngress and ConnectionUtilizationEgress, depending on the traffic going through the connection when you make the change. For example, if your Interconnect is configured to 1 Gbps and it has a constant 500 Mbps of egress traffic, you will see ConnectionUtilizationEgress at 50% utilization. If you increase that Interconnect’s bandwidth to 2 Gbps, that utilization will drop to 25% as soon as the change is provisioned and the utilization metric is recalculated using the new configured capacity for that Interconnect.