AWSLambda
Each grouping represents a specific way AWS Lambda measures and bills for resource consumption. Click into a code for additional specifications.
Data Transfer
DataTransfer-Regional-Bytes
The amount of data (per GB) transferred between Availability Zones within the same region.
Billing Codes
- DataTransfer-Regional-Bytes
- EU-DataTransfer-Regional-Bytes
- USW2-DataTransfer-Regional-Bytes
- SAE1-DataTransfer-Regional-Bytes
- APS3-DataTransfer-Regional-Bytes
- USE2-DataTransfer-Regional-Bytes
- APS2-DataTransfer-Regional-Bytes
- USW1-DataTransfer-Regional-Bytes
- EUC1-DataTransfer-Regional-Bytes
- APN1-DataTransfer-Regional-Bytes
- EUW2-DataTransfer-Regional-Bytes
- EUW3-DataTransfer-Regional-Bytes
- EUN1-DataTransfer-Regional-Bytes
- UGW1-DataTransfer-Regional-Bytes
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
- USE1-DataTransfer-xAZ-In-Bytes
- EU-DataTransfer-xAZ-In-Bytes
- USW2-DataTransfer-xAZ-In-Bytes
- CAN1-DataTransfer-xAZ-In-Bytes
- APN1-DataTransfer-xAZ-In-Bytes
- USE2-DataTransfer-xAZ-In-Bytes
- USW1-DataTransfer-xAZ-In-Bytes
- EUC1-DataTransfer-xAZ-In-Bytes
- EUW2-DataTransfer-xAZ-In-Bytes
- EUW3-DataTransfer-xAZ-In-Bytes
- APS2-DataTransfer-xAZ-In-Bytes
- APN3-DataTransfer-xAZ-In-Bytes
- APN2-DataTransfer-xAZ-In-Bytes
- UGW1-DataTransfer-xAZ-In-Bytes
- UGE1-DataTransfer-xAZ-In-Bytes
- EUN1-DataTransfer-xAZ-In-Bytes
- APS3-DataTransfer-xAZ-In-Bytes
- SAE1-DataTransfer-xAZ-In-Bytes
- CNN1-DataTransfer-xAZ-In-Bytes
- AFS1-DataTransfer-xAZ-In-Bytes
- APS4-DataTransfer-xAZ-In-Bytes
DataTransfer-Out-Bytes
The amount of data (per GB) transferred out of AWS to the internet.
Billing Codes
- DataTransfer-Out-Bytes
- EU-DataTransfer-Out-Bytes
- EUC1-DataTransfer-Out-Bytes
- USW2-DataTransfer-Out-Bytes
- APN1-DataTransfer-Out-Bytes
- USE2-DataTransfer-Out-Bytes
- CAN1-DataTransfer-Out-Bytes
- USW1-DataTransfer-Out-Bytes
- SAE1-DataTransfer-Out-Bytes
- APS2-DataTransfer-Out-Bytes
- EUW2-DataTransfer-Out-Bytes
- APS3-DataTransfer-Out-Bytes
- UGW1-DataTransfer-Out-Bytes
- EUW3-DataTransfer-Out-Bytes
- APE1-DataTransfer-Out-Bytes
- APN2-DataTransfer-Out-Bytes
- EUN1-DataTransfer-Out-Bytes
- APS1-DataTransfer-Out-Bytes
- AFS1-DataTransfer-Out-Bytes
- APN3-DataTransfer-Out-Bytes
- MES1-DataTransfer-Out-Bytes
- MEC1-DataTransfer-Out-Bytes
- EUS2-DataTransfer-Out-Bytes
- CNN1-DataTransfer-Out-Bytes
- EUS1-DataTransfer-Out-Bytes
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
- USE1-AWS-Out-Bytes
- EU-USE1-AWS-Out-Bytes
- USW2-USE2-AWS-Out-Bytes
- USW2-USE1-AWS-Out-Bytes
- EUW2-EU-AWS-Out-Bytes
- EUC1-APN1-AWS-Out-Bytes
- APN1-USE1-AWS-Out-Bytes
- USE1-USE2-AWS-Out-Bytes
- EU-CAN1-AWS-Out-Bytes
- EU-APN2-AWS-Out-Bytes
- EU-USW1-AWS-Out-Bytes
- EU-APS3-AWS-Out-Bytes
- EU-USE2-AWS-Out-Bytes
- EU-EUN1-AWS-Out-Bytes
- EU-APS2-AWS-Out-Bytes
- EU-SAE1-AWS-Out-Bytes
- EU-APS1-AWS-Out-Bytes
- EU-APN3-AWS-Out-Bytes
- EU-EUW3-AWS-Out-Bytes
- EU-APN1-AWS-Out-Bytes
- EU-EUC1-AWS-Out-Bytes
- EU-USW2-AWS-Out-Bytes
- EU-EUW2-AWS-Out-Bytes
- USE1-USW2-AWS-Out-Bytes
- USE1-EU-AWS-Out-Bytes
- EU-AWS-Out-Bytes
- USE1-APN1-AWS-Out-Bytes
- USE1-APS1-AWS-Out-Bytes
- USE1-APN3-AWS-Out-Bytes
- USE1-EUN1-AWS-Out-Bytes
- USE1-EUW3-AWS-Out-Bytes
- USE1-APN2-AWS-Out-Bytes
- USE1-EUC1-AWS-Out-Bytes
- USE1-APS2-AWS-Out-Bytes
- USE1-EUW2-AWS-Out-Bytes
- USE1-SAE1-AWS-Out-Bytes
- USE1-APS3-AWS-Out-Bytes
- USE1-USW1-AWS-Out-Bytes
- USE1-CAN1-AWS-Out-Bytes
- USW2-APS3-AWS-Out-Bytes
- EUC1-USW2-AWS-Out-Bytes
- APN1-USW2-AWS-Out-Bytes
- USE2-USW2-AWS-Out-Bytes
- USE1-APE1-AWS-Out-Bytes
- USE1-MEC1-AWS-Out-Bytes
- USW2-APS2-AWS-Out-Bytes
- USE2-EUC1-AWS-Out-Bytes
- EUC1-USE1-AWS-Out-Bytes
- USW1-USE1-AWS-Out-Bytes
- USE2-USE1-AWS-Out-Bytes
- EUS1-EU-AWS-Out-Bytes
- EUC1-EU-AWS-Out-Bytes
- EUS1-USE1-AWS-Out-Bytes
- USW2-EUW3-AWS-Out-Bytes
- USW2-EUC1-AWS-Out-Bytes
- USW2-APS1-AWS-Out-Bytes
- USW2-APN3-AWS-Out-Bytes
- USW2-EUW2-AWS-Out-Bytes
- USW2-CAN1-AWS-Out-Bytes
- USW2-EU-AWS-Out-Bytes
- USW2-USW1-AWS-Out-Bytes
- USW2-APN2-AWS-Out-Bytes
- USW2-APN1-AWS-Out-Bytes
- USW2-EUN1-AWS-Out-Bytes
- USW2-SAE1-AWS-Out-Bytes
- CAN1-EU-AWS-Out-Bytes
- SAE1-USW2-AWS-Out-Bytes
- APS2-USE1-AWS-Out-Bytes
- USE1-APS5-AWS-Out-Bytes
- USE1-EUS2-AWS-Out-Bytes
- USE1-MES1-AWS-Out-Bytes
- USE1-CAN2-AWS-Out-Bytes
- USE1-APS4-AWS-Out-Bytes
- USE1-EUS1-AWS-Out-Bytes
- USE1-ILC1-AWS-Out-Bytes
- USE1-AFS1-AWS-Out-Bytes
- USE1-APS6-AWS-Out-Bytes
- USE1-EUC2-AWS-Out-Bytes
- EU-APE1-AWS-Out-Bytes
- CAN1-USE1-AWS-Out-Bytes
- UGW1-USW2-AWS-Out-Bytes
- UGW1-USE1-AWS-Out-Bytes
- APN1-SAE1-AWS-Out-Bytes
- APS2-SAE1-AWS-Out-Bytes
- EUW2-USE1-AWS-Out-Bytes
- APS3-SAE1-AWS-Out-Bytes
- APS1-SAE1-AWS-Out-Bytes
- EUW2-SAE1-AWS-Out-Bytes
- EUC1-SAE1-AWS-Out-Bytes
- SAE1-AWS-Out-Bytes
- USE2-SAE1-AWS-Out-Bytes
- SAE1-USE1-AWS-Out-Bytes
- APN2-SAE1-AWS-Out-Bytes
- USW1-USW2-AWS-Out-Bytes
- USW1-SAE1-AWS-Out-Bytes
- USE2-EUN1-AWS-Out-Bytes
- USE2-APS3-AWS-Out-Bytes
- USE2-APN2-AWS-Out-Bytes
- USE2-CAN1-AWS-Out-Bytes
- USE2-EU-AWS-Out-Bytes
- USE2-APS1-AWS-Out-Bytes
- USE2-USW1-AWS-Out-Bytes
- USE2-EUW2-AWS-Out-Bytes
- USE2-APN3-AWS-Out-Bytes
- USE2-EUW3-AWS-Out-Bytes
- USE2-APN1-AWS-Out-Bytes
- USE2-APS2-AWS-Out-Bytes
- APS1-USE1-AWS-Out-Bytes
- EU-UGE1-AWS-Out-Bytes
- EU-AFS1-AWS-Out-Bytes
- EU-EUS2-AWS-Out-Bytes
- EU-MES1-AWS-Out-Bytes
- EU-EUS1-AWS-Out-Bytes
- EU-UGW1-AWS-Out-Bytes
- EU-MEC1-AWS-Out-Bytes
- APS2-USW1-AWS-Out-Bytes
- CAN1-APN1-AWS-Out-Bytes
- APS2-USE2-AWS-Out-Bytes
- APS2-APN1-AWS-Out-Bytes
- CAN1-EUC1-AWS-Out-Bytes
- CAN1-APS3-AWS-Out-Bytes
- CAN1-APS1-AWS-Out-Bytes
- USE1-UGW1-AWS-Out-Bytes
- APS2-APN2-AWS-Out-Bytes
- CAN1-USE2-AWS-Out-Bytes
- APS2-USW2-AWS-Out-Bytes
- CAN1-EUW3-AWS-Out-Bytes
- APS2-EUC1-AWS-Out-Bytes
- APS2-CAN1-AWS-Out-Bytes
- APS2-APS1-AWS-Out-Bytes
- USE1-UGE1-AWS-Out-Bytes
- CAN1-APS2-AWS-Out-Bytes
- APS2-EUW3-AWS-Out-Bytes
- APS2-APS3-AWS-Out-Bytes
- CAN1-EUN1-AWS-Out-Bytes
- CAN1-EUW2-AWS-Out-Bytes
- CAN1-APE1-AWS-Out-Bytes
- CAN1-USW2-AWS-Out-Bytes
- APS2-EUW2-AWS-Out-Bytes
- APS2-EU-AWS-Out-Bytes
- CAN1-USW1-AWS-Out-Bytes
- APS2-EUN1-AWS-Out-Bytes
- EUW2-APN1-AWS-Out-Bytes
- USE2-AWS-Out-Bytes
- APN1-APS2-AWS-Out-Bytes
- USW2-AWS-Out-Bytes
- APS3-USE1-AWS-Out-Bytes
- EUC1-USE2-AWS-Out-Bytes
- USW1-USE2-AWS-Out-Bytes
- APS3-USE2-AWS-Out-Bytes
- EUW3-USE2-AWS-Out-Bytes
- EUW2-USE2-AWS-Out-Bytes
- EUW3-USE1-AWS-Out-Bytes
- APS1-USE2-AWS-Out-Bytes
- EUW3-EUC1-AWS-Out-Bytes
- APE1-USE1-AWS-Out-Bytes
- APE1-USW2-AWS-Out-Bytes
- APN2-APS1-AWS-Out-Bytes
- EUW2-EUC1-AWS-Out-Bytes
- APN2-APN1-AWS-Out-Bytes
- APE1-APN1-AWS-Out-Bytes
- EUW3-EU-AWS-Out-Bytes
- EUW3-EUW2-AWS-Out-Bytes
- EUN1-EUC1-AWS-Out-Bytes
- APN1-USE2-AWS-Out-Bytes
- EUN1-EU-AWS-Out-Bytes
- EUW2-USW1-AWS-Out-Bytes
- EUW2-MES1-AWS-Out-Bytes
- USW1-EUC1-AWS-Out-Bytes
- EUW2-EUW3-AWS-Out-Bytes
- USW1-APS2-AWS-Out-Bytes
- APE1-APS1-AWS-Out-Bytes
- SAE1-USE2-AWS-Out-Bytes
- APN2-USE1-AWS-Out-Bytes
- APN1-APS1-AWS-Out-Bytes
- USW1-APS3-AWS-Out-Bytes
- EUN1-USE1-AWS-Out-Bytes
- USW1-EU-AWS-Out-Bytes
- EUC1-EUS1-AWS-Out-Bytes
- AFS1-EU-AWS-Out-Bytes
- APE1-USE2-AWS-Out-Bytes
- AFS1-USE1-AWS-Out-Bytes
- APS1-APE1-AWS-Out-Bytes
- EUS1-EUC1-AWS-Out-Bytes
- EU-APS4-AWS-Out-Bytes
- EU-EUC2-AWS-Out-Bytes
- APN2-USW2-AWS-Out-Bytes
- APS3-APN2-AWS-Out-Bytes
- APS3-APS1-AWS-Out-Bytes
- APS3-USW1-AWS-Out-Bytes
- APS1-APS2-AWS-Out-Bytes
- USW2-MES1-AWS-Out-Bytes
- USW2-ILC1-AWS-Out-Bytes
- USW2-EUS2-AWS-Out-Bytes
- CAN1-UGW1-AWS-Out-Bytes
- EUC1-APE1-AWS-Out-Bytes
- EUC1-APN3-AWS-Out-Bytes
- EUC1-EUW2-AWS-Out-Bytes
- EUC1-APS2-AWS-Out-Bytes
- EUC1-APS1-AWS-Out-Bytes
- EUC1-EUN1-AWS-Out-Bytes
- EUC1-APN2-AWS-Out-Bytes
- EUC1-EUW3-AWS-Out-Bytes
- EUC1-APS3-AWS-Out-Bytes
- EUC1-USW1-AWS-Out-Bytes
- EUC1-MEC1-AWS-Out-Bytes
- USE2-EUS1-AWS-Out-Bytes
- USE2-EUS2-AWS-Out-Bytes
- USE2-MES1-AWS-Out-Bytes
- USE2-APE1-AWS-Out-Bytes
- USE2-AFS1-AWS-Out-Bytes
- USE2-CAN2-AWS-Out-Bytes
- USE2-APS4-AWS-Out-Bytes
- USE2-APS6-AWS-Out-Bytes
- APS1-APS3-AWS-Out-Bytes
- USW1-APE1-AWS-Out-Bytes
- EUC1-CAN1-AWS-Out-Bytes
- APS2-APS6-AWS-Out-Bytes
- APS2-UGW1-AWS-Out-Bytes
- USW2-APE1-AWS-Out-Bytes
- USW2-AFS1-AWS-Out-Bytes
- USW2-EUS1-AWS-Out-Bytes
- USE2-MEC1-AWS-Out-Bytes
- CAN1-EUC2-AWS-Out-Bytes
- CAN1-SAE1-AWS-Out-Bytes
- APS2-APN3-AWS-Out-Bytes
- USW2-APS4-AWS-Out-Bytes
- EUW2-USW2-AWS-Out-Bytes
- AFS1-EUC1-AWS-Out-Bytes
- APS1-EUC1-AWS-Out-Bytes
- APS3-EUC1-AWS-Out-Bytes
- USW1-APN1-AWS-Out-Bytes
- APN3-APN1-AWS-Out-Bytes
- APS1-APN1-AWS-Out-Bytes
- EU-APS6-AWS-Out-Bytes
- USE2-APS5-AWS-Out-Bytes
- USE2-EUC2-AWS-Out-Bytes
- USE2-ILC1-AWS-Out-Bytes
- APS2-MES1-AWS-Out-Bytes
- EUW3-USW2-AWS-Out-Bytes
- APS1-EU-AWS-Out-Bytes
- APS3-APS2-AWS-Out-Bytes
- SAE1-EUC1-AWS-Out-Bytes
- USW1-UGW1-AWS-Out-Bytes
- APN1-EUW3-AWS-Out-Bytes
- APN1-USW1-AWS-Out-Bytes
- APN1-EUW2-AWS-Out-Bytes
- APN1-EUN1-AWS-Out-Bytes
- APN1-APS3-AWS-Out-Bytes
- APN1-APN3-AWS-Out-Bytes
- APN1-CAN1-AWS-Out-Bytes
- APN1-EU-AWS-Out-Bytes
- APN1-EUC1-AWS-Out-Bytes
- APN1-APN2-AWS-Out-Bytes
- USW2-UGW1-AWS-Out-Bytes
- USE1-PER1-AWS-Out-Bytes
- USE1-MNL1-AWS-Out-Bytes
- USE1-AKL1-AWS-Out-Bytes
- USE1-APS7-AWS-Out-Bytes
- USE1-LOS1-AWS-Out-Bytes
- USE1-MCT1-AWS-Out-Bytes
- USE1-DEL1-AWS-Out-Bytes
- USE1-BKK1-AWS-Out-Bytes
- USE1-CCU1-AWS-Out-Bytes
- USE1-TPE1-AWS-Out-Bytes
- APS3-USW2-AWS-Out-Bytes
- APS1-USW2-AWS-Out-Bytes
- APS3-MEC1-AWS-Out-Bytes
- APS2-APS4-AWS-Out-Bytes
- EUW3-EUS1-AWS-Out-Bytes
- USW1-APS1-AWS-Out-Bytes
- EUN1-APS1-AWS-Out-Bytes
- EUC1-MES1-AWS-Out-Bytes
- EUN1-USE2-AWS-Out-Bytes
- EUC1-EUC2-AWS-Out-Bytes
- APS1-USW1-AWS-Out-Bytes
- EUW2-EUN1-AWS-Out-Bytes
- EUW3-MES1-AWS-Out-Bytes
- USW2-EUC2-AWS-Out-Bytes
- USW2-CAN2-AWS-Out-Bytes
- USW2-APS5-AWS-Out-Bytes
- USW2-APS6-AWS-Out-Bytes
- APS3-APN1-AWS-Out-Bytes
- EUW2-APS1-AWS-Out-Bytes
- EUN1-USW2-AWS-Out-Bytes
- APN3-USW2-AWS-Out-Bytes
- APS1-APS4-AWS-Out-Bytes
- EUC1-ILC1-AWS-Out-Bytes
- EUW3-EUN1-AWS-Out-Bytes
- AFS1-USW2-AWS-Out-Bytes
- APS3-MES1-AWS-Out-Bytes
- EUW2-APS2-AWS-Out-Bytes
- UGW1-UGE1-AWS-Out-Bytes
- EUN1-CAN1-AWS-Out-Bytes
- APN3-APS1-AWS-Out-Bytes
- APS1-CAN1-AWS-Out-Bytes
- EUN1-EUW2-AWS-Out-Bytes
- EUN1-APN1-AWS-Out-Bytes
- SAE1-APN1-AWS-Out-Bytes
- APN2-USW1-AWS-Out-Bytes
- AFS1-APS1-AWS-Out-Bytes
- SAE1-APS2-AWS-Out-Bytes
- EUW3-APN2-AWS-Out-Bytes
- EUW3-USW1-AWS-Out-Bytes
- AFS1-APN1-AWS-Out-Bytes
- AFS1-EUW3-AWS-Out-Bytes
- APE1-APN2-AWS-Out-Bytes
- SAE1-EUW2-AWS-Out-Bytes
- APN3-USW1-AWS-Out-Bytes
- APE1-USW1-AWS-Out-Bytes
- APN3-USE1-AWS-Out-Bytes
- APN3-CAN1-AWS-Out-Bytes
- USW1-EUW2-AWS-Out-Bytes
- USW1-CAN1-AWS-Out-Bytes
- AFS1-APN2-AWS-Out-Bytes
- EUN1-EUW3-AWS-Out-Bytes
- SAE1-EU-AWS-Out-Bytes
- APN3-EUC1-AWS-Out-Bytes
- EUW3-APS2-AWS-Out-Bytes
- APS3-EU-AWS-Out-Bytes
- EUC1-AFS1-AWS-Out-Bytes
- EUW2-CAN1-AWS-Out-Bytes
- APS1-EUW2-AWS-Out-Bytes
- APN3-APS2-AWS-Out-Bytes
- APN2-EUW3-AWS-Out-Bytes
- APE1-EUW2-AWS-Out-Bytes
- APE1-APS2-AWS-Out-Bytes
- AFS1-APS2-AWS-Out-Bytes
- APN2-EU-AWS-Out-Bytes
- SAE1-APN2-AWS-Out-Bytes
- APN2-EUC1-AWS-Out-Bytes
- APN2-CAN1-AWS-Out-Bytes
- AFS1-CAN1-AWS-Out-Bytes
- EUN1-USW1-AWS-Out-Bytes
- APN3-APN2-AWS-Out-Bytes
- APS1-EUW3-AWS-Out-Bytes
- APN3-EUW3-AWS-Out-Bytes
- USW1-APN2-AWS-Out-Bytes
- APN2-USE2-AWS-Out-Bytes
- APE1-EU-AWS-Out-Bytes
- EUW3-CAN1-AWS-Out-Bytes
- APS3-EUW3-AWS-Out-Bytes
- EUN1-MES1-AWS-Out-Bytes
- CAN1-UGE1-AWS-Out-Bytes
- EUC1-UGW1-AWS-Out-Bytes
- APE1-EUC1-AWS-Out-Bytes
- APS1-APN2-AWS-Out-Bytes
- APS3-EUW2-AWS-Out-Bytes
- CAN1-APN2-AWS-Out-Bytes
- USW1-EUN1-AWS-Out-Bytes
- APN1-APE1-AWS-Out-Bytes
- EUW3-APS1-AWS-Out-Bytes
- AFS1-USW1-AWS-Out-Bytes
- APS1-MES1-AWS-Out-Bytes
- AFS1-USE2-AWS-Out-Bytes
- APN2-APN3-AWS-Out-Bytes
- EUW2-AFS1-AWS-Out-Bytes
- AFS1-EUW2-AWS-Out-Bytes
- APN3-APE1-AWS-Out-Bytes
- APS1-EUN1-AWS-Out-Bytes
- APE1-SAE1-AWS-Out-Bytes
- USW1-EUW3-AWS-Out-Bytes
- EUN1-AFS1-AWS-Out-Bytes
- AFS1-MES1-AWS-Out-Bytes
- AFS1-UGW1-AWS-Out-Bytes
- AFS1-APS3-AWS-Out-Bytes
- APS2-AKL1-AWS-Out-Bytes
- USW2-UGE1-AWS-Out-Bytes
- SAE1-APS1-AWS-Out-Bytes
- APE1-APN3-AWS-Out-Bytes
- EUW2-APS3-AWS-Out-Bytes
- SAE1-USW1-AWS-Out-Bytes
- EUN1-MEC1-AWS-Out-Bytes
- APS3-APE1-AWS-Out-Bytes
- USW1-MES1-AWS-Out-Bytes
- USW1-APS4-AWS-Out-Bytes
- UGE1-UGW1-AWS-Out-Bytes
- USE1-CHI1-AWS-Out-Bytes
- APS2-MEC1-AWS-Out-Bytes
- EUW3-EUS2-AWS-Out-Bytes
- APE1-EUN1-AWS-Out-Bytes
- APE1-APS3-AWS-Out-Bytes
- CAN2-USE1-AWS-Out-Bytes
- APS3-UGW1-AWS-Out-Bytes
- APE1-APS5-AWS-Out-Bytes
- APE1-EUW3-AWS-Out-Bytes
- APE1-CAN1-AWS-Out-Bytes
- APE1-APS6-AWS-Out-Bytes
- APE1-EUC2-AWS-Out-Bytes
- APE1-APS7-AWS-Out-Bytes
- APE1-AFS1-AWS-Out-Bytes
- SAE1-EUN1-AWS-Out-Bytes
- EUW3-EUC2-AWS-Out-Bytes
- SAE1-APS3-AWS-Out-Bytes
- APS1-APN3-AWS-Out-Bytes
- APN2-APS2-AWS-Out-Bytes
- APS3-EUN1-AWS-Out-Bytes
- USW2-PER1-AWS-Out-Bytes
- EUN1-SAE1-AWS-Out-Bytes
- EU-APS5-AWS-Out-Bytes
- EUW2-EUS1-AWS-Out-Bytes
- EUW2-APN2-AWS-Out-Bytes
- USW1-EUS1-AWS-Out-Bytes
- APS3-APS5-AWS-Out-Bytes
- EUW3-APS3-AWS-Out-Bytes
- APN2-APS3-AWS-Out-Bytes
- USE2-UGW1-AWS-Out-Bytes
- APN2-APE1-AWS-Out-Bytes
- EUN1-APN2-AWS-Out-Bytes
- SAE1-EUW3-AWS-Out-Bytes
- APN3-EU-AWS-Out-Bytes
- EUN1-APS3-AWS-Out-Bytes
- APN3-APS3-AWS-Out-Bytes
- SAE1-CAN1-AWS-Out-Bytes
- APN3-USE2-AWS-Out-Bytes
- EUN1-APS2-AWS-Out-Bytes
- APS3-CAN1-AWS-Out-Bytes
- EUW3-APN1-AWS-Out-Bytes
- APS2-APE1-AWS-Out-Bytes
- EUW3-MEC1-AWS-Out-Bytes
- EUW2-UGW1-AWS-Out-Bytes
- APN3-EUW2-AWS-Out-Bytes
- USE1-CPH1-AWS-Out-Bytes
- USE1-ATL1-AWS-Out-Bytes
- USW1-APN3-AWS-Out-Bytes
- USW2-MEC1-AWS-Out-Bytes
- USW1-AFS1-AWS-Out-Bytes
- USW1-UGE1-AWS-Out-Bytes
- EUW2-APS5-AWS-Out-Bytes
- EUW2-EUC2-AWS-Out-Bytes
- EUW2-SGGOV1-AWS-Out-Bytes
- EUW2-APS4-AWS-Out-Bytes
- EUW2-ILC1-AWS-Out-Bytes
- EUW2-MEC1-AWS-Out-Bytes
- EUW2-APE1-AWS-Out-Bytes
- EUW2-EUS2-AWS-Out-Bytes
- EUW2-APS6-AWS-Out-Bytes
- EUW2-APS7-AWS-Out-Bytes
- EUW2-UGE1-AWS-Out-Bytes
- EUW2-CAN2-AWS-Out-Bytes
- EUW2-APN3-AWS-Out-Bytes
- EUW2-AKL1-AWS-Out-Bytes
- EUW2-PER1-AWS-Out-Bytes
- USW1-MEC1-AWS-Out-Bytes
- MES1-APS3-AWS-Out-Bytes
- MES1-EU-AWS-Out-Bytes
- USW2-MIA1-AWS-Out-Bytes
- MES1-MEC1-AWS-Out-Bytes
- APN2-EUN1-AWS-Out-Bytes
- USW1-EUS2-AWS-Out-Bytes
- AFS1-SAE1-AWS-Out-Bytes
- EUW3-AFS1-AWS-Out-Bytes
- APN2-EUW2-AWS-Out-Bytes
- MEC1-APS3-AWS-Out-Bytes
- MEC1-MES1-AWS-Out-Bytes
- USE1-MIA1-AWS-Out-Bytes
- EUN1-UGW1-AWS-Out-Bytes
- APE1-ILC1-AWS-Out-Bytes
- EUW3-ILC1-AWS-Out-Bytes
- APE1-EUS1-AWS-Out-Bytes
- APE1-CAN2-AWS-Out-Bytes
- EUC1-UGE1-AWS-Out-Bytes
- EUC1-EUS2-AWS-Out-Bytes
- APS2-PER1-AWS-Out-Bytes
- APE1-APS4-AWS-Out-Bytes
- APE1-EUS2-AWS-Out-Bytes
- APE1-MEC1-AWS-Out-Bytes
- APN1-EUS1-AWS-Out-Bytes
- APE1-MES1-AWS-Out-Bytes
- USW1-EUC2-AWS-Out-Bytes
- EUW3-SAE1-AWS-Out-Bytes
- APS1-APS7-AWS-Out-Bytes
- EUN1-AWS-Out-Bytes
- APS2-AWS-Out-Bytes
- EUC1-AWS-Out-Bytes
- USW1-CAN2-AWS-Out-Bytes
- AFS1-EUN1-AWS-Out-Bytes
- EUC1-APS4-AWS-Out-Bytes
- USE1-PHX1-AWS-Out-Bytes
- CAN1-APN3-AWS-Out-Bytes
- CAN1-CAN2-AWS-Out-Bytes
- USE1-SEA1-AWS-Out-Bytes
- EUS2-EUW3-AWS-Out-Bytes
- EUW3-APE1-AWS-Out-Bytes
- USE1-DFW1-AWS-Out-Bytes
- APN1-AWS-Out-Bytes
- USE2-UGE1-AWS-Out-Bytes
- USW1-TPE1-AWS-Out-Bytes
- USE1-SCL1-AWS-Out-Bytes
- EUW2-AWS-Out-Bytes
- APS6-USE1-AWS-Out-Bytes
- USE1-NYC1-AWS-Out-Bytes
- APS3-AWS-Out-Bytes
- USW1-AWS-Out-Bytes
- APN2-AFS1-AWS-Out-Bytes
- APS3-APN3-AWS-Out-Bytes
- SAE1-EUS1-AWS-Out-Bytes
- SAE1-MES1-AWS-Out-Bytes
- SAE1-AFS1-AWS-Out-Bytes
- SAE1-APN3-AWS-Out-Bytes
- SAE1-APE1-AWS-Out-Bytes
- APN3-SAE1-AWS-Out-Bytes
- USW1-APS7-AWS-Out-Bytes
- EUW2-LAX1-AWS-Out-Bytes
- USE1-USE1WL1ATL1-AWS-Out-Bytes
- USE1-USW2WL1-AWS-Out-Bytes
- USE1-WAW1-AWS-Out-Bytes
- USE1-SGGOV1-AWS-Out-Bytes
- USE1-USE1WL1MSP1-AWS-Out-Bytes
- USE1-APNE1WL1KIX1-AWS-Out-Bytes
- USE1-USW2WL1LAS1-AWS-Out-Bytes
- USE1-MCI2-AWS-Out-Bytes
- USE1-LAS1-AWS-Out-Bytes
- USE1-USE1WL1BWAS1-AWS-Out-Bytes
- USE1-USE1WL1CLT1-AWS-Out-Bytes
- USE1-IAH1-AWS-Out-Bytes
- USE1-PDX1-AWS-Out-Bytes
- USE1-USE1WL1-AWS-Out-Bytes
- USE1-APNE2WL1SEL1-AWS-Out-Bytes
- USE1-DEN1-AWS-Out-Bytes
- USE1-EUC1WL1DTM1-AWS-Out-Bytes
- USE1-PHL1-AWS-Out-Bytes
- USE1-CAC1WL1YTO1-AWS-Out-Bytes
- USE1-QRO1-AWS-Out-Bytes
- USE1-LAX1-AWS-Out-Bytes
- USE1-USE1WL1DFW1-AWS-Out-Bytes
- USE1-BOS1-AWS-Out-Bytes
- USE1-MSP1-AWS-Out-Bytes
- USE1-HNL1-AWS-Out-Bytes
- EUC1-APS5-AWS-Out-Bytes
- USW2-SGGOV1-AWS-Out-Bytes
- APS2-EUS1-AWS-Out-Bytes
- APS2-AFS1-AWS-Out-Bytes
- EUC1-APS6-AWS-Out-Bytes
- APN1-MES1-AWS-Out-Bytes
- APS1-UGW1-AWS-Out-Bytes
- USW1-ILC1-AWS-Out-Bytes
- USW1-APS6-AWS-Out-Bytes
- MEC1-EUC1-AWS-Out-Bytes
- MEC1-USW2-AWS-Out-Bytes
- MES1-USW2-AWS-Out-Bytes
- MES1-EUC1-AWS-Out-Bytes
- MEC1-USE1-AWS-Out-Bytes
- EUW3-AWS-Out-Bytes
- EU-CAN2-AWS-Out-Bytes
- APN2-UGE1-AWS-Out-Bytes
- USW1-APS5-AWS-Out-Bytes
- USW1-LAS1-AWS-Out-Bytes
- USW1-AKL1-AWS-Out-Bytes
- APS3-EUS2-AWS-Out-Bytes
- EU-PER1-AWS-Out-Bytes
- EUC1-IAH1-AWS-Out-Bytes
- EUC1-DEN1-AWS-Out-Bytes
- APS3-AFS1-AWS-Out-Bytes
- CNN1-CNW1-AWS-Out-Bytes
- EUC1-PER1-AWS-Out-Bytes
- APS3-EUS1-AWS-Out-Bytes
- APN2-MES1-AWS-Out-Bytes
- EUC1-MIA1-AWS-Out-Bytes
- EU-APS7-AWS-Out-Bytes
- APS2-UGE1-AWS-Out-Bytes
- APS1-AWS-Out-Bytes
- USW1-PHX1-AWS-Out-Bytes
- USE1-MXC1-AWS-Out-Bytes
- USE1-APS9-AWS-Out-Bytes
- USW1-LAX1-AWS-Out-Bytes
- USE1-HEL1-AWS-Out-Bytes
- APN2-EUS1-AWS-Out-Bytes
- EU-ILC1-AWS-Out-Bytes
- EUW2-ATL1-AWS-Out-Bytes
- APN2-EUC2-AWS-Out-Bytes
- APN2-UGW1-AWS-Out-Bytes
- AFS1-MEC1-AWS-Out-Bytes
- USW1-MIA1-AWS-Out-Bytes
- EUS1-USW2-AWS-Out-Bytes
- EUC1-CHI1-AWS-Out-Bytes
- USW2-APS7-AWS-Out-Bytes
- USE1-LIM1-AWS-Out-Bytes
- EUN1-EUS1-AWS-Out-Bytes
- APS4-USE1-AWS-Out-Bytes
- CAN1-AWS-Out-Bytes
- APN2-MEC1-AWS-Out-Bytes
- APS5-APS3-AWS-Out-Bytes
- APS5-APS1-AWS-Out-Bytes
- APS1-EUS1-AWS-Out-Bytes
- APS1-APS5-AWS-Out-Bytes
- EUC1-HEL1-AWS-Out-Bytes
- AFS1-EUS1-AWS-Out-Bytes
- EUC1-QRO1-AWS-Out-Bytes
- USW1-WAW1-AWS-Out-Bytes
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
- DataTransfer-In-Bytes
- EU-DataTransfer-In-Bytes
- EUC1-DataTransfer-In-Bytes
- USW2-DataTransfer-In-Bytes
- APN1-DataTransfer-In-Bytes
- USE2-DataTransfer-In-Bytes
- CAN1-DataTransfer-In-Bytes
- USW1-DataTransfer-In-Bytes
- SAE1-DataTransfer-In-Bytes
- APS2-DataTransfer-In-Bytes
- EUW2-DataTransfer-In-Bytes
- APS3-DataTransfer-In-Bytes
- UGW1-DataTransfer-In-Bytes
- EUW3-DataTransfer-In-Bytes
- AFS1-DataTransfer-In-Bytes
- EUN1-DataTransfer-In-Bytes
- APS1-DataTransfer-In-Bytes
- APN2-DataTransfer-In-Bytes
- APE1-DataTransfer-In-Bytes
- APN3-DataTransfer-In-Bytes
- MES1-DataTransfer-In-Bytes
- MEC1-DataTransfer-In-Bytes
- EUS2-DataTransfer-In-Bytes
- CNN1-DataTransfer-In-Bytes
- EUS1-DataTransfer-In-Bytes
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
- USE1-AWS-In-Bytes
- EU-USE1-AWS-In-Bytes
- USW2-USE1-AWS-In-Bytes
- USW2-USE2-AWS-In-Bytes
- EUW2-EU-AWS-In-Bytes
- EUC1-APN1-AWS-In-Bytes
- APN1-USE1-AWS-In-Bytes
- USE1-USE2-AWS-In-Bytes
- EU-APS3-AWS-In-Bytes
- EU-APN1-AWS-In-Bytes
- EU-CAN1-AWS-In-Bytes
- EU-SAE1-AWS-In-Bytes
- EU-EUW3-AWS-In-Bytes
- EU-EUW2-AWS-In-Bytes
- EU-EUN1-AWS-In-Bytes
- EU-USW2-AWS-In-Bytes
- EU-APN2-AWS-In-Bytes
- EU-USW1-AWS-In-Bytes
- EU-APS2-AWS-In-Bytes
- EU-EUC1-AWS-In-Bytes
- EU-USE2-AWS-In-Bytes
- EU-APN3-AWS-In-Bytes
- EU-APS1-AWS-In-Bytes
- USE1-USW2-AWS-In-Bytes
- USE1-EU-AWS-In-Bytes
- EU-AWS-In-Bytes
- USE1-EUW3-AWS-In-Bytes
- USE1-APN1-AWS-In-Bytes
- USE1-APS1-AWS-In-Bytes
- USE1-EUC1-AWS-In-Bytes
- USE1-APN3-AWS-In-Bytes
- USE1-APN2-AWS-In-Bytes
- USE1-SAE1-AWS-In-Bytes
- USE1-APS3-AWS-In-Bytes
- USE1-APS2-AWS-In-Bytes
- USE1-USW1-AWS-In-Bytes
- USE1-CAN1-AWS-In-Bytes
- USE1-EUW2-AWS-In-Bytes
- USE1-EUN1-AWS-In-Bytes
- APN1-USW2-AWS-In-Bytes
- EUC1-USW2-AWS-In-Bytes
- USW2-APS3-AWS-In-Bytes
- USE2-USW2-AWS-In-Bytes
- USE1-MEC1-AWS-In-Bytes
- USE1-APE1-AWS-In-Bytes
- USW2-APS2-AWS-In-Bytes
- EUC1-USE1-AWS-In-Bytes
- USE2-EUC1-AWS-In-Bytes
- USW1-USE1-AWS-In-Bytes
- USE2-USE1-AWS-In-Bytes
- EUS1-EU-AWS-In-Bytes
- EUC1-EU-AWS-In-Bytes
- EUS1-USE1-AWS-In-Bytes
- USW2-USW1-AWS-In-Bytes
- USW2-EUC1-AWS-In-Bytes
- USW2-APS1-AWS-In-Bytes
- USW2-EUN1-AWS-In-Bytes
- USW2-APN1-AWS-In-Bytes
- USW2-APN3-AWS-In-Bytes
- USW2-APN2-AWS-In-Bytes
- USW2-SAE1-AWS-In-Bytes
- USW2-EUW3-AWS-In-Bytes
- USW2-EU-AWS-In-Bytes
- USW2-CAN1-AWS-In-Bytes
- USW2-EUW2-AWS-In-Bytes
- CAN1-EU-AWS-In-Bytes
- SAE1-USW2-AWS-In-Bytes
- APS2-USE1-AWS-In-Bytes
- USE1-APS4-AWS-In-Bytes
- USE1-ILC1-AWS-In-Bytes
- USE1-EUS1-AWS-In-Bytes
- USE1-EUS2-AWS-In-Bytes
- USE1-EUC2-AWS-In-Bytes
- USE1-AFS1-AWS-In-Bytes
- USE1-APS5-AWS-In-Bytes
- USE1-CAN2-AWS-In-Bytes
- USE1-MES1-AWS-In-Bytes
- USE1-APS6-AWS-In-Bytes
- EU-APE1-AWS-In-Bytes
- CAN1-USE1-AWS-In-Bytes
- UGW1-USW2-AWS-In-Bytes
- UGW1-USE1-AWS-In-Bytes
- APN1-SAE1-AWS-In-Bytes
- EUW2-USE1-AWS-In-Bytes
- EUW2-SAE1-AWS-In-Bytes
- EUC1-SAE1-AWS-In-Bytes
- APS3-SAE1-AWS-In-Bytes
- APS2-SAE1-AWS-In-Bytes
- SAE1-AWS-In-Bytes
- APS1-SAE1-AWS-In-Bytes
- SAE1-USE1-AWS-In-Bytes
- USE2-SAE1-AWS-In-Bytes
- APN2-SAE1-AWS-In-Bytes
- USW1-SAE1-AWS-In-Bytes
- USW1-USW2-AWS-In-Bytes
- USE2-EUW3-AWS-In-Bytes
- USE2-CAN1-AWS-In-Bytes
- USE2-EUW2-AWS-In-Bytes
- USE2-USW1-AWS-In-Bytes
- USE2-APS1-AWS-In-Bytes
- USE2-APN3-AWS-In-Bytes
- USE2-EU-AWS-In-Bytes
- USE2-APN2-AWS-In-Bytes
- USE2-APS2-AWS-In-Bytes
- USE2-APS3-AWS-In-Bytes
- USE2-EUN1-AWS-In-Bytes
- USE2-APN1-AWS-In-Bytes
- APS1-USE1-AWS-In-Bytes
- EU-AFS1-AWS-In-Bytes
- EU-UGW1-AWS-In-Bytes
- EU-EUS2-AWS-In-Bytes
- EU-MES1-AWS-In-Bytes
- EU-MEC1-AWS-In-Bytes
- EU-UGE1-AWS-In-Bytes
- EU-EUS1-AWS-In-Bytes
- CAN1-APE1-AWS-In-Bytes
- CAN1-APN1-AWS-In-Bytes
- APS2-APS1-AWS-In-Bytes
- APS2-APS3-AWS-In-Bytes
- CAN1-APS2-AWS-In-Bytes
- CAN1-EUW3-AWS-In-Bytes
- USE1-UGW1-AWS-In-Bytes
- USE1-UGE1-AWS-In-Bytes
- CAN1-USE2-AWS-In-Bytes
- APS2-USW1-AWS-In-Bytes
- APS2-EUC1-AWS-In-Bytes
- APS2-USE2-AWS-In-Bytes
- APS2-EU-AWS-In-Bytes
- CAN1-USW1-AWS-In-Bytes
- CAN1-APS3-AWS-In-Bytes
- APS2-APN1-AWS-In-Bytes
- CAN1-APS1-AWS-In-Bytes
- APS2-APN2-AWS-In-Bytes
- CAN1-USW2-AWS-In-Bytes
- CAN1-EUN1-AWS-In-Bytes
- APS2-EUN1-AWS-In-Bytes
- APS2-EUW3-AWS-In-Bytes
- CAN1-EUC1-AWS-In-Bytes
- CAN1-EUW2-AWS-In-Bytes
- APS2-EUW2-AWS-In-Bytes
- APS2-USW2-AWS-In-Bytes
- APS2-CAN1-AWS-In-Bytes
- USW2-AWS-In-Bytes
- USE2-AWS-In-Bytes
- APN1-APS2-AWS-In-Bytes
- EUW2-USE2-AWS-In-Bytes
- APS3-USE2-AWS-In-Bytes
- EUC1-USE2-AWS-In-Bytes
- APS1-USE2-AWS-In-Bytes
- EUW3-USE1-AWS-In-Bytes
- USW1-USE2-AWS-In-Bytes
- EUW3-USE2-AWS-In-Bytes
- APS3-USE1-AWS-In-Bytes
- EUW3-EUS1-AWS-In-Bytes
- EUW3-EUC1-AWS-In-Bytes
- APS1-APS2-AWS-In-Bytes
- APE1-USE1-AWS-In-Bytes
- APN1-USE2-AWS-In-Bytes
- EUW3-EU-AWS-In-Bytes
- USW1-EU-AWS-In-Bytes
- EUW3-EUW2-AWS-In-Bytes
- EUC1-EUW3-AWS-In-Bytes
- APN1-APS1-AWS-In-Bytes
- EUW2-EUC1-AWS-In-Bytes
- USW1-EUC1-AWS-In-Bytes
- APS1-EUC1-AWS-In-Bytes
- EUN1-EU-AWS-In-Bytes
- APN2-APN1-AWS-In-Bytes
- EUC1-USW1-AWS-In-Bytes
- APE1-APS1-AWS-In-Bytes
- EUW2-MES1-AWS-In-Bytes
- APN2-APS1-AWS-In-Bytes
- USW1-EUW3-AWS-In-Bytes
- SAE1-USE2-AWS-In-Bytes
- APN2-USE1-AWS-In-Bytes
- USW1-APS3-AWS-In-Bytes
- EUN1-EUC1-AWS-In-Bytes
- AFS1-EU-AWS-In-Bytes
- EUN1-USE1-AWS-In-Bytes
- EUC1-EUS1-AWS-In-Bytes
- APS1-APE1-AWS-In-Bytes
- EUW3-USW2-AWS-In-Bytes
- AFS1-USE1-AWS-In-Bytes
- EUW3-MES1-AWS-In-Bytes
- APN3-APN1-AWS-In-Bytes
- EUS1-EUC1-AWS-In-Bytes
- EU-APS4-AWS-In-Bytes
- EU-EUC2-AWS-In-Bytes
- APN2-USW2-AWS-In-Bytes
- USW2-MES1-AWS-In-Bytes
- USW2-ILC1-AWS-In-Bytes
- USW2-EUS2-AWS-In-Bytes
- CAN1-UGW1-AWS-In-Bytes
- EUC1-APS1-AWS-In-Bytes
- EUC1-APN2-AWS-In-Bytes
- EUC1-APN3-AWS-In-Bytes
- EUC1-EUN1-AWS-In-Bytes
- EUC1-APE1-AWS-In-Bytes
- EUC1-MEC1-AWS-In-Bytes
- EUC1-APS2-AWS-In-Bytes
- EUC1-EUW2-AWS-In-Bytes
- EUC1-CAN1-AWS-In-Bytes
- EUC1-APS3-AWS-In-Bytes
- USE2-APS6-AWS-In-Bytes
- USE2-CAN2-AWS-In-Bytes
- USE2-EUS2-AWS-In-Bytes
- USE2-MES1-AWS-In-Bytes
- USE2-APS4-AWS-In-Bytes
- USE2-EUS1-AWS-In-Bytes
- USE2-AFS1-AWS-In-Bytes
- USE2-APE1-AWS-In-Bytes
- APE1-APN1-AWS-In-Bytes
- USW1-APE1-AWS-In-Bytes
- APN1-APE1-AWS-In-Bytes
- APS2-UGW1-AWS-In-Bytes
- APS2-APS6-AWS-In-Bytes
- USW2-AFS1-AWS-In-Bytes
- USW2-APE1-AWS-In-Bytes
- USW2-EUS1-AWS-In-Bytes
- USE2-MEC1-AWS-In-Bytes
- CAN1-EUC2-AWS-In-Bytes
- CAN1-SAE1-AWS-In-Bytes
- APS2-APN3-AWS-In-Bytes
- USW2-APS4-AWS-In-Bytes
- EUW2-USW2-AWS-In-Bytes
- AFS1-EUC1-AWS-In-Bytes
- SAE1-EUC1-AWS-In-Bytes
- APN1-EUC1-AWS-In-Bytes
- APS3-APS1-AWS-In-Bytes
- EU-APS6-AWS-In-Bytes
- USE2-APS5-AWS-In-Bytes
- USE2-ILC1-AWS-In-Bytes
- USE2-EUC2-AWS-In-Bytes
- APS2-MES1-AWS-In-Bytes
- APS1-EU-AWS-In-Bytes
- APS3-APS2-AWS-In-Bytes
- USW1-UGW1-AWS-In-Bytes
- APN1-EUN1-AWS-In-Bytes
- APN1-CAN1-AWS-In-Bytes
- APN1-APS3-AWS-In-Bytes
- APN1-EUW3-AWS-In-Bytes
- APN1-APN2-AWS-In-Bytes
- APN1-EUW2-AWS-In-Bytes
- APN1-EU-AWS-In-Bytes
- APN1-USW1-AWS-In-Bytes
- APN1-APN3-AWS-In-Bytes
- APS3-MEC1-AWS-In-Bytes
- USW2-UGW1-AWS-In-Bytes
- USE1-DEL1-AWS-In-Bytes
- USE1-LOS1-AWS-In-Bytes
- USE1-MCT1-AWS-In-Bytes
- USE1-APS7-AWS-In-Bytes
- USE1-PER1-AWS-In-Bytes
- USE1-CCU1-AWS-In-Bytes
- USE1-BKK1-AWS-In-Bytes
- USE1-MNL1-AWS-In-Bytes
- USE1-AKL1-AWS-In-Bytes
- USE1-TPE1-AWS-In-Bytes
- APS3-EUC1-AWS-In-Bytes
- APS3-USW2-AWS-In-Bytes
- APS1-USW2-AWS-In-Bytes
- APS2-APS4-AWS-In-Bytes
- EUW2-USW1-AWS-In-Bytes
- USW1-APN1-AWS-In-Bytes
- APN3-APS1-AWS-In-Bytes
- EUN1-APS1-AWS-In-Bytes
- EUN1-USW2-AWS-In-Bytes
- EUN1-APN1-AWS-In-Bytes
- EUC1-MES1-AWS-In-Bytes
- EUN1-USE2-AWS-In-Bytes
- EUC1-EUC2-AWS-In-Bytes
- APS1-APN1-AWS-In-Bytes
- APS3-MES1-AWS-In-Bytes
- EUW2-EUN1-AWS-In-Bytes
- EUW2-EUW3-AWS-In-Bytes
- USW2-EUC2-AWS-In-Bytes
- USW2-APS5-AWS-In-Bytes
- USW2-APS6-AWS-In-Bytes
- USW2-CAN2-AWS-In-Bytes
- APS3-APN1-AWS-In-Bytes
- USW1-APS1-AWS-In-Bytes
- APN3-EUW2-AWS-In-Bytes
- APS1-EUW2-AWS-In-Bytes
- USW1-APS2-AWS-In-Bytes
- APE1-USW2-AWS-In-Bytes
- SAE1-EU-AWS-In-Bytes
- APN2-APE1-AWS-In-Bytes
- APN3-USW2-AWS-In-Bytes
- APE1-APS2-AWS-In-Bytes
- EUW2-APS2-AWS-In-Bytes
- EUW3-USW1-AWS-In-Bytes
- AFS1-SAE1-AWS-In-Bytes
- UGW1-UGE1-AWS-In-Bytes
- APS3-EU-AWS-In-Bytes
- EUN1-CAN1-AWS-In-Bytes
- SAE1-USW1-AWS-In-Bytes
- EUW3-APN2-AWS-In-Bytes
- APS3-USW1-AWS-In-Bytes
- SAE1-CAN1-AWS-In-Bytes
- SAE1-APN1-AWS-In-Bytes
- APE1-USW1-AWS-In-Bytes
- APN2-EUC1-AWS-In-Bytes
- APE1-CAN1-AWS-In-Bytes
- SAE1-EUW2-AWS-In-Bytes
- EUW3-APS2-AWS-In-Bytes
- APE1-EUC1-AWS-In-Bytes
- APS1-CAN1-AWS-In-Bytes
- USW1-CAN1-AWS-In-Bytes
- APE1-APN2-AWS-In-Bytes
- EUN1-EUW2-AWS-In-Bytes
- APN3-EU-AWS-In-Bytes
- APN2-EUW3-AWS-In-Bytes
- APE1-EU-AWS-In-Bytes
- APN2-EU-AWS-In-Bytes
- APS1-EUW3-AWS-In-Bytes
- APN3-USE1-AWS-In-Bytes
- AFS1-APS1-AWS-In-Bytes
- APS3-EUW3-AWS-In-Bytes
- APS3-APN2-AWS-In-Bytes
- APS3-CAN1-AWS-In-Bytes
- EUN1-USW1-AWS-In-Bytes
- APN3-SAE1-AWS-In-Bytes
- EUW3-EUN1-AWS-In-Bytes
- AFS1-APS2-AWS-In-Bytes
- APN3-APN2-AWS-In-Bytes
- APN3-USE2-AWS-In-Bytes
- APE1-EUW2-AWS-In-Bytes
- EUW2-CAN1-AWS-In-Bytes
- EUN1-SAE1-AWS-In-Bytes
- APE1-EUW3-AWS-In-Bytes
- APN3-CAN1-AWS-In-Bytes
- APS1-USW1-AWS-In-Bytes
- USW1-EUW2-AWS-In-Bytes
- APS1-APN2-AWS-In-Bytes
- SAE1-APS2-AWS-In-Bytes
- APN2-USE2-AWS-In-Bytes
- EUC1-UGW1-AWS-In-Bytes
- APS1-APS4-AWS-In-Bytes
- EUC1-ILC1-AWS-In-Bytes
- EUW3-CAN1-AWS-In-Bytes
- EUN1-MES1-AWS-In-Bytes
- USW1-EUN1-AWS-In-Bytes
- APS1-APS3-AWS-In-Bytes
- CAN1-UGE1-AWS-In-Bytes
- EUC1-AFS1-AWS-In-Bytes
- AFS1-USW2-AWS-In-Bytes
- APS3-EUW2-AWS-In-Bytes
- CAN1-APN2-AWS-In-Bytes
- EUW3-APS1-AWS-In-Bytes
- APS1-MES1-AWS-In-Bytes
- AFS1-USE2-AWS-In-Bytes
- AFS1-USW1-AWS-In-Bytes
- APN2-APN3-AWS-In-Bytes
- EUN1-APS3-AWS-In-Bytes
- USW1-APN2-AWS-In-Bytes
- EUW2-AFS1-AWS-In-Bytes
- APE1-USE2-AWS-In-Bytes
- AFS1-EUW2-AWS-In-Bytes
- APN3-APE1-AWS-In-Bytes
- APS1-EUN1-AWS-In-Bytes
- EUW2-APS3-AWS-In-Bytes
- EUN1-EUW3-AWS-In-Bytes
- EUN1-AFS1-AWS-In-Bytes
- APN2-APS2-AWS-In-Bytes
- EUW2-APN1-AWS-In-Bytes
- AFS1-MES1-AWS-In-Bytes
- AFS1-APS3-AWS-In-Bytes
- APS2-AKL1-AWS-In-Bytes
- EUW3-APS3-AWS-In-Bytes
- USW2-UGE1-AWS-In-Bytes
- SAE1-APS1-AWS-In-Bytes
- APE1-APN3-AWS-In-Bytes
- EUN1-MEC1-AWS-In-Bytes
- APS3-APE1-AWS-In-Bytes
- USW1-MES1-AWS-In-Bytes
- USE1-CHI1-AWS-In-Bytes
- EUW3-EUC2-AWS-In-Bytes
- AFS1-EUW3-AWS-In-Bytes
- EUW2-APS1-AWS-In-Bytes
- UGE1-UGW1-AWS-In-Bytes
- APE1-EUN1-AWS-In-Bytes
- APS3-EUN1-AWS-In-Bytes
- APS2-APE1-AWS-In-Bytes
- APS2-MEC1-AWS-In-Bytes
- EUW3-EUS2-AWS-In-Bytes
- CAN2-USE1-AWS-In-Bytes
- APE1-AFS1-AWS-In-Bytes
- APE1-APS3-AWS-In-Bytes
- APE1-APS5-AWS-In-Bytes
- APE1-EUC2-AWS-In-Bytes
- APE1-APS6-AWS-In-Bytes
- APE1-APS7-AWS-In-Bytes
- SAE1-EUN1-AWS-In-Bytes
- APS1-APN3-AWS-In-Bytes
- EUW3-APN1-AWS-In-Bytes
- EUC1-APS5-AWS-In-Bytes
- USW2-PER1-AWS-In-Bytes
- AFS1-UGW1-AWS-In-Bytes
- EU-APS5-AWS-In-Bytes
- EUW2-EUS1-AWS-In-Bytes
- APS3-APS5-AWS-In-Bytes
- APN2-APS3-AWS-In-Bytes
- APN2-USW1-AWS-In-Bytes
- EUN1-APS2-AWS-In-Bytes
- SAE1-EUW3-AWS-In-Bytes
- APN3-USW1-AWS-In-Bytes
- EUW2-APN2-AWS-In-Bytes
- SAE1-APS3-AWS-In-Bytes
- EUN1-APN2-AWS-In-Bytes
- APN2-CAN1-AWS-In-Bytes
- AFS1-APN1-AWS-In-Bytes
- APN3-APS2-AWS-In-Bytes
- APN3-APS3-AWS-In-Bytes
- AFS1-CAN1-AWS-In-Bytes
- SAE1-APN2-AWS-In-Bytes
- APN3-EUC1-AWS-In-Bytes
- APE1-SAE1-AWS-In-Bytes
- APE1-CAN2-AWS-In-Bytes
- EUW3-MEC1-AWS-In-Bytes
- APS3-UGW1-AWS-In-Bytes
- USW1-APN3-AWS-In-Bytes
- USW1-CAN2-AWS-In-Bytes
- USW2-MEC1-AWS-In-Bytes
- USW1-AFS1-AWS-In-Bytes
- EUW3-APE1-AWS-In-Bytes
- EUW2-UGW1-AWS-In-Bytes
- EUW2-APS4-AWS-In-Bytes
- EUW2-EUS2-AWS-In-Bytes
- EUW2-ILC1-AWS-In-Bytes
- EUW2-EUC2-AWS-In-Bytes
- EUW2-MEC1-AWS-In-Bytes
- EUW2-APS5-AWS-In-Bytes
- EUW2-APE1-AWS-In-Bytes
- EUW2-APS6-AWS-In-Bytes
- EUW2-UGE1-AWS-In-Bytes
- EUW2-CAN2-AWS-In-Bytes
- EUW2-APN3-AWS-In-Bytes
- EUW2-AKL1-AWS-In-Bytes
- USE1-MIA1-AWS-In-Bytes
- USW2-APS7-AWS-In-Bytes
- EUW2-PER1-AWS-In-Bytes
- USE1-WAW1-AWS-In-Bytes
- USW2-WAW1-AWS-In-Bytes
- USW2-MIA1-AWS-In-Bytes
- USW1-MEC1-AWS-In-Bytes
- USW1-EUS1-AWS-In-Bytes
- MES1-EU-AWS-In-Bytes
- MES1-APS3-AWS-In-Bytes
- MES1-MEC1-AWS-In-Bytes
- APE1-EUS1-AWS-In-Bytes
- APN3-EUW3-AWS-In-Bytes
- APN2-EUN1-AWS-In-Bytes
- USW1-EUS2-AWS-In-Bytes
- USW1-UGE1-AWS-In-Bytes
- EUW3-AFS1-AWS-In-Bytes
- APN2-EUW2-AWS-In-Bytes
- MEC1-MES1-AWS-In-Bytes
- MEC1-APS3-AWS-In-Bytes
- AFS1-APN2-AWS-In-Bytes
- EUN1-UGW1-AWS-In-Bytes
- USE2-UGW1-AWS-In-Bytes
- APE1-ILC1-AWS-In-Bytes
- APE1-APS4-AWS-In-Bytes
- EUC1-UGE1-AWS-In-Bytes
- EUC1-EUS2-AWS-In-Bytes
- APS2-PER1-AWS-In-Bytes
- APE1-EUS2-AWS-In-Bytes
- APE1-MEC1-AWS-In-Bytes
- USW1-EUC2-AWS-In-Bytes
- EUW3-ILC1-AWS-In-Bytes
- EUW3-SAE1-AWS-In-Bytes
- APS1-APS7-AWS-In-Bytes
- APS2-AWS-In-Bytes
- EUC1-AWS-In-Bytes
- EUN1-AWS-In-Bytes
- AFS1-EUN1-AWS-In-Bytes
- USW1-APS4-AWS-In-Bytes
- CAN1-APN3-AWS-In-Bytes
- CAN1-CAN2-AWS-In-Bytes
- EUS2-EUW3-AWS-In-Bytes
- APN1-AWS-In-Bytes
- USE2-UGE1-AWS-In-Bytes
- APE1-MES1-AWS-In-Bytes
- APN1-EUS1-AWS-In-Bytes
- EUW2-AWS-In-Bytes
- APS6-USE1-AWS-In-Bytes
- USW1-AWS-In-Bytes
- EUC1-APS4-AWS-In-Bytes
- APN2-AFS1-AWS-In-Bytes
- APS3-APN3-AWS-In-Bytes
- SAE1-APE1-AWS-In-Bytes
- SAE1-APN3-AWS-In-Bytes
- SAE1-MES1-AWS-In-Bytes
- SAE1-AFS1-AWS-In-Bytes
- SAE1-EUS1-AWS-In-Bytes
- USW1-APS6-AWS-In-Bytes
- EUC1-APS6-AWS-In-Bytes
- APN2-EUS1-AWS-In-Bytes
- APS2-EUS1-AWS-In-Bytes
- APN1-MES1-AWS-In-Bytes
- APS1-UGW1-AWS-In-Bytes
- USW1-ILC1-AWS-In-Bytes
- USW1-TPE1-AWS-In-Bytes
- USW1-APS5-AWS-In-Bytes
- MEC1-EUC1-AWS-In-Bytes
- MEC1-USW2-AWS-In-Bytes
- MES1-EUC1-AWS-In-Bytes
- MES1-USW2-AWS-In-Bytes
- USW1-APS7-AWS-In-Bytes
- MEC1-USE1-AWS-In-Bytes
- EUW3-AWS-In-Bytes
- EU-CAN2-AWS-In-Bytes
- APN2-UGE1-AWS-In-Bytes
- USE1-QRO1-AWS-In-Bytes
- USW1-AKL1-AWS-In-Bytes
- EUC1-APS7-AWS-In-Bytes
- USE1-APS9-AWS-In-Bytes
- USE1-DFW1-AWS-In-Bytes
- EU-PER1-AWS-In-Bytes
- APS1-AWS-In-Bytes
- APS3-AFS1-AWS-In-Bytes
- APS2-AFS1-AWS-In-Bytes
- APS2-UGE1-AWS-In-Bytes
- CNN1-CNW1-AWS-In-Bytes
- EU-ILC1-AWS-In-Bytes
- USE1-DEN1-AWS-In-Bytes
- EUC1-PER1-AWS-In-Bytes
- APS3-EUS1-AWS-In-Bytes
- APN2-MES1-AWS-In-Bytes
- EUC1-WAW1-AWS-In-Bytes
- EUC1-MIA1-AWS-In-Bytes
- EU-APS7-AWS-In-Bytes
- USW1-PHX1-AWS-In-Bytes
- APS3-EUS2-AWS-In-Bytes
- USW1-LAS1-AWS-In-Bytes
- USW1-LAX1-AWS-In-Bytes
- USW1-MIA1-AWS-In-Bytes
- EUW2-ATL1-AWS-In-Bytes
- APN2-UGW1-AWS-In-Bytes
- USE1-LAX1-AWS-In-Bytes
- EUW2-APS7-AWS-In-Bytes
- AFS1-MEC1-AWS-In-Bytes
- EUS1-USW2-AWS-In-Bytes
- EUC1-CHI1-AWS-In-Bytes
- USE1-LIM1-AWS-In-Bytes
- EUN1-EUS1-AWS-In-Bytes
- APS4-USE1-AWS-In-Bytes
- EUW2-WAW1-AWS-In-Bytes
- APS1-EUS1-AWS-In-Bytes
- CAN1-AWS-In-Bytes
- APN2-MEC1-AWS-In-Bytes
- APS5-APS3-AWS-In-Bytes
- APS5-APS1-AWS-In-Bytes
- APN2-EUC2-AWS-In-Bytes
- APS1-APS5-AWS-In-Bytes
- EUC1-QRO1-AWS-In-Bytes
- AFS1-EUS1-AWS-In-Bytes
- USW1-WAW1-AWS-In-Bytes
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
- USE1-DataTransfer-xAZ-Out-Bytes
- EU-DataTransfer-xAZ-Out-Bytes
- USW2-DataTransfer-xAZ-Out-Bytes
- CAN1-DataTransfer-xAZ-Out-Bytes
- APN1-DataTransfer-xAZ-Out-Bytes
- USE2-DataTransfer-xAZ-Out-Bytes
- USW1-DataTransfer-xAZ-Out-Bytes
- EUC1-DataTransfer-xAZ-Out-Bytes
- APS1-DataTransfer-xAZ-Out-Bytes
- APS2-DataTransfer-xAZ-Out-Bytes
- EUW3-DataTransfer-xAZ-Out-Bytes
- EUW2-DataTransfer-xAZ-Out-Bytes
- APN2-DataTransfer-xAZ-Out-Bytes
- UGW1-DataTransfer-xAZ-Out-Bytes
- EUN1-DataTransfer-xAZ-Out-Bytes
- APS3-DataTransfer-xAZ-Out-Bytes
- SAE1-DataTransfer-xAZ-Out-Bytes
- UGE1-DataTransfer-xAZ-Out-Bytes
- CNN1-DataTransfer-xAZ-Out-Bytes
- AFS1-DataTransfer-xAZ-Out-Bytes
- APS4-DataTransfer-xAZ-Out-Bytes
CloudFront-Out-Bytes
The amount of data (per GB) transferred out of an AWS region to CloudFront.
Billing Codes
- EU-CloudFront-Out-Bytes
- USE1-CloudFront-Out-Bytes
- EUC1-CloudFront-Out-Bytes
- USE2-CloudFront-Out-Bytes
- USW2-CloudFront-Out-Bytes
- APS2-CloudFront-Out-Bytes
- APN1-CloudFront-Out-Bytes
- APS3-CloudFront-Out-Bytes
- EUW2-CloudFront-Out-Bytes
- SAE1-CloudFront-Out-Bytes
- APS1-CloudFront-Out-Bytes
- APN2-CloudFront-Out-Bytes
- USW1-CloudFront-Out-Bytes
- CAN1-CloudFront-Out-Bytes
- EUW3-CloudFront-Out-Bytes
- EUN1-CloudFront-Out-Bytes
- APE1-CloudFront-Out-Bytes
- APN3-CloudFront-Out-Bytes
- AFS1-CloudFront-Out-Bytes
- UGW1-CloudFront-Out-Bytes
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
- EU-CloudFront-In-Bytes
- USE1-CloudFront-In-Bytes
- EUC1-CloudFront-In-Bytes
- USW2-CloudFront-In-Bytes
- USE2-CloudFront-In-Bytes
- APN1-CloudFront-In-Bytes
- EUW2-CloudFront-In-Bytes
- SAE1-CloudFront-In-Bytes
- APS2-CloudFront-In-Bytes
- APS3-CloudFront-In-Bytes
- APS1-CloudFront-In-Bytes
- APN2-CloudFront-In-Bytes
- USW1-CloudFront-In-Bytes
- CAN1-CloudFront-In-Bytes
- EUW3-CloudFront-In-Bytes
- APE1-CloudFront-In-Bytes
- EUN1-CloudFront-In-Bytes
- APN3-CloudFront-In-Bytes
- UGW1-CloudFront-In-Bytes
- AFS1-CloudFront-In-Bytes
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
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
Serverless
Lambda-GB-Second
The duration (per GB-seconds) Lambda code on x86 architectures is executing. Billing starts from function invocation (including cold start time—handler and initialization code) to the time the Lambda code returns or ends. Costs are rounded to the nearest millisecond and vary by memory allocation. Pricing is tiered, the free tier includes 400,000 GB-seconds per month, then there are reduced rates after the first 7.5 billion GB-seconds per month, and the next 11.25 billion. For Compute Savings Plans, a negation amount will show as a negative number.
Billing Codes
- Lambda-GB-Second
- EU-Lambda-GB-Second
- APN1-Lambda-GB-Second
- USE2-Lambda-GB-Second
- EUC1-Lambda-GB-Second
- USW2-Lambda-GB-Second
- EUW2-Lambda-GB-Second
- Lambda-GB-Second
- USE2-Lambda-GB-Second
- CAN1-Lambda-GB-Second
- APS1-Lambda-GB-Second
- APS2-Lambda-GB-Second
- CAN1-Lambda-GB-Second
- EUC1-Lambda-GB-Second
- EUW2-Lambda-GB-Second
- EUW3-Lambda-GB-Second
- APS2-Lambda-GB-Second
- APN3-Lambda-GB-Second
- USW1-Lambda-GB-Second
- EUS1-Lambda-GB-Second
- APN2-Lambda-GB-Second
- APS3-Lambda-GB-Second
- APS1-Lambda-GB-Second
- EUW3-Lambda-GB-Second
- SAE1-Lambda-GB-Second
- UGW1-Lambda-GB-Second
- USW2-Lambda-GB-Second
- EU-Lambda-GB-Second
- APN2-Lambda-GB-Second
- UGW1-Lambda-GB-Second
- AFS1-Lambda-GB-Second
- APE1-Lambda-GB-Second
- EUN1-Lambda-GB-Second
- USW1-Lambda-GB-Second
- APN1-Lambda-GB-Second
- SAE1-Lambda-GB-Second
- APS3-Lambda-GB-Second
- EUN1-Lambda-GB-Second
- APE1-Lambda-GB-Second
- APN3-Lambda-GB-Second
- AFS1-Lambda-GB-Second
- UGE1-Lambda-GB-Second
- CAN2-Lambda-GB-Second
- MES1-Lambda-GB-Second
- MEC1-Lambda-GB-Second
- UGE1-Lambda-GB-Second
- EUS2-Lambda-GB-Second
- APS6-Lambda-GB-Second
- APS4-Lambda-GB-Second
- CAN2-Lambda-GB-Second
- MEC1-Lambda-GB-Second
- EUS1-Lambda-GB-Second
- CNN1-Lambda-GB-Second
- CNN1-Lambda-GB-Second
- APS5-Lambda-GB-Second
Request
The number of Lambda requests on x86 architectures. The free tier includes one million free requests per month.
Billing Codes
- Request
- EU-Request
- APN1-Request
- USE2-Request
- EUC1-Request
- USW2-Request
- EUW2-Request
- Request
- USE2-Request
- CAN1-Request
- APS1-Request
- APS2-Request
- CAN1-Request
- EUC1-Request
- EUW2-Request
- EUW3-Request
- APS2-Request
- APN3-Request
- USW1-Request
- EUS1-Request
- APN2-Request
- APS3-Request
- APS1-Request
- EUW3-Request
- SAE1-Request
- UGW1-Request
- USW2-Request
- AFS1-Request
- APE1-Request
- EUN1-Request
- USW1-Request
- EU-Request
- APN1-Request
- UGE1-Request
- UGE1-Request
- CAN2-Request
- SAE1-Request
- APS3-Request
- AFS1-Request
- APE1-Request
- APN2-Request
- APN3-Request
- EUN1-Request
- MES1-Request
- MEC1-Request
- MES1-Request
- UGW1-Request
- EUS2-Request
- APS6-Request
- APS4-Request
- CAN2-Request
- EUS1-Request
- CNN1-Request
- CNN1-Request
- APS5-Request
- MEC1-Request
Request-ARM
The number of Lambda requests on ARM architectures. The free tier includes one million free requests per month.
Billing Codes
- Request-ARM
- USW2-Request-ARM
- Request-ARM
- APN1-Request-ARM
- EU-Request-ARM
- EUC1-Request-ARM
- EUS1-Request-ARM
- USE2-Request-ARM
- USW1-Request-ARM
- EUW2-Request-ARM
- APS2-Request-ARM
- CAN1-Request-ARM
- APS3-Request-ARM
- USE2-Request-ARM
- APN2-Request-ARM
- EUW3-Request-ARM
- USW2-Request-ARM
- APN1-Request-ARM
- AFS1-Request-ARM
- APE1-Request-ARM
- APN3-Request-ARM
- APS1-Request-ARM
- EUN1-Request-ARM
- EU-Request-ARM
- USW1-Request-ARM
- SAE1-Request-ARM
- AFS1-Request-ARM
- APE1-Request-ARM
- APN2-Request-ARM
- APN3-Request-ARM
- APS3-Request-ARM
- APS1-Request-ARM
- APS2-Request-ARM
- EUC1-Request-ARM
- EUN1-Request-ARM
- EUW2-Request-ARM
- EUW3-Request-ARM
- SAE1-Request-ARM
- MES1-Request-ARM
- UGW1-Request-ARM
- CAN1-Request-ARM
- EUS1-Request-ARM
- MEC1-Request-ARM
- MES1-Request-ARM
- APS4-Request-ARM
Lambda-GB-Second-ARM
The duration (per GB-second) Lambda code on ARM architectures is executing. Billing starts from function invocation (including cold start time—handler and initialization code) to the time the Lambda code returns or ends. Costs are rounded to the nearest millisecond and vary by memory allocation. Pricing is tiered, the free tier includes 400,000 GB-seconds per month, then there are reduced rates after the first 7.5 billion GB-seconds per month, and the next 11.25 billion. For Compute Savings Plans, a negation amount will show as a negative number.
Billing Codes
- Lambda-GB-Second-ARM
- USW2-Lambda-GB-Second-ARM
- Lambda-GB-Second-ARM
- APN1-Lambda-GB-Second-ARM
- EU-Lambda-GB-Second-ARM
- EUC1-Lambda-GB-Second-ARM
- EUS1-Lambda-GB-Second-ARM
- USE2-Lambda-GB-Second-ARM
- USW1-Lambda-GB-Second-ARM
- EUW2-Lambda-GB-Second-ARM
- APS2-Lambda-GB-Second-ARM
- CAN1-Lambda-GB-Second-ARM
- EU-Lambda-GB-Second-ARM
- USW2-Lambda-GB-Second-ARM
- APS2-Lambda-GB-Second-ARM
- APN2-Lambda-GB-Second-ARM
- EUW2-Lambda-GB-Second-ARM
- USE2-Lambda-GB-Second-ARM
- APS3-Lambda-GB-Second-ARM
- CAN1-Lambda-GB-Second-ARM
- EUW3-Lambda-GB-Second-ARM
- APN1-Lambda-GB-Second-ARM
- AFS1-Lambda-GB-Second-ARM
- APE1-Lambda-GB-Second-ARM
- APN2-Lambda-GB-Second-ARM
- APN3-Lambda-GB-Second-ARM
- APS1-Lambda-GB-Second-ARM
- EUN1-Lambda-GB-Second-ARM
- SAE1-Lambda-GB-Second-ARM
- USW1-Lambda-GB-Second-ARM
- APE1-Lambda-GB-Second-ARM
- APS3-Lambda-GB-Second-ARM
- APS1-Lambda-GB-Second-ARM
- EUC1-Lambda-GB-Second-ARM
- EUN1-Lambda-GB-Second-ARM
- AFS1-Lambda-GB-Second-ARM
- APN3-Lambda-GB-Second-ARM
- EUW3-Lambda-GB-Second-ARM
- SAE1-Lambda-GB-Second-ARM
- MES1-Lambda-GB-Second-ARM
- EUS1-Lambda-GB-Second-ARM
- UGW1-Lambda-GB-Second-ARM
- MEC1-Lambda-GB-Second-ARM
- APS4-Lambda-GB-Second-ARM
Lambda-Storage-GB-Second-ARM
The amount of ephemeral storage allocated to Lambda functions on ARM architectures, calculated per GB-second of function execution duration. 512 MB of ephemeral storage is included at no additional cost.
Billing Codes
- EU-Lambda-Storage-GB-Second-ARM
- Lambda-Storage-GB-Second-ARM
- USW2-Lambda-Storage-GB-Second-ARM
- EUC1-Lambda-Storage-GB-Second-ARM
- USE2-Lambda-Storage-GB-Second-ARM
- APS3-Lambda-Storage-GB-Second-ARM
- APN1-Lambda-Storage-GB-Second-ARM
- APS2-Lambda-Storage-GB-Second-ARM
- APN2-Lambda-Storage-GB-Second-ARM
- EUW2-Lambda-Storage-GB-Second-ARM
- EUW3-Lambda-Storage-GB-Second-ARM
- CAN1-Lambda-Storage-GB-Second-ARM
- USW1-Lambda-Storage-GB-Second-ARM
- EUN1-Lambda-Storage-GB-Second-ARM
- SAE1-Lambda-Storage-GB-Second-ARM
Lambda-Storage-GB-Second
The amount of ephemeral storage allocated to Lambda functions on x86 architectures, calculated per GB-second of function execution duration. 512 MB of ephemeral storage is included at no additional cost.
Billing Codes
- EU-Lambda-Storage-GB-Second
- EUW2-Lambda-Storage-GB-Second
- Lambda-Storage-GB-Second
- USW2-Lambda-Storage-GB-Second
- EUC1-Lambda-Storage-GB-Second
- USE2-Lambda-Storage-GB-Second
- APN1-Lambda-Storage-GB-Second
- APN2-Lambda-Storage-GB-Second
- APS3-Lambda-Storage-GB-Second
- APS1-Lambda-Storage-GB-Second
- APS2-Lambda-Storage-GB-Second
- CAN1-Lambda-Storage-GB-Second
- EUW3-Lambda-Storage-GB-Second
- UGW1-Lambda-Storage-GB-Second
- SAE1-Lambda-Storage-GB-Second
- USW1-Lambda-Storage-GB-Second
- UGE1-Lambda-Storage-GB-Second
- EUN1-Lambda-Storage-GB-Second
- APN3-Lambda-Storage-GB-Second
- CNN1-Lambda-Storage-GB-Second
Lambda-Provisioned-Concurrency
The Provisioned Concurrency feature keeps Lambda functions initialized for better response times. Charges apply for the the duration (per GB-second) that concurrency is configured on x86 architectures, rounded up to the nearest 5 minutes.
Billing Codes
- Lambda-Provisioned-Concurrency
- USW2-Lambda-Provisioned-Concurrency
- EUW2-Lambda-Provisioned-Concurrency
- Lambda-Provisioned-Concurrency
- USW2-Lambda-Provisioned-Concurrency
- EU-Lambda-Provisioned-Concurrency
- EUW2-Lambda-Provisioned-Concurrency
- APN1-Lambda-Provisioned-Concurrency
- APN3-Lambda-Provisioned-Concurrency
- EUW3-Lambda-Provisioned-Concurrency
- USE2-Lambda-Provisioned-Concurrency
- APS2-Lambda-Provisioned-Concurrency
- USE2-Lambda-Provisioned-Concurrency
- EU-Lambda-Provisioned-Concurrency
- EUN1-Lambda-Provisioned-Concurrency
- EUC1-Lambda-Provisioned-Concurrency
- EUC1-Lambda-Provisioned-Concurrency
- AFS1-Lambda-Provisioned-Concurrency
- CAN1-Lambda-Provisioned-Concurrency
- MES1-Lambda-Provisioned-Concurrency
- APS2-Lambda-Provisioned-Concurrency
- APN1-Lambda-Provisioned-Concurrency
- APN3-Lambda-Provisioned-Concurrency
- EUW3-Lambda-Provisioned-Concurrency
- UGW1-Lambda-Provisioned-Concurrency
- APN2-Lambda-Provisioned-Concurrency
- CAN1-Lambda-Provisioned-Concurrency
- APS3-Lambda-Provisioned-Concurrency
- USW1-Lambda-Provisioned-Concurrency
- USW1-Lambda-Provisioned-Concurrency
- CNN1-Lambda-Provisioned-Concurrency
- CNW1-Lambda-Provisioned-Concurrency
- APN2-Lambda-Provisioned-Concurrency
- CNN1-Lambda-Provisioned-Concurrency
- EUN1-Lambda-Provisioned-Concurrency
- MES1-Lambda-Provisioned-Concurrency
Lambda-Provisioned-GB-Second
The Provisioned Concurrency feature keeps Lambda functions initialized for better response times. Charges apply for the duration (per GB-second) Lambda code with enabled Provisioned Concurrency on x86 architectures is executing. Billing starts from function invocation (including cold start time—handler and initialization code) to the time the Lambda code returns or ends. Costs are rounded to the nearest millisecond and vary by memory allocation.
Billing Codes
- USW2-Lambda-Provisioned-GB-Second
- Lambda-Provisioned-GB-Second
- USE2-Lambda-Provisioned-GB-Second
- EUW2-Lambda-Provisioned-GB-Second
- Lambda-Provisioned-GB-Second
- USW2-Lambda-Provisioned-GB-Second
- EU-Lambda-Provisioned-GB-Second
- USE2-Lambda-Provisioned-GB-Second
- EUW2-Lambda-Provisioned-GB-Second
- APS2-Lambda-Provisioned-GB-Second
- EU-Lambda-Provisioned-GB-Second
- EUN1-Lambda-Provisioned-GB-Second
- APN1-Lambda-Provisioned-GB-Second
- EUC1-Lambda-Provisioned-GB-Second
- EUC1-Lambda-Provisioned-GB-Second
- AFS1-Lambda-Provisioned-GB-Second
- CAN1-Lambda-Provisioned-GB-Second
- EUW3-Lambda-Provisioned-GB-Second
- MES1-Lambda-Provisioned-GB-Second
- APS2-Lambda-Provisioned-GB-Second
- UGW1-Lambda-Provisioned-GB-Second
- APN2-Lambda-Provisioned-GB-Second
- CAN1-Lambda-Provisioned-GB-Second
- APS3-Lambda-Provisioned-GB-Second
- USW1-Lambda-Provisioned-GB-Second
- USW1-Lambda-Provisioned-GB-Second
- CNN1-Lambda-Provisioned-GB-Second
- CNW1-Lambda-Provisioned-GB-Second
- APN2-Lambda-Provisioned-GB-Second
- EUN1-Lambda-Provisioned-GB-Second
- CNN1-Lambda-Provisioned-GB-Second
- EUW3-Lambda-Provisioned-GB-Second
- MES1-Lambda-Provisioned-GB-Second
Lambda-Provisioned-GB-Second-ARM
The Provisioned Concurrency feature keeps Lambda functions initialized for better response times. Charges apply for the duration (per GB-second) Lambda code with enabled Provisioned Concurrency on ARM architectures is executing. Billing starts from function invocation (including cold start time—handler and initialization code) to the time the Lambda code returns or ends. Costs are rounded to the nearest millisecond and vary by memory allocation.
Billing Codes
- EUC1-Lambda-Provisioned-GB-Second-ARM
- APN1-Lambda-Provisioned-GB-Second-ARM
- USW2-Lambda-Provisioned-GB-Second-ARM
- Lambda-Provisioned-GB-Second-ARM
- Lambda-Provisioned-GB-Second-ARM
- USW2-Lambda-Provisioned-GB-Second-ARM
- EU-Lambda-Provisioned-GB-Second-ARM
- APS2-Lambda-Provisioned-GB-Second-ARM
- APN2-Lambda-Provisioned-GB-Second-ARM
- EUW2-Lambda-Provisioned-GB-Second-ARM
- USE2-Lambda-Provisioned-GB-Second-ARM
- CAN1-Lambda-Provisioned-GB-Second-ARM
- EUW3-Lambda-Provisioned-GB-Second-ARM
- APN1-Lambda-Provisioned-GB-Second-ARM
- USW1-Lambda-Provisioned-GB-Second-ARM
- SAE1-Lambda-Provisioned-GB-Second-ARM
- APS2-Lambda-Provisioned-GB-Second-ARM
- CAN1-Lambda-Provisioned-GB-Second-ARM
- USW1-Lambda-Provisioned-GB-Second-ARM
- EU-Lambda-Provisioned-GB-Second-ARM
- USE2-Lambda-Provisioned-GB-Second-ARM
- EUC1-Lambda-Provisioned-GB-Second-ARM
Lambda-Provisioned-Concurrency-ARM
The Provisioned Concurrency feature keeps Lambda functions initialized for better response times. Charges apply for the the duration (per GB-second) that concurrency is configured on ARM architectures, rounded up to the nearest 5 minutes.
Billing Codes
- EUC1-Lambda-Provisioned-Concurrency-ARM
- USW2-Lambda-Provisioned-Concurrency-ARM
- APN1-Lambda-Provisioned-Concurrency-ARM
- Lambda-Provisioned-Concurrency-ARM
- Lambda-Provisioned-Concurrency-ARM
- USW2-Lambda-Provisioned-Concurrency-ARM
- EU-Lambda-Provisioned-Concurrency-ARM
- APS2-Lambda-Provisioned-Concurrency-ARM
- APN2-Lambda-Provisioned-Concurrency-ARM
- EUW2-Lambda-Provisioned-Concurrency-ARM
- USE2-Lambda-Provisioned-Concurrency-ARM
- CAN1-Lambda-Provisioned-Concurrency-ARM
- EUW3-Lambda-Provisioned-Concurrency-ARM
- APN1-Lambda-Provisioned-Concurrency-ARM
- USW1-Lambda-Provisioned-Concurrency-ARM
- SAE1-Lambda-Provisioned-Concurrency-ARM
- APS2-Lambda-Provisioned-Concurrency-ARM
- CAN1-Lambda-Provisioned-Concurrency-ARM
- USW1-Lambda-Provisioned-Concurrency-ARM
- EU-Lambda-Provisioned-Concurrency-ARM
- USE2-Lambda-Provisioned-Concurrency-ARM
- EUW3-Lambda-Provisioned-Concurrency-ARM
- EUC1-Lambda-Provisioned-Concurrency-ARM
Lambda-Streaming-Response-Processed-Bytes-ARM
The Lambda HTTP Response Stream feature returns an HTTP response stream to improve Time to First Byte performance. Charges apply per GB of processed response bytes on ARM architectures, with the first 6 MB per request included at no additional cost.
Billing Codes
Lambda-Streaming-Response-Processed-Bytes
The Lambda HTTP Response Stream feature returns an HTTP response stream to improve Time to First Byte performance. Charges apply per GB of processed response bytes on x86 architectures, with the first 6 MB per request included at no additional cost.
Billing Codes
Lambda-SnapStart-Cached-GB-S
The Lambda SnapStart feature reduces cold start latency by caching a snapshot of the function state. Charges apply per GB-second for caching the snapshot while the function version is active, with a minimum billing duration of 3 hours.
Lambda-SnapStart-Restored-GB
The Lambda SnapStart feature reduces cold start latency by caching a snapshot of the function state. Charges apply per GB restored, based on the memory allocated to the Lambda function.
Billing Codes
DT-Data Transfer
DataTransfer-AZ-Out-Bytes
The amount of data (per GB) transferred out to the same Availability Zone. Data transferred within the same Availability Zone does not incur a fee.
Billing Codes
DataTransfer-AZ-In-Bytes
The amount of data (per GB) transferred in from the same Availability Zone. Data transferred within the same Availability Zone does not incur a fee.