Contents

AWSELB

Each grouping represents a specific way AWS Elastic Load Balancing (AWS ELB) measures and bills for resource consumption. Click into a code for additional specifications.

AWS Elastic Load Balancing (AWS ELB)

Data Transfer

AWS-In-Bytes

The amount of data (per GB) transferred into AWS. Data transferred into AWS does not incur a fee. If there are two regions in the prefix, the first represents the source region, and the second represents the destination region. If there is only one region in the prefix, the prefix represents the AWS source region.

Billing Codes

AWS-Out-Bytes

The amount of data (per GB) transferred out of AWS. If there are two regions in the prefix, the first represents the source region, and the second represents the destination region. If there is only one region in the prefix, the prefix represents the AWS source region.

Billing Codes

DataTransfer-Out-Bytes

The amount of data (per GB) transferred out of AWS to the internet.

Billing Codes

DataTransfer-Regional-Bytes

The amount of data (per GB) transferred within the same Availability Zone.

Billing Codes

DataTransfer-In-Bytes

The amount of data (per GB) transferred into AWS from the internet. Data transferred into AWS does not incur a fee.

Billing Codes

CloudFront-Out-Bytes

The amount of data (per GB) transferred out of an AWS region to CloudFront.

Billing Codes

CloudFront-In-Bytes

The amount of data (per GB) transferred into an AWS region from CloudFront. Each CloudFront data transfer also has a line item for CloudFront-Out-Bytes in which the cost is applied.

Billing Codes

DataXfer-In

The amount of AWS Direct Connect data (per GB) transferred in over a virtual interface. Each AWS Direct Connect data transfer also has a line item for DataXfer-Out in which the cost is applied. If there is a postfix of `dc.3` that indicates the data was transferred over a private virtual interface. Otherwise, the data was transferred over a public virtual interface. The first region in the prefix represents the source region, and the second represents the destination region.

Billing Codes

DataXfer-Out

The amount of AWS Direct Connect data (per GB) transferred out over a virtual interface. If there is a postfix of `dc.3` that indicates the data was transferred over a private virtual interface. Otherwise, the data was transferred over a public virtual interface. The first region in the prefix represents the source region, and the second represents the destination region.

Billing Codes

CloudFrontChina-In-Bytes

The amount of data (per GB) transferred into an AWS region from CloudFront China. Each CloudFront China data transfer also has a line item for CloudFrontChina-Out-Bytes in which the cost is applied.

Billing Codes

CloudFrontChina-Out-Bytes

The amount of data (per GB) transferred out of an AWS region to CloudFront China.

Billing Codes

DataTransfer-xAZ-Out-Bytes

The amount of data (per GB) transferred out of an AWS Availability Zone to another Availability Zone within the same region.

Billing Codes

DataTransfer-xAZ-In-Bytes

The amount of data (per GB) transferred into an AWS Availability Zone from another Availability Zone within the same region. Each Inter-AZ data transfer also has a line item for DataTransfer-xAZ-Out-Bytes in which the cost is applied.

Billing Codes

Load Balancer-Application

LCUUsage

The number of Load Balancer Capacity Units (LCU) used per hour. Charges apply to the LCU metric with the highest usage. Metrics include new connections, active connections, processed bytes, and rule evaluations. See the LCU details section for specific quantities.

Billing Codes

LoadBalancerUsage

The amount of time an Application Load Balancer is running, billed in hourly increments.

Billing Codes

IdleProvisionedLBCapacity

The number of idle Load Balancer Capacity Units (LCU) reserved but not used.

Billing Codes

TS-LoadBalancerUsage

The number of Trust Store unit-hours the Mutual Transport Layer Security (TLS) feature is running, billed in hourly increments. This feature enables secure mutual authentication for clients and servers.

Billing Codes

Outposts-LoadBalancerUsage

The amount of time an Application Load Balancer on Outposts is running, billed in hourly increments.

Billing Codes

Outposts-LCUUsage

The number of Load Balancer Capacity Units (LCU) consumed on Outposts per hour. Charges apply to the LCU metric with the highest usage. Metrics include new connections, active connections, processed bytes, and rule evaluations. See the LCU details section for specific quantities.

Billing Codes

ReservedLCUUsage

The number of Load Balancer Capacity Units (LCU) reserved. LCUs can be reserved to reduce costs and ensure capacity availability

Billing Codes

Load Balancer-Network

LoadBalancerUsage

The amount of time a Network Load Balancer is running, billed in hourly increments.

Billing Codes

LCUUsage

The number of Network Load Balancer Capacity Units (NLCU) used per hour. Charges apply to the NLCU metric with the highest usage. Metrics include new connections/flows, active connections/flows, and processed bytes. See the NLCU details section for specific quantities.

Billing Codes

Load Balancer

LoadBalancerUsage

The amount of time a Classic Load Balancer is running, billed in hourly increments.

Billing Codes

DataProcessing-Bytes

The amount of data processed (per GB) by a Classic Load Balancer.

Billing Codes

IdleProvisionedLBCapacity

The number of idle Load Balancer Capacity Units (LCU) reserved but not used.

Billing Codes

Load Balancer-Gateway

LoadBalancerUsage

The amount of time a Gateway Load Balancer is running, billed in hourly increments.

Billing Codes

LCUUsage

The number of Gateway Load Balancer Capacity Units (GLCU) used per hour. Charges apply to the GLCU metric with the highest usage. Metrics include new connections/flows, active connections/flows, and processed bytes. See the GLCU details section for specific quantities.

Billing Codes