AmazonECS
Each grouping represents a specific way Amazon Elastic Container Service (Amazon ECS) 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
- EUC1-DataTransfer-Regional-Bytes
- EU-DataTransfer-Regional-Bytes
- USW2-DataTransfer-Regional-Bytes
- EUW3-DataTransfer-Regional-Bytes
- APS2-DataTransfer-Regional-Bytes
- EUW2-DataTransfer-Regional-Bytes
- USE2-DataTransfer-Regional-Bytes
- UGE1-DataTransfer-Regional-Bytes
- CAN1-DataTransfer-Regional-Bytes
- APS1-DataTransfer-Regional-Bytes
- APN1-DataTransfer-Regional-Bytes
- USW1-DataTransfer-Regional-Bytes
- SAE1-DataTransfer-Regional-Bytes
- EUS1-DataTransfer-Regional-Bytes
- APN2-DataTransfer-Regional-Bytes
- UGW1-DataTransfer-Regional-Bytes
- APS3-DataTransfer-Regional-Bytes
- EUN1-DataTransfer-Regional-Bytes
- AFS1-DataTransfer-Regional-Bytes
- APE1-DataTransfer-Regional-Bytes
- APN3-DataTransfer-Regional-Bytes
- MEC1-DataTransfer-Regional-Bytes
- EUS2-DataTransfer-Regional-Bytes
- APS4-DataTransfer-Regional-Bytes
- CNN1-DataTransfer-Regional-Bytes
- APS6-DataTransfer-Regional-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
- EUC1-APS1-AWS-Out-Bytes
- EUC1-APN1-AWS-Out-Bytes
- EUC1-APS2-AWS-Out-Bytes
- EUC1-EU-AWS-Out-Bytes
- EUC1-APN2-AWS-Out-Bytes
- EUC1-USW2-AWS-Out-Bytes
- EUC1-USE2-AWS-Out-Bytes
- EUC1-EUW2-AWS-Out-Bytes
- EUC1-USE1-AWS-Out-Bytes
- EUC1-EUN1-AWS-Out-Bytes
- EUC1-APS3-AWS-Out-Bytes
- EUC1-CAN1-AWS-Out-Bytes
- USE1-APS1-AWS-Out-Bytes
- USE1-APS2-AWS-Out-Bytes
- USE1-EUW2-AWS-Out-Bytes
- USE1-SAE1-AWS-Out-Bytes
- USE1-EUN1-AWS-Out-Bytes
- USE1-EUC1-AWS-Out-Bytes
- USE1-USE2-AWS-Out-Bytes
- USE1-USW2-AWS-Out-Bytes
- USE1-APS3-AWS-Out-Bytes
- USE1-EU-AWS-Out-Bytes
- USE1-APN1-AWS-Out-Bytes
- USE1-USW1-AWS-Out-Bytes
- EUW3-AWS-Out-Bytes
- USE1-AWS-Out-Bytes
- USE1-EUW3-AWS-Out-Bytes
- USE1-APN2-AWS-Out-Bytes
- EU-AWS-Out-Bytes
- USE2-USE1-AWS-Out-Bytes
- USW2-USE1-AWS-Out-Bytes
- USW2-USE2-AWS-Out-Bytes
- USW2-APS3-AWS-Out-Bytes
- USW2-APS1-AWS-Out-Bytes
- USW2-APS4-AWS-Out-Bytes
- USW2-EU-AWS-Out-Bytes
- USW2-EUW2-AWS-Out-Bytes
- USW2-APN1-AWS-Out-Bytes
- USW2-EUW3-AWS-Out-Bytes
- USW2-CAN1-AWS-Out-Bytes
- USW2-EUC1-AWS-Out-Bytes
- USW2-APS2-AWS-Out-Bytes
- USW1-USE1-AWS-Out-Bytes
- APS1-USW2-AWS-Out-Bytes
- SAE1-USE2-AWS-Out-Bytes
- SAE1-USE1-AWS-Out-Bytes
- SAE1-APS1-AWS-Out-Bytes
- USE1-CAN2-AWS-Out-Bytes
- SAE1-USW1-AWS-Out-Bytes
- SAE1-USW2-AWS-Out-Bytes
- SAE1-AWS-Out-Bytes
- APS2-USW2-AWS-Out-Bytes
- EU-USE1-AWS-Out-Bytes
- EU-EUW2-AWS-Out-Bytes
- EU-APS1-AWS-Out-Bytes
- EU-EUC1-AWS-Out-Bytes
- EU-USE2-AWS-Out-Bytes
- APS2-EUW2-AWS-Out-Bytes
- APS2-APS1-AWS-Out-Bytes
- APS2-USE2-AWS-Out-Bytes
- APS2-EU-AWS-Out-Bytes
- APS2-EUN1-AWS-Out-Bytes
- APS2-USE1-AWS-Out-Bytes
- APS2-APS3-AWS-Out-Bytes
- APS2-EUC1-AWS-Out-Bytes
- APS2-SAE1-AWS-Out-Bytes
- APS2-APN2-AWS-Out-Bytes
- APS2-CAN1-AWS-Out-Bytes
- USW2-AWS-Out-Bytes
- USW2-USW1-AWS-Out-Bytes
- USW2-APN2-AWS-Out-Bytes
- USW2-SAE1-AWS-Out-Bytes
- APS2-APN1-AWS-Out-Bytes
- APS2-EUW3-AWS-Out-Bytes
- USE1-APE1-AWS-Out-Bytes
- APS2-USW1-AWS-Out-Bytes
- APS2-WAW1-AWS-Out-Bytes
- USW2-EUN1-AWS-Out-Bytes
- APS2-APS4-AWS-Out-Bytes
- CAN1-USE1-AWS-Out-Bytes
- CAN1-EU-AWS-Out-Bytes
- EU-USW2-AWS-Out-Bytes
- EUW2-USE1-AWS-Out-Bytes
- USW1-USW2-AWS-Out-Bytes
- EUW2-USW2-AWS-Out-Bytes
- APS1-USE1-AWS-Out-Bytes
- EUN1-USW2-AWS-Out-Bytes
- EUN1-USE1-AWS-Out-Bytes
- USE2-EUC1-AWS-Out-Bytes
- USE2-APN2-AWS-Out-Bytes
- USE2-TPE1-AWS-Out-Bytes
- USE2-EUW2-AWS-Out-Bytes
- USE2-APS1-AWS-Out-Bytes
- CAN1-EUC1-AWS-Out-Bytes
- CAN1-APS3-AWS-Out-Bytes
- CAN1-EUN1-AWS-Out-Bytes
- CAN1-EUW2-AWS-Out-Bytes
- CAN1-USE2-AWS-Out-Bytes
- CAN1-APN1-AWS-Out-Bytes
- CAN1-APS2-AWS-Out-Bytes
- CAN1-USW2-AWS-Out-Bytes
- CAN1-APS1-AWS-Out-Bytes
- USE2-USW1-AWS-Out-Bytes
- USE2-USW2-AWS-Out-Bytes
- USE2-APS2-AWS-Out-Bytes
- USE2-APS3-AWS-Out-Bytes
- CAN1-TPE1-AWS-Out-Bytes
- CAN1-EUW3-AWS-Out-Bytes
- CAN1-SAE1-AWS-Out-Bytes
- CAN1-USW1-AWS-Out-Bytes
- CAN1-APN2-AWS-Out-Bytes
- CAN1-AKL1-AWS-Out-Bytes
- USE2-MEC1-AWS-Out-Bytes
- SAE1-EUW2-AWS-Out-Bytes
- USE1-CAN1-AWS-Out-Bytes
- USE2-EUN1-AWS-Out-Bytes
- USE2-SAE1-AWS-Out-Bytes
- USE1-MES1-AWS-Out-Bytes
- USE2-CAN1-AWS-Out-Bytes
- EUS1-USE1-AWS-Out-Bytes
- EUS1-USW2-AWS-Out-Bytes
- EUS1-USE2-AWS-Out-Bytes
- EUS1-APS2-AWS-Out-Bytes
- EUS1-APS1-AWS-Out-Bytes
- EUS1-EUW2-AWS-Out-Bytes
- EUS1-EU-AWS-Out-Bytes
- EUS1-EUC1-AWS-Out-Bytes
- EUS1-USW1-AWS-Out-Bytes
- EUS1-APS3-AWS-Out-Bytes
- EUS1-EUN1-AWS-Out-Bytes
- USE1-APS7-AWS-Out-Bytes
- USE1-APS5-AWS-Out-Bytes
- CAN1-APS6-AWS-Out-Bytes
- CAN1-ILC1-AWS-Out-Bytes
- USE2-APN3-AWS-Out-Bytes
- USE2-EUW3-AWS-Out-Bytes
- USE2-EU-AWS-Out-Bytes
- USE2-APN1-AWS-Out-Bytes
- EU-APS2-AWS-Out-Bytes
- EU-EUW3-AWS-Out-Bytes
- USE1-MEC1-AWS-Out-Bytes
- EU-APN1-AWS-Out-Bytes
- EU-EUN1-AWS-Out-Bytes
- USW2-APS6-AWS-Out-Bytes
- USW2-ILC1-AWS-Out-Bytes
- USW2-MEC1-AWS-Out-Bytes
- USW2-AKL1-AWS-Out-Bytes
- APS2-APS6-AWS-Out-Bytes
- EUS1-CAN1-AWS-Out-Bytes
- USE1-ILC1-AWS-Out-Bytes
- EUS1-APN1-AWS-Out-Bytes
- EUS1-EUW3-AWS-Out-Bytes
- EUS1-SAE1-AWS-Out-Bytes
- EUS1-ILC1-AWS-Out-Bytes
- EUS1-APE1-AWS-Out-Bytes
- EUS1-AKL1-AWS-Out-Bytes
- EUS1-APN2-AWS-Out-Bytes
- APS2-APS5-AWS-Out-Bytes
- USE1-WAW1-AWS-Out-Bytes
- APS2-NYC1-AWS-Out-Bytes
- APS2-DFW1-AWS-Out-Bytes
- APS2-LAX1-AWS-Out-Bytes
- USE1-MCT1-AWS-Out-Bytes
- USE1-CCU1-AWS-Out-Bytes
- USE1-BKK1-AWS-Out-Bytes
- USE1-PDX1-AWS-Out-Bytes
- USE1-SEA1-AWS-Out-Bytes
- USE1-PHX1-AWS-Out-Bytes
- USE1-LAX1-AWS-Out-Bytes
- USE1-AFS1-AWS-Out-Bytes
- USE1-APS4-AWS-Out-Bytes
- USE1-DEL1-AWS-Out-Bytes
- USE1-LAS1-AWS-Out-Bytes
- USE1-LOS1-AWS-Out-Bytes
- USE1-DEN1-AWS-Out-Bytes
- APS2-SCL1-AWS-Out-Bytes
- EU-USW1-AWS-Out-Bytes
- EU-APN2-AWS-Out-Bytes
- USE1-EUS1-AWS-Out-Bytes
- USE1-APN3-AWS-Out-Bytes
- USW1-USE2-AWS-Out-Bytes
- USW1-EUW2-AWS-Out-Bytes
- USW1-EUC1-AWS-Out-Bytes
- USW1-APS1-AWS-Out-Bytes
- USW1-EU-AWS-Out-Bytes
- USE1-EUC2-AWS-Out-Bytes
- USE1-TPE1-AWS-Out-Bytes
- USE1-HAM1-AWS-Out-Bytes
- USE1-MNL1-AWS-Out-Bytes
- USW1-APS4-AWS-Out-Bytes
- USE1-UGW1-AWS-Out-Bytes
- APS2-MEC1-AWS-Out-Bytes
- EUN1-EU-AWS-Out-Bytes
- AFS1-APS1-AWS-Out-Bytes
- APN1-USE1-AWS-Out-Bytes
- APN1-APS1-AWS-Out-Bytes
- APS3-USE1-AWS-Out-Bytes
- EUW3-USE1-AWS-Out-Bytes
- APS3-APS1-AWS-Out-Bytes
- USW1-APS2-AWS-Out-Bytes
- USW1-APS3-AWS-Out-Bytes
- USW1-EUW3-AWS-Out-Bytes
- USW1-SAE1-AWS-Out-Bytes
- USW1-APN1-AWS-Out-Bytes
- USW1-APN2-AWS-Out-Bytes
- USW1-APE1-AWS-Out-Bytes
- USW1-EUN1-AWS-Out-Bytes
- USW1-CAN1-AWS-Out-Bytes
- USW1-AFS1-AWS-Out-Bytes
- AFS1-USE1-AWS-Out-Bytes
- APN3-USE1-AWS-Out-Bytes
- USW1-APN3-AWS-Out-Bytes
- EUW2-EU-AWS-Out-Bytes
- USW1-EUS1-AWS-Out-Bytes
- USW1-LIM1-AWS-Out-Bytes
- USW1-ILC1-AWS-Out-Bytes
- EUN1-EUC1-AWS-Out-Bytes
- EUC1-USW1-AWS-Out-Bytes
- APN1-EUW2-AWS-Out-Bytes
- APN1-USW2-AWS-Out-Bytes
- EUC1-MEC1-AWS-Out-Bytes
- APS2-AWS-Out-Bytes
- APN1-USE2-AWS-Out-Bytes
- EU-CAN1-AWS-Out-Bytes
- APN1-EUC1-AWS-Out-Bytes
- EUN1-USW1-AWS-Out-Bytes
- APN1-EU-AWS-Out-Bytes
- EUC1-EUW3-AWS-Out-Bytes
- EUC1-APE1-AWS-Out-Bytes
- USE1-APS6-AWS-Out-Bytes
- EUN1-USE2-AWS-Out-Bytes
- EUC1-SCL1-AWS-Out-Bytes
- APS1-EUC1-AWS-Out-Bytes
- APS1-EUW3-AWS-Out-Bytes
- USW1-MEC1-AWS-Out-Bytes
- EUC1-SAE1-AWS-Out-Bytes
- APS2-APE1-AWS-Out-Bytes
- APS2-CCU1-AWS-Out-Bytes
- APS2-MIA1-AWS-Out-Bytes
- EUN1-SAE1-AWS-Out-Bytes
- USE1-AKL1-AWS-Out-Bytes
- APS1-USE2-AWS-Out-Bytes
- EUC1-TPE1-AWS-Out-Bytes
- USW2-AFS1-AWS-Out-Bytes
- USW2-MES1-AWS-Out-Bytes
- EUC1-APN3-AWS-Out-Bytes
- EUN1-APS1-AWS-Out-Bytes
- EU-APS3-AWS-Out-Bytes
- EUN1-APS3-AWS-Out-Bytes
- USW1-UGW1-AWS-Out-Bytes
- USW1-MES1-AWS-Out-Bytes
- USW1-EUC2-AWS-Out-Bytes
- APN1-USW1-AWS-Out-Bytes
- APE1-USE1-AWS-Out-Bytes
- USW1-EUS2-AWS-Out-Bytes
- EU-MSP1-AWS-Out-Bytes
- EU-ILC1-AWS-Out-Bytes
- EU-SAE1-AWS-Out-Bytes
- USW1-UGE1-AWS-Out-Bytes
- USW1-APS5-AWS-Out-Bytes
- EU-APE1-AWS-Out-Bytes
- EU-MEC1-AWS-Out-Bytes
- EU-APS5-AWS-Out-Bytes
- EU-TPE1-AWS-Out-Bytes
- EU-MIA1-AWS-Out-Bytes
- USE2-UGW1-AWS-Out-Bytes
- CAN1-APN3-AWS-Out-Bytes
- EUC1-LAS1-AWS-Out-Bytes
- EUC1-APS4-AWS-Out-Bytes
- EUC1-ILC1-AWS-Out-Bytes
- EUC1-APS6-AWS-Out-Bytes
- EUW2-EUN1-AWS-Out-Bytes
- EUW2-EUC1-AWS-Out-Bytes
- EUW2-APS3-AWS-Out-Bytes
- EUW2-USE2-AWS-Out-Bytes
- EUW2-APS2-AWS-Out-Bytes
- EUW2-APS1-AWS-Out-Bytes
- EUW2-APN2-AWS-Out-Bytes
- EUW2-CAN1-AWS-Out-Bytes
- EUW2-APN1-AWS-Out-Bytes
- EUW2-EUW3-AWS-Out-Bytes
- EUW2-SAE1-AWS-Out-Bytes
- EUW2-USW1-AWS-Out-Bytes
- USE2-EUS1-AWS-Out-Bytes
- USE2-APE1-AWS-Out-Bytes
- USE2-AFS1-AWS-Out-Bytes
- USE2-MES1-AWS-Out-Bytes
- EUW2-MIA1-AWS-Out-Bytes
- APN2-USE1-AWS-Out-Bytes
- USE2-APS4-AWS-Out-Bytes
- APN1-EUW3-AWS-Out-Bytes
- USW1-PER1-AWS-Out-Bytes
- EUC1-LOS1-AWS-Out-Bytes
- EUC1-PHX1-AWS-Out-Bytes
- USW1-QRO1-AWS-Out-Bytes
- USW1-TPE1-AWS-Out-Bytes
- EU-APN3-AWS-Out-Bytes
- EUW2-AWS-Out-Bytes
- EUC1-AWS-Out-Bytes
- CAN1-AWS-Out-Bytes
- APS1-AWS-Out-Bytes
- USW1-APS6-AWS-Out-Bytes
- EUN1-APS2-AWS-Out-Bytes
- EUN1-EUW3-AWS-Out-Bytes
- EUN1-EUW2-AWS-Out-Bytes
- USE1-PER1-AWS-Out-Bytes
- USW2-APE1-AWS-Out-Bytes
- USW2-APS5-AWS-Out-Bytes
- USW2-MNL1-AWS-Out-Bytes
- USW2-WAW1-AWS-Out-Bytes
- EUS1-MEC1-AWS-Out-Bytes
- EUS1-WAW1-AWS-Out-Bytes
- EUS1-MIA1-AWS-Out-Bytes
- EUS1-TPE1-AWS-Out-Bytes
- EUC1-UGW1-AWS-Out-Bytes
- APN1-APS2-AWS-Out-Bytes
- APN2-APS3-AWS-Out-Bytes
- APS1-APS3-AWS-Out-Bytes
- EU-WAW1-AWS-Out-Bytes
- USW2-APN3-AWS-Out-Bytes
- APS3-USW2-AWS-Out-Bytes
- APS3-USW1-AWS-Out-Bytes
- MEC1-EUC1-AWS-Out-Bytes
- MEC1-APS3-AWS-Out-Bytes
- APS3-EUW2-AWS-Out-Bytes
- APS3-APE1-AWS-Out-Bytes
- APS3-EU-AWS-Out-Bytes
- APS3-APS5-AWS-Out-Bytes
- APS3-EUN1-AWS-Out-Bytes
- APS3-USE2-AWS-Out-Bytes
- APS3-EUW3-AWS-Out-Bytes
- MEC1-EU-AWS-Out-Bytes
- APS3-EUC1-AWS-Out-Bytes
- APS3-APN2-AWS-Out-Bytes
- APS3-APN1-AWS-Out-Bytes
- APS3-CAN1-AWS-Out-Bytes
- APS3-APS2-AWS-Out-Bytes
- APS3-MEC1-AWS-Out-Bytes
- APS3-WAW1-AWS-Out-Bytes
- APS3-TPE1-AWS-Out-Bytes
- APS3-SAE1-AWS-Out-Bytes
- USE1-EUS2-AWS-Out-Bytes
- EUW3-EUW2-AWS-Out-Bytes
- EUW3-EUC1-AWS-Out-Bytes
- EUW3-EU-AWS-Out-Bytes
- EUW3-USW2-AWS-Out-Bytes
- EUW3-USW1-AWS-Out-Bytes
- EUW3-DEN1-AWS-Out-Bytes
- EUW3-APS3-AWS-Out-Bytes
- EUW3-USE2-AWS-Out-Bytes
- EUW3-EUN1-AWS-Out-Bytes
- EUW3-APN1-AWS-Out-Bytes
- EUW3-QRO1-AWS-Out-Bytes
- EUW3-APS1-AWS-Out-Bytes
- EUW3-LAX1-AWS-Out-Bytes
- EUW3-MEC1-AWS-Out-Bytes
- EUW3-CCU1-AWS-Out-Bytes
- EUW3-LAS1-AWS-Out-Bytes
- EUW3-DFW1-AWS-Out-Bytes
- EUW3-LOS1-AWS-Out-Bytes
- EUW3-IAH1-AWS-Out-Bytes
- EUW3-MCT1-AWS-Out-Bytes
- EUW3-SEA1-AWS-Out-Bytes
- EUW3-MIA1-AWS-Out-Bytes
- EUW3-DEL1-AWS-Out-Bytes
- EUW3-AKL1-AWS-Out-Bytes
- EUW3-PHX1-AWS-Out-Bytes
- EUW3-LIM1-AWS-Out-Bytes
- EUW3-BKK1-AWS-Out-Bytes
- EUW3-MES1-AWS-Out-Bytes
- EUW3-APS2-AWS-Out-Bytes
- EUW3-SCL1-AWS-Out-Bytes
- EUW3-PDX1-AWS-Out-Bytes
- EUW3-SAE1-AWS-Out-Bytes
- EUW3-APN2-AWS-Out-Bytes
- EUW3-MSP1-AWS-Out-Bytes
- EUW3-HAM1-AWS-Out-Bytes
- EUW3-TPE1-AWS-Out-Bytes
- EUW3-EUS1-AWS-Out-Bytes
- EUW3-CAN1-AWS-Out-Bytes
- EUW3-APE1-AWS-Out-Bytes
- EUW3-PHL1-AWS-Out-Bytes
- EUW3-BOS1-AWS-Out-Bytes
- EUW3-MCI2-AWS-Out-Bytes
- EUW3-WAW1-AWS-Out-Bytes
- EUW3-NYC1-AWS-Out-Bytes
- EUW3-APN3-AWS-Out-Bytes
- EUW3-ATL1-AWS-Out-Bytes
- EUW3-MNL1-AWS-Out-Bytes
- EUW3-CHI1-AWS-Out-Bytes
- EUC1-PHL1-AWS-Out-Bytes
- EUC1-EUS1-AWS-Out-Bytes
- USE2-EUC2-AWS-Out-Bytes
- USE2-UGE1-AWS-Out-Bytes
- EU-APS4-AWS-Out-Bytes
- EU-AFS1-AWS-Out-Bytes
- APN1-AWS-Out-Bytes
- USE1-UGE1-AWS-Out-Bytes
- EUC1-NYC1-AWS-Out-Bytes
- APS1-EU-AWS-Out-Bytes
- APS1-SAE1-AWS-Out-Bytes
- APS1-USW1-AWS-Out-Bytes
- APS1-EUW2-AWS-Out-Bytes
- APS1-APS2-AWS-Out-Bytes
- APS1-TPE1-AWS-Out-Bytes
- APS1-APN1-AWS-Out-Bytes
- USW1-AWS-Out-Bytes
- EUC1-MES1-AWS-Out-Bytes
- EUW2-WAW1-AWS-Out-Bytes
- APS1-EUN1-AWS-Out-Bytes
- APS1-APN2-AWS-Out-Bytes
- APS1-CAN1-AWS-Out-Bytes
- APS1-ILC1-AWS-Out-Bytes
- SAE1-APE1-AWS-Out-Bytes
- SAE1-EUW3-AWS-Out-Bytes
- SAE1-CAN1-AWS-Out-Bytes
- SAE1-EUC1-AWS-Out-Bytes
- SAE1-APN2-AWS-Out-Bytes
- SAE1-APS3-AWS-Out-Bytes
- SAE1-EU-AWS-Out-Bytes
- SAE1-EUN1-AWS-Out-Bytes
- SAE1-APN1-AWS-Out-Bytes
- SAE1-APS2-AWS-Out-Bytes
- SAE1-MEC1-AWS-Out-Bytes
- SAE1-APS5-AWS-Out-Bytes
- SAE1-WAW1-AWS-Out-Bytes
- APS3-APS4-AWS-Out-Bytes
- SAE1-APN3-AWS-Out-Bytes
- USE2-AWS-Out-Bytes
- SAE1-MES1-AWS-Out-Bytes
- SAE1-AKL1-AWS-Out-Bytes
- SAE1-MIA1-AWS-Out-Bytes
- APS2-EUS1-AWS-Out-Bytes
- APS2-TPE1-AWS-Out-Bytes
- USE2-LOS1-AWS-Out-Bytes
- APN1-SAE1-AWS-Out-Bytes
- APN1-APN2-AWS-Out-Bytes
- APN1-APE1-AWS-Out-Bytes
- EUN1-APN2-AWS-Out-Bytes
- EUN1-APN1-AWS-Out-Bytes
- EU-EUS1-AWS-Out-Bytes
- APE1-APS2-AWS-Out-Bytes
- APE1-EUW3-AWS-Out-Bytes
- EU-UGW1-AWS-Out-Bytes
- EU-MES1-AWS-Out-Bytes
- APE1-USW1-AWS-Out-Bytes
- EU-EUS2-AWS-Out-Bytes
- APE1-AWS-Out-Bytes
- APE1-USW2-AWS-Out-Bytes
- EU-UGE1-AWS-Out-Bytes
- APE1-APS1-AWS-Out-Bytes
- APE1-USE2-AWS-Out-Bytes
- APE1-APN1-AWS-Out-Bytes
- APE1-EUC1-AWS-Out-Bytes
- APE1-APS3-AWS-Out-Bytes
- APE1-EU-AWS-Out-Bytes
- EU-MCT1-AWS-Out-Bytes
- APE1-APN2-AWS-Out-Bytes
- APE1-EUN1-AWS-Out-Bytes
- APE1-CAN1-AWS-Out-Bytes
- APE1-EUW2-AWS-Out-Bytes
- USW2-MIA1-AWS-Out-Bytes
- USE2-MCT1-AWS-Out-Bytes
- USW2-UGE1-AWS-Out-Bytes
- EUN1-CAN1-AWS-Out-Bytes
- USW1-CCU1-AWS-Out-Bytes
- APN1-APS3-AWS-Out-Bytes
- EU-APS7-AWS-Out-Bytes
- CAN1-APE1-AWS-Out-Bytes
- CAN1-APS5-AWS-Out-Bytes
- CAN1-EUS2-AWS-Out-Bytes
- CAN1-MEC1-AWS-Out-Bytes
- CAN1-WAW1-AWS-Out-Bytes
- CAN1-MIA1-AWS-Out-Bytes
- CAN1-APS4-AWS-Out-Bytes
- EUW2-TPE1-AWS-Out-Bytes
- EUW2-PDX1-AWS-Out-Bytes
- SAE1-APS4-AWS-Out-Bytes
- EU-PER1-AWS-Out-Bytes
- EU-SEA1-AWS-Out-Bytes
- EU-DFW1-AWS-Out-Bytes
- EU-LAS1-AWS-Out-Bytes
- EU-IAH1-AWS-Out-Bytes
- EU-DEL1-AWS-Out-Bytes
- APS3-MES1-AWS-Out-Bytes
- USW1-MNL1-AWS-Out-Bytes
- USW2-LIM1-AWS-Out-Bytes
- EUC1-APS7-AWS-Out-Bytes
- USW2-CCU1-AWS-Out-Bytes
- APS1-APS4-AWS-Out-Bytes
- USW2-TPE1-AWS-Out-Bytes
- EUW3-AFS1-AWS-Out-Bytes
- EUW3-EUC2-AWS-Out-Bytes
- USW2-APS7-AWS-Out-Bytes
- APS1-MEC1-AWS-Out-Bytes
- APS1-MIA1-AWS-Out-Bytes
- APS1-AFS1-AWS-Out-Bytes
- APS1-LAX1-AWS-Out-Bytes
- APS1-SEA1-AWS-Out-Bytes
- APS1-MSP1-AWS-Out-Bytes
- APS1-LOS1-AWS-Out-Bytes
- EUN1-APE1-AWS-Out-Bytes
- EUN1-APS6-AWS-Out-Bytes
- EUN1-APS5-AWS-Out-Bytes
- EUN1-MEC1-AWS-Out-Bytes
- EUN1-WAW1-AWS-Out-Bytes
- EUN1-EUS2-AWS-Out-Bytes
- APS1-PHX1-AWS-Out-Bytes
- APS1-CHI1-AWS-Out-Bytes
- APS2-APS7-AWS-Out-Bytes
- APS2-MCI2-AWS-Out-Bytes
- APS2-MES1-AWS-Out-Bytes
- USW2-MCT1-AWS-Out-Bytes
- USW2-CHI1-AWS-Out-Bytes
- APS3-CHI1-AWS-Out-Bytes
- APS3-EUS1-AWS-Out-Bytes
- EUW2-MEC1-AWS-Out-Bytes
- EU-AKL1-AWS-Out-Bytes
- APS1-APE1-AWS-Out-Bytes
- APN2-APN1-AWS-Out-Bytes
- APN2-USE2-AWS-Out-Bytes
- APS1-LAS1-AWS-Out-Bytes
- APS1-NYC1-AWS-Out-Bytes
- APS1-BOS1-AWS-Out-Bytes
- APS1-PDX1-AWS-Out-Bytes
- APS1-PHL1-AWS-Out-Bytes
- APS1-DEN1-AWS-Out-Bytes
- EUC1-MNL1-AWS-Out-Bytes
- USE2-APS5-AWS-Out-Bytes
- USE2-APS7-AWS-Out-Bytes
- USE2-SCL1-AWS-Out-Bytes
- USE2-WAW1-AWS-Out-Bytes
- USE2-QRO1-AWS-Out-Bytes
- USE2-MIA1-AWS-Out-Bytes
- USE2-CAN2-AWS-Out-Bytes
- EUW2-CCU1-AWS-Out-Bytes
- APS1-DFW1-AWS-Out-Bytes
- APS1-MES1-AWS-Out-Bytes
- USW2-BKK1-AWS-Out-Bytes
- USW2-PER1-AWS-Out-Bytes
- APS1-APS5-AWS-Out-Bytes
- EUN1-ILC1-AWS-Out-Bytes
- APS1-PER1-AWS-Out-Bytes
- EUW2-APS4-AWS-Out-Bytes
- APN2-USW1-AWS-Out-Bytes
- APN2-USW2-AWS-Out-Bytes
- APN3-EUC1-AWS-Out-Bytes
- APN3-USW2-AWS-Out-Bytes
- USW1-PHL1-AWS-Out-Bytes
- APN3-USE2-AWS-Out-Bytes
- USW1-CHI1-AWS-Out-Bytes
- EU-NYC1-AWS-Out-Bytes
- APN1-APS5-AWS-Out-Bytes
- EUW2-ILC1-AWS-Out-Bytes
- SAE1-TPE1-AWS-Out-Bytes
- APS3-AWS-Out-Bytes
- EUW3-PER1-AWS-Out-Bytes
- APS3-ILC1-AWS-Out-Bytes
- EUW3-APS6-AWS-Out-Bytes
- EUW3-APS4-AWS-Out-Bytes
- EUW3-ILC1-AWS-Out-Bytes
- EUW2-APE1-AWS-Out-Bytes
- USW1-WAW1-AWS-Out-Bytes
- EUW2-EUC2-AWS-Out-Bytes
- USW1-CAN2-AWS-Out-Bytes
- USE2-AKL1-AWS-Out-Bytes
- EUW2-EUS1-AWS-Out-Bytes
- EUW2-AFS1-AWS-Out-Bytes
- APN2-EUC1-AWS-Out-Bytes
- APN2-EU-AWS-Out-Bytes
- EUW2-DFW1-AWS-Out-Bytes
- EUW2-APS6-AWS-Out-Bytes
- EUW2-DEN1-AWS-Out-Bytes
- EUW2-CAN2-AWS-Out-Bytes
- EUW2-BOS1-AWS-Out-Bytes
- EUW2-APN3-AWS-Out-Bytes
- EUW2-IAH1-AWS-Out-Bytes
- EUC1-CHI1-AWS-Out-Bytes
- EU-APS6-AWS-Out-Bytes
- EUW2-MES1-AWS-Out-Bytes
- APS1-EUC2-AWS-Out-Bytes
- APS1-WAW1-AWS-Out-Bytes
- EUW2-APS5-AWS-Out-Bytes
- APS1-CAN2-AWS-Out-Bytes
- APS1-APS6-AWS-Out-Bytes
- APS1-APS7-AWS-Out-Bytes
- APS1-APN3-AWS-Out-Bytes
- APS1-SCL1-AWS-Out-Bytes
- EUW2-APS7-AWS-Out-Bytes
- EUW2-PER1-AWS-Out-Bytes
- EUW2-EUS2-AWS-Out-Bytes
- EUW3-APS5-AWS-Out-Bytes
- EUW3-APS7-AWS-Out-Bytes
- EUW3-CAN2-AWS-Out-Bytes
- USW2-LOS1-AWS-Out-Bytes
- USW2-DEL1-AWS-Out-Bytes
- USW2-EUS2-AWS-Out-Bytes
- EU-LIM1-AWS-Out-Bytes
- EU-EUC2-AWS-Out-Bytes
- EUS1-EUC2-AWS-Out-Bytes
- USW2-EUC2-AWS-Out-Bytes
- EU-CCU1-AWS-Out-Bytes
- EUW2-SEA1-AWS-Out-Bytes
- EUN1-LAX1-AWS-Out-Bytes
- EUN1-APN3-AWS-Out-Bytes
- USE2-APS6-AWS-Out-Bytes
- USW1-AKL1-AWS-Out-Bytes
- EUW2-PHL1-AWS-Out-Bytes
- EUW2-DEL1-AWS-Out-Bytes
- APN2-EUW2-AWS-Out-Bytes
- APN2-APS1-AWS-Out-Bytes
- EUW2-ATL1-AWS-Out-Bytes
- USW2-SCL1-AWS-Out-Bytes
- APS4-EUW2-AWS-Out-Bytes
- APS4-USE1-AWS-Out-Bytes
- APN2-EUN1-AWS-Out-Bytes
- EUC1-AFS1-AWS-Out-Bytes
- EUC1-APS5-AWS-Out-Bytes
- SAE1-UGE1-AWS-Out-Bytes
- SAE1-ILC1-AWS-Out-Bytes
- SAE1-SEA1-AWS-Out-Bytes
- EUW2-HAM1-AWS-Out-Bytes
- USE2-ILC1-AWS-Out-Bytes
- EUW2-CHI1-AWS-Out-Bytes
- APS3-APS6-AWS-Out-Bytes
- UGW1-APS2-AWS-Out-Bytes
- UGW1-EU-AWS-Out-Bytes
- UGW1-EUW3-AWS-Out-Bytes
- UGW1-EUW2-AWS-Out-Bytes
- UGW1-USE1-AWS-Out-Bytes
- UGW1-USE2-AWS-Out-Bytes
- UGW1-EUN1-AWS-Out-Bytes
- UGW1-USW2-AWS-Out-Bytes
- UGW1-APN1-AWS-Out-Bytes
- UGW1-APS1-AWS-Out-Bytes
- UGW1-APS3-AWS-Out-Bytes
- UGW1-APN2-AWS-Out-Bytes
- UGW1-SAE1-AWS-Out-Bytes
- UGW1-EUC1-AWS-Out-Bytes
- USW1-DEL1-AWS-Out-Bytes
- EUW2-LAX1-AWS-Out-Bytes
- UGW1-LIM1-AWS-Out-Bytes
- UGW1-WAW1-AWS-Out-Bytes
- UGW1-PDX1-AWS-Out-Bytes
- UGW1-CAN1-AWS-Out-Bytes
- EUW2-NYC1-AWS-Out-Bytes
- APE1-SAE1-AWS-Out-Bytes
- APE1-MES1-AWS-Out-Bytes
- EUW2-UGE1-AWS-Out-Bytes
- APS2-AFS1-AWS-Out-Bytes
- USW1-MIA1-AWS-Out-Bytes
- EUW2-MSP1-AWS-Out-Bytes
- APS2-DEN1-AWS-Out-Bytes
- EUW2-UGW1-AWS-Out-Bytes
- EUN1-AWS-Out-Bytes
- USW2-CAN2-AWS-Out-Bytes
- USE2-HAM1-AWS-Out-Bytes
- APN1-APS6-AWS-Out-Bytes
- APN1-EUN1-AWS-Out-Bytes
- APN1-MEC1-AWS-Out-Bytes
- UGW1-USW1-AWS-Out-Bytes
- USW1-DFW1-AWS-Out-Bytes
- USW1-MCT1-AWS-Out-Bytes
- USW1-SCL1-AWS-Out-Bytes
- USE2-DEL1-AWS-Out-Bytes
- USW1-NYC1-AWS-Out-Bytes
- USW1-APS7-AWS-Out-Bytes
- USW1-BKK1-AWS-Out-Bytes
- APS1-EUS1-AWS-Out-Bytes
- EUC1-CPH1-AWS-Out-Bytes
- APS2-ILC1-AWS-Out-Bytes
- EUN1-UGE1-AWS-Out-Bytes
- EUN1-MES1-AWS-Out-Bytes
- EUN1-TPE1-AWS-Out-Bytes
- APS2-UGW1-AWS-Out-Bytes
- APS3-QRO1-AWS-Out-Bytes
- EUN1-AFS1-AWS-Out-Bytes
- APN3-USW1-AWS-Out-Bytes
- APN3-EUN1-AWS-Out-Bytes
- EU-PHX1-AWS-Out-Bytes
- EU-CAN2-AWS-Out-Bytes
- EU-SCL1-AWS-Out-Bytes
- SAE1-APS7-AWS-Out-Bytes
- SAE1-EUC2-AWS-Out-Bytes
- SAE1-SCL1-AWS-Out-Bytes
- APS3-APS7-AWS-Out-Bytes
- USW1-PHX1-AWS-Out-Bytes
- USW2-IAH1-AWS-Out-Bytes
- EUC1-EUS2-AWS-Out-Bytes
- EUC1-MIA1-AWS-Out-Bytes
- EUN1-PDX1-AWS-Out-Bytes
- EUN1-CAN2-AWS-Out-Bytes
- EUN1-MNL1-AWS-Out-Bytes
- EUN1-DEN1-AWS-Out-Bytes
- EUC1-PDX1-AWS-Out-Bytes
- EUW2-MNL1-AWS-Out-Bytes
- APS3-LOS1-AWS-Out-Bytes
- APE1-EUS1-AWS-Out-Bytes
- EUW2-LIM1-AWS-Out-Bytes
- APS2-SEA1-AWS-Out-Bytes
- EUW2-AKL1-AWS-Out-Bytes
- EUW2-SGGOV1-AWS-Out-Bytes
- EUN1-APS7-AWS-Out-Bytes
- USW1-LOS1-AWS-Out-Bytes
- USE2-EUS2-AWS-Out-Bytes
- EUW2-QRO1-AWS-Out-Bytes
- EUN1-APS4-AWS-Out-Bytes
- USW2-EUS1-AWS-Out-Bytes
- APE1-APS5-AWS-Out-Bytes
- SAE1-LIM1-AWS-Out-Bytes
- SAE1-DEN1-AWS-Out-Bytes
- SAE1-MCT1-AWS-Out-Bytes
- SAE1-AFS1-AWS-Out-Bytes
- SAE1-IAH1-AWS-Out-Bytes
- SAE1-CCU1-AWS-Out-Bytes
- SAE1-PDX1-AWS-Out-Bytes
- SAE1-QRO1-AWS-Out-Bytes
- SAE1-BKK1-AWS-Out-Bytes
- SAE1-DEL1-AWS-Out-Bytes
- SAE1-LOS1-AWS-Out-Bytes
- SAE1-PHX1-AWS-Out-Bytes
- SAE1-LAX1-AWS-Out-Bytes
- SAE1-DFW1-AWS-Out-Bytes
- SAE1-HAM1-AWS-Out-Bytes
- SAE1-EUS1-AWS-Out-Bytes
- SAE1-BOS1-AWS-Out-Bytes
- SAE1-CHI1-AWS-Out-Bytes
- SAE1-PHL1-AWS-Out-Bytes
- SAE1-NYC1-AWS-Out-Bytes
- SAE1-MCI2-AWS-Out-Bytes
- SAE1-MNL1-AWS-Out-Bytes
- SAE1-ATL1-AWS-Out-Bytes
- SAE1-MSP1-AWS-Out-Bytes
- USW2-UGW1-AWS-Out-Bytes
- EUW2-APNE1WL1NRT1-AWS-Out-Bytes
- APS3-APN3-AWS-Out-Bytes
- EU-BKK1-AWS-Out-Bytes
- APS3-AFS1-AWS-Out-Bytes
- APS3-AKL1-AWS-Out-Bytes
- APS3-NYC1-AWS-Out-Bytes
- APS3-MCI2-AWS-Out-Bytes
- SAE1-CAN2-AWS-Out-Bytes
- APS1-IAH1-AWS-Out-Bytes
- EUW2-LOS1-AWS-Out-Bytes
- EUW2-MCT1-AWS-Out-Bytes
- EUW2-BKK1-AWS-Out-Bytes
- EU-QRO1-AWS-Out-Bytes
- EU-MCI2-AWS-Out-Bytes
- EU-LOS1-AWS-Out-Bytes
- EU-BOS1-AWS-Out-Bytes
- EU-MNL1-AWS-Out-Bytes
- EU-DEN1-AWS-Out-Bytes
- APS3-DEN1-AWS-Out-Bytes
- USW1-APNE1WL1KIX1-AWS-Out-Bytes
- USW1-USE1WL1ATL1-AWS-Out-Bytes
- USW1-EUW2WL1LON1-AWS-Out-Bytes
- UGW1-MEC1-AWS-Out-Bytes
- APS1-CCU1-AWS-Out-Bytes
- APS1-LIM1-AWS-Out-Bytes
- APS1-DEL1-AWS-Out-Bytes
- APS1-MCI2-AWS-Out-Bytes
- APS1-AKL1-AWS-Out-Bytes
- APS1-QRO1-AWS-Out-Bytes
- APS1-MCT1-AWS-Out-Bytes
- APS1-HAM1-AWS-Out-Bytes
- APS1-ATL1-AWS-Out-Bytes
- EU-CHI1-AWS-Out-Bytes
- CAN1-APS7-AWS-Out-Bytes
- APS3-BOS1-AWS-Out-Bytes
- USE2-BKK1-AWS-Out-Bytes
- UGW1-DEL1-AWS-Out-Bytes
- UGW1-MES1-AWS-Out-Bytes
- EU-ATL1-AWS-Out-Bytes
- EU-PHL1-AWS-Out-Bytes
- EU-HAM1-AWS-Out-Bytes
- EU-PDX1-AWS-Out-Bytes
- EU-LAX1-AWS-Out-Bytes
- APS2-MCT1-AWS-Out-Bytes
- APS2-DEL1-AWS-Out-Bytes
- APS2-BKK1-AWS-Out-Bytes
- APS2-HAM1-AWS-Out-Bytes
- APS2-MNL1-AWS-Out-Bytes
- APS2-APN3-AWS-Out-Bytes
- APS3-PDX1-AWS-Out-Bytes
- APS3-BKK1-AWS-Out-Bytes
- APS2-BOS1-AWS-Out-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
- EUC1-APN2-AWS-In-Bytes
- EUC1-EUW2-AWS-In-Bytes
- EUC1-USW2-AWS-In-Bytes
- EUC1-USE2-AWS-In-Bytes
- EUC1-APS2-AWS-In-Bytes
- EUC1-APN1-AWS-In-Bytes
- EUC1-EUN1-AWS-In-Bytes
- EUC1-APS3-AWS-In-Bytes
- EUC1-EU-AWS-In-Bytes
- EUC1-USE1-AWS-In-Bytes
- EUC1-APS1-AWS-In-Bytes
- EUC1-CAN1-AWS-In-Bytes
- USE1-EUW3-AWS-In-Bytes
- USE1-USW2-AWS-In-Bytes
- USE1-EUC1-AWS-In-Bytes
- USE1-APS2-AWS-In-Bytes
- USE1-EUN1-AWS-In-Bytes
- USE1-EU-AWS-In-Bytes
- USE1-SAE1-AWS-In-Bytes
- USE1-APS1-AWS-In-Bytes
- USE1-USE2-AWS-In-Bytes
- USE1-EUW2-AWS-In-Bytes
- USE1-APS3-AWS-In-Bytes
- USE1-APN1-AWS-In-Bytes
- USE1-USW1-AWS-In-Bytes
- USE1-MES1-AWS-In-Bytes
- EUW3-AWS-In-Bytes
- USE1-AWS-In-Bytes
- USE1-APN2-AWS-In-Bytes
- EU-AWS-In-Bytes
- USE2-USE1-AWS-In-Bytes
- USW2-USE1-AWS-In-Bytes
- USW2-AWS-In-Bytes
- USW2-USE2-AWS-In-Bytes
- USW2-APS3-AWS-In-Bytes
- USW2-APS1-AWS-In-Bytes
- USW2-EU-AWS-In-Bytes
- USW2-APS4-AWS-In-Bytes
- USW2-EUW2-AWS-In-Bytes
- USW2-APS2-AWS-In-Bytes
- USW2-EUN1-AWS-In-Bytes
- USW2-EUC1-AWS-In-Bytes
- USW2-APN1-AWS-In-Bytes
- USW2-EUW3-AWS-In-Bytes
- USW2-CAN1-AWS-In-Bytes
- USW2-APN2-AWS-In-Bytes
- USW1-USE1-AWS-In-Bytes
- EU-EUW2-AWS-In-Bytes
- EU-EUC1-AWS-In-Bytes
- EU-USW2-AWS-In-Bytes
- EU-USE1-AWS-In-Bytes
- EU-USE2-AWS-In-Bytes
- EU-APS5-AWS-In-Bytes
- EU-APS1-AWS-In-Bytes
- EU-TPE1-AWS-In-Bytes
- EU-SAE1-AWS-In-Bytes
- USE1-ILC1-AWS-In-Bytes
- APS1-USW2-AWS-In-Bytes
- USE1-CAN1-AWS-In-Bytes
- USE1-APE1-AWS-In-Bytes
- SAE1-USE2-AWS-In-Bytes
- SAE1-USE1-AWS-In-Bytes
- EU-EUW3-AWS-In-Bytes
- SAE1-APS1-AWS-In-Bytes
- USE1-CAN2-AWS-In-Bytes
- SAE1-USW1-AWS-In-Bytes
- SAE1-USW2-AWS-In-Bytes
- SAE1-AWS-In-Bytes
- EU-APN2-AWS-In-Bytes
- APS2-USW2-AWS-In-Bytes
- APS2-USE2-AWS-In-Bytes
- APS2-USE1-AWS-In-Bytes
- APS2-APN1-AWS-In-Bytes
- APS2-APS1-AWS-In-Bytes
- APS2-SAE1-AWS-In-Bytes
- APS2-EUW2-AWS-In-Bytes
- APS2-USW1-AWS-In-Bytes
- APS2-EU-AWS-In-Bytes
- APS2-APS3-AWS-In-Bytes
- APS2-EUN1-AWS-In-Bytes
- APS2-CAN1-AWS-In-Bytes
- APS2-EUC1-AWS-In-Bytes
- APS2-APN2-AWS-In-Bytes
- USW2-SAE1-AWS-In-Bytes
- USW2-USW1-AWS-In-Bytes
- APS2-EUW3-AWS-In-Bytes
- USW2-TPE1-AWS-In-Bytes
- APS2-WAW1-AWS-In-Bytes
- APS2-APS4-AWS-In-Bytes
- USW2-ILC1-AWS-In-Bytes
- CAN1-USE1-AWS-In-Bytes
- CAN1-EU-AWS-In-Bytes
- EU-USW1-AWS-In-Bytes
- EU-APS3-AWS-In-Bytes
- CAN1-USE2-AWS-In-Bytes
- CAN1-USW2-AWS-In-Bytes
- CAN1-EUC1-AWS-In-Bytes
- CAN1-USW1-AWS-In-Bytes
- CAN1-EUW2-AWS-In-Bytes
- CAN1-APS3-AWS-In-Bytes
- CAN1-APS1-AWS-In-Bytes
- USE1-MEC1-AWS-In-Bytes
- EUW2-USE1-AWS-In-Bytes
- EUW2-USW2-AWS-In-Bytes
- EUN1-USE1-AWS-In-Bytes
- APS1-USE1-AWS-In-Bytes
- USW1-USW2-AWS-In-Bytes
- EUN1-USW2-AWS-In-Bytes
- USE2-EUW2-AWS-In-Bytes
- USE2-EUC1-AWS-In-Bytes
- USE2-APN2-AWS-In-Bytes
- USE2-TPE1-AWS-In-Bytes
- USE2-APS1-AWS-In-Bytes
- CAN1-EUN1-AWS-In-Bytes
- CAN1-APS2-AWS-In-Bytes
- USE2-USW1-AWS-In-Bytes
- USE2-USW2-AWS-In-Bytes
- USE2-APS2-AWS-In-Bytes
- USE2-APS3-AWS-In-Bytes
- CAN1-TPE1-AWS-In-Bytes
- CAN1-APN1-AWS-In-Bytes
- CAN1-EUW3-AWS-In-Bytes
- CAN1-APN2-AWS-In-Bytes
- CAN1-SAE1-AWS-In-Bytes
- CAN1-AKL1-AWS-In-Bytes
- USE1-APS4-AWS-In-Bytes
- USE2-MEC1-AWS-In-Bytes
- SAE1-EUW2-AWS-In-Bytes
- EU-APS4-AWS-In-Bytes
- EU-APS2-AWS-In-Bytes
- USE2-EUN1-AWS-In-Bytes
- USE2-SAE1-AWS-In-Bytes
- USE2-CAN1-AWS-In-Bytes
- EUS1-APS2-AWS-In-Bytes
- EUS1-APS1-AWS-In-Bytes
- EUS1-USW2-AWS-In-Bytes
- EUS1-EUW2-AWS-In-Bytes
- EUS1-USE2-AWS-In-Bytes
- EUS1-EU-AWS-In-Bytes
- EUS1-USE1-AWS-In-Bytes
- EUS1-EUC1-AWS-In-Bytes
- EUS1-USW1-AWS-In-Bytes
- EUS1-APS3-AWS-In-Bytes
- EUS1-EUN1-AWS-In-Bytes
- USE1-APS7-AWS-In-Bytes
- EU-EUN1-AWS-In-Bytes
- EU-APN1-AWS-In-Bytes
- CAN1-APS6-AWS-In-Bytes
- CAN1-ILC1-AWS-In-Bytes
- USE2-APN3-AWS-In-Bytes
- USE2-APN1-AWS-In-Bytes
- USE2-EU-AWS-In-Bytes
- USE2-EUW3-AWS-In-Bytes
- APS2-APS5-AWS-In-Bytes
- EU-MEC1-AWS-In-Bytes
- CAN1-MEC1-AWS-In-Bytes
- USE1-EUS1-AWS-In-Bytes
- USE1-WAW1-AWS-In-Bytes
- USW2-APS6-AWS-In-Bytes
- USW2-EUS1-AWS-In-Bytes
- USW2-APN3-AWS-In-Bytes
- USW2-MEC1-AWS-In-Bytes
- USW2-AKL1-AWS-In-Bytes
- APS2-APS6-AWS-In-Bytes
- USE1-EUC2-AWS-In-Bytes
- USE1-TPE1-AWS-In-Bytes
- EUS1-CAN1-AWS-In-Bytes
- USE1-APS5-AWS-In-Bytes
- EUS1-APN1-AWS-In-Bytes
- EUS1-EUW3-AWS-In-Bytes
- EUS1-ILC1-AWS-In-Bytes
- EUS1-SAE1-AWS-In-Bytes
- EUS1-APE1-AWS-In-Bytes
- EUS1-AKL1-AWS-In-Bytes
- EUS1-APN2-AWS-In-Bytes
- APS2-DFW1-AWS-In-Bytes
- APS2-NYC1-AWS-In-Bytes
- APS2-LAX1-AWS-In-Bytes
- USE1-PHX1-AWS-In-Bytes
- USE1-LAS1-AWS-In-Bytes
- USE1-CCU1-AWS-In-Bytes
- USE1-DEN1-AWS-In-Bytes
- USE1-PDX1-AWS-In-Bytes
- USE1-AFS1-AWS-In-Bytes
- USE1-DEL1-AWS-In-Bytes
- USE1-SEA1-AWS-In-Bytes
- USE1-BKK1-AWS-In-Bytes
- USE1-LAX1-AWS-In-Bytes
- USE1-MCT1-AWS-In-Bytes
- USE1-LOS1-AWS-In-Bytes
- APS2-SCL1-AWS-In-Bytes
- USE1-APN3-AWS-In-Bytes
- USW1-USE2-AWS-In-Bytes
- USW1-EUC1-AWS-In-Bytes
- USW1-APS1-AWS-In-Bytes
- USW1-EUW2-AWS-In-Bytes
- USW1-EUS1-AWS-In-Bytes
- USW1-EU-AWS-In-Bytes
- CAN1-CAN2-AWS-In-Bytes
- USE1-MNL1-AWS-In-Bytes
- USE1-HAM1-AWS-In-Bytes
- USW1-APS4-AWS-In-Bytes
- USE1-UGW1-AWS-In-Bytes
- USW1-SAE1-AWS-In-Bytes
- USW1-EUW3-AWS-In-Bytes
- APS2-MEC1-AWS-In-Bytes
- USW1-APN1-AWS-In-Bytes
- EUN1-EU-AWS-In-Bytes
- AFS1-USE1-AWS-In-Bytes
- APN1-APS1-AWS-In-Bytes
- AFS1-APS1-AWS-In-Bytes
- APS3-APS1-AWS-In-Bytes
- APS3-USE1-AWS-In-Bytes
- APN1-USE1-AWS-In-Bytes
- APN3-USE1-AWS-In-Bytes
- USW1-APS3-AWS-In-Bytes
- USW1-APS2-AWS-In-Bytes
- USW1-APN2-AWS-In-Bytes
- USW1-APE1-AWS-In-Bytes
- USW1-CAN1-AWS-In-Bytes
- USW1-AFS1-AWS-In-Bytes
- EUW3-USE1-AWS-In-Bytes
- APE1-USE1-AWS-In-Bytes
- USW1-EUN1-AWS-In-Bytes
- EUN1-EUC1-AWS-In-Bytes
- EUW2-EU-AWS-In-Bytes
- USW1-ILC1-AWS-In-Bytes
- EUC1-USW1-AWS-In-Bytes
- USW2-APS5-AWS-In-Bytes
- APN1-USW2-AWS-In-Bytes
- APN1-EUW2-AWS-In-Bytes
- EUC1-MEC1-AWS-In-Bytes
- APS2-AWS-In-Bytes
- APN1-USE2-AWS-In-Bytes
- EUN1-USW1-AWS-In-Bytes
- EU-CAN1-AWS-In-Bytes
- APN1-EUC1-AWS-In-Bytes
- EU-EUS1-AWS-In-Bytes
- APN1-EU-AWS-In-Bytes
- EUC1-APE1-AWS-In-Bytes
- EUC1-EUW3-AWS-In-Bytes
- USE1-APS6-AWS-In-Bytes
- EUC1-SAE1-AWS-In-Bytes
- EUN1-APN1-AWS-In-Bytes
- APS1-EUW3-AWS-In-Bytes
- APS1-EUC1-AWS-In-Bytes
- EUC1-SCL1-AWS-In-Bytes
- EUN1-USE2-AWS-In-Bytes
- UGW1-USE2-AWS-In-Bytes
- UGW1-APN2-AWS-In-Bytes
- UGW1-APS1-AWS-In-Bytes
- UGW1-USW2-AWS-In-Bytes
- UGW1-CAN1-AWS-In-Bytes
- UGW1-APS3-AWS-In-Bytes
- UGW1-APS2-AWS-In-Bytes
- UGW1-EUW2-AWS-In-Bytes
- UGW1-EUN1-AWS-In-Bytes
- UGW1-SAE1-AWS-In-Bytes
- UGW1-EUC1-AWS-In-Bytes
- UGW1-EU-AWS-In-Bytes
- UGW1-USE1-AWS-In-Bytes
- UGW1-EUW3-AWS-In-Bytes
- USW1-MEC1-AWS-In-Bytes
- EUN1-SAE1-AWS-In-Bytes
- APS2-CCU1-AWS-In-Bytes
- APS2-APE1-AWS-In-Bytes
- APS2-MIA1-AWS-In-Bytes
- UGW1-MEC1-AWS-In-Bytes
- USE1-AKL1-AWS-In-Bytes
- APS1-USE2-AWS-In-Bytes
- EUC1-TPE1-AWS-In-Bytes
- USW2-AFS1-AWS-In-Bytes
- USW2-MES1-AWS-In-Bytes
- EUC1-APN3-AWS-In-Bytes
- EUN1-APS1-AWS-In-Bytes
- EUN1-APS3-AWS-In-Bytes
- USW1-MES1-AWS-In-Bytes
- USW1-EUC2-AWS-In-Bytes
- USW1-UGW1-AWS-In-Bytes
- APN1-USW1-AWS-In-Bytes
- USW1-EUS2-AWS-In-Bytes
- USW1-APN3-AWS-In-Bytes
- USW1-MIA1-AWS-In-Bytes
- EU-MSP1-AWS-In-Bytes
- EU-ILC1-AWS-In-Bytes
- EU-APE1-AWS-In-Bytes
- USW1-APS5-AWS-In-Bytes
- EU-MIA1-AWS-In-Bytes
- USE2-UGW1-AWS-In-Bytes
- CAN1-APN3-AWS-In-Bytes
- EUC1-LAS1-AWS-In-Bytes
- EUC1-APS4-AWS-In-Bytes
- EUC1-ILC1-AWS-In-Bytes
- EUC1-APS6-AWS-In-Bytes
- EUW2-APS1-AWS-In-Bytes
- EUW2-APS3-AWS-In-Bytes
- EUW2-EUC1-AWS-In-Bytes
- EUW2-EUN1-AWS-In-Bytes
- EUW2-USE2-AWS-In-Bytes
- EUW2-APN1-AWS-In-Bytes
- EUW2-APS2-AWS-In-Bytes
- EUW2-APN2-AWS-In-Bytes
- EUW2-CAN1-AWS-In-Bytes
- EUW2-EUW3-AWS-In-Bytes
- EUW2-SAE1-AWS-In-Bytes
- APN2-USE1-AWS-In-Bytes
- EUW2-USW1-AWS-In-Bytes
- USE2-EUS1-AWS-In-Bytes
- USE2-AFS1-AWS-In-Bytes
- USE2-MES1-AWS-In-Bytes
- USE2-APE1-AWS-In-Bytes
- EUW2-MIA1-AWS-In-Bytes
- USE2-APS4-AWS-In-Bytes
- APN1-EUW3-AWS-In-Bytes
- USW1-PER1-AWS-In-Bytes
- EUC1-PHX1-AWS-In-Bytes
- EUC1-LOS1-AWS-In-Bytes
- USW1-QRO1-AWS-In-Bytes
- USW1-TPE1-AWS-In-Bytes
- EU-APN3-AWS-In-Bytes
- EUW2-AWS-In-Bytes
- EUC1-AWS-In-Bytes
- CAN1-AWS-In-Bytes
- APS1-AWS-In-Bytes
- USW1-UGE1-AWS-In-Bytes
- USW1-APS6-AWS-In-Bytes
- EUN1-EUW2-AWS-In-Bytes
- EUN1-APS2-AWS-In-Bytes
- EUN1-EUW3-AWS-In-Bytes
- USE1-PER1-AWS-In-Bytes
- USW2-WAW1-AWS-In-Bytes
- USW2-APE1-AWS-In-Bytes
- USE1-UGE1-AWS-In-Bytes
- USE1-EUS2-AWS-In-Bytes
- USW2-MNL1-AWS-In-Bytes
- USW2-MIA1-AWS-In-Bytes
- EUS1-MEC1-AWS-In-Bytes
- EUS1-WAW1-AWS-In-Bytes
- EUS1-MIA1-AWS-In-Bytes
- EUS1-TPE1-AWS-In-Bytes
- EUC1-UGW1-AWS-In-Bytes
- APN1-APS2-AWS-In-Bytes
- USE1-APNE1WL1NRT1-AWS-In-Bytes
- APN2-EUW2-AWS-In-Bytes
- APN2-USE2-AWS-In-Bytes
- APN2-USW2-AWS-In-Bytes
- APN2-APS2-AWS-In-Bytes
- APN2-APS3-AWS-In-Bytes
- APN2-EUN1-AWS-In-Bytes
- APN2-APS1-AWS-In-Bytes
- APN2-EUC1-AWS-In-Bytes
- APN2-EU-AWS-In-Bytes
- APN2-APN1-AWS-In-Bytes
- APN2-APE1-AWS-In-Bytes
- EUN1-MIA1-AWS-In-Bytes
- APS1-APS3-AWS-In-Bytes
- EU-WAW1-AWS-In-Bytes
- APS3-EUW3-AWS-In-Bytes
- APS3-APN2-AWS-In-Bytes
- APS3-EUC1-AWS-In-Bytes
- APS3-USE2-AWS-In-Bytes
- MEC1-EUC1-AWS-In-Bytes
- APS3-USW1-AWS-In-Bytes
- APS3-EUW2-AWS-In-Bytes
- APS3-EUN1-AWS-In-Bytes
- MEC1-APS3-AWS-In-Bytes
- MEC1-EU-AWS-In-Bytes
- APS3-USW2-AWS-In-Bytes
- APS3-APE1-AWS-In-Bytes
- APS3-APS5-AWS-In-Bytes
- APS3-EU-AWS-In-Bytes
- APS3-APN1-AWS-In-Bytes
- APS3-CAN1-AWS-In-Bytes
- APS3-APS2-AWS-In-Bytes
- APS3-MEC1-AWS-In-Bytes
- APS3-WAW1-AWS-In-Bytes
- APS3-TPE1-AWS-In-Bytes
- APS3-SAE1-AWS-In-Bytes
- EUW3-EUC1-AWS-In-Bytes
- EUW3-USW2-AWS-In-Bytes
- EUW3-EU-AWS-In-Bytes
- EUW3-USW1-AWS-In-Bytes
- EUW3-APS3-AWS-In-Bytes
- EUW3-DEN1-AWS-In-Bytes
- EUW3-EUW2-AWS-In-Bytes
- EUW3-USE2-AWS-In-Bytes
- EUW3-APN1-AWS-In-Bytes
- EUW3-EUN1-AWS-In-Bytes
- EUW3-MIA1-AWS-In-Bytes
- EUW3-SAE1-AWS-In-Bytes
- EUW3-IAH1-AWS-In-Bytes
- EUW3-APS1-AWS-In-Bytes
- EUW3-LOS1-AWS-In-Bytes
- EUW3-LIM1-AWS-In-Bytes
- EUW3-MES1-AWS-In-Bytes
- EUW3-SEA1-AWS-In-Bytes
- EUW3-QRO1-AWS-In-Bytes
- EUW3-CCU1-AWS-In-Bytes
- EUW3-MEC1-AWS-In-Bytes
- EUW3-DFW1-AWS-In-Bytes
- EUW3-MCT1-AWS-In-Bytes
- EUW3-LAS1-AWS-In-Bytes
- EUW3-PDX1-AWS-In-Bytes
- EUW3-PHX1-AWS-In-Bytes
- EUW3-DEL1-AWS-In-Bytes
- EUW3-BKK1-AWS-In-Bytes
- EUW3-SCL1-AWS-In-Bytes
- EUW3-AKL1-AWS-In-Bytes
- EUW3-APS2-AWS-In-Bytes
- EUW3-LAX1-AWS-In-Bytes
- EUW3-CHI1-AWS-In-Bytes
- EUW3-APN3-AWS-In-Bytes
- EUW3-APN2-AWS-In-Bytes
- EUW3-EUS1-AWS-In-Bytes
- EUW3-CAN1-AWS-In-Bytes
- EUW3-HAM1-AWS-In-Bytes
- EUW3-PHL1-AWS-In-Bytes
- EUW3-NYC1-AWS-In-Bytes
- EUW3-TPE1-AWS-In-Bytes
- EUW3-MCI2-AWS-In-Bytes
- EUW3-MNL1-AWS-In-Bytes
- EUW3-WAW1-AWS-In-Bytes
- EUW3-ATL1-AWS-In-Bytes
- EUW3-APE1-AWS-In-Bytes
- EUW3-MSP1-AWS-In-Bytes
- EUW3-BOS1-AWS-In-Bytes
- EUC1-PHL1-AWS-In-Bytes
- EUC1-EUS1-AWS-In-Bytes
- USE2-UGE1-AWS-In-Bytes
- USE2-EUC2-AWS-In-Bytes
- EU-AFS1-AWS-In-Bytes
- APN1-AWS-In-Bytes
- APS1-EU-AWS-In-Bytes
- APS1-SAE1-AWS-In-Bytes
- APS1-USW1-AWS-In-Bytes
- APS1-EUW2-AWS-In-Bytes
- APS1-APN1-AWS-In-Bytes
- APS1-TPE1-AWS-In-Bytes
- APS1-APS2-AWS-In-Bytes
- USW1-AWS-In-Bytes
- APS1-EUS1-AWS-In-Bytes
- APS3-EUS1-AWS-In-Bytes
- EUC1-MES1-AWS-In-Bytes
- EUW2-WAW1-AWS-In-Bytes
- APS1-APN2-AWS-In-Bytes
- APS1-EUN1-AWS-In-Bytes
- APS1-EUS2-AWS-In-Bytes
- APS1-CAN1-AWS-In-Bytes
- APS1-UGE1-AWS-In-Bytes
- APS1-APE1-AWS-In-Bytes
- APS1-ILC1-AWS-In-Bytes
- SAE1-APE1-AWS-In-Bytes
- SAE1-EUN1-AWS-In-Bytes
- SAE1-APS3-AWS-In-Bytes
- SAE1-EU-AWS-In-Bytes
- SAE1-EUC1-AWS-In-Bytes
- SAE1-APN2-AWS-In-Bytes
- SAE1-EUW3-AWS-In-Bytes
- SAE1-CAN1-AWS-In-Bytes
- SAE1-APN1-AWS-In-Bytes
- SAE1-APS2-AWS-In-Bytes
- SAE1-APS5-AWS-In-Bytes
- SAE1-MEC1-AWS-In-Bytes
- SAE1-WAW1-AWS-In-Bytes
- APS3-APS4-AWS-In-Bytes
- SAE1-APN3-AWS-In-Bytes
- USE2-AWS-In-Bytes
- USE2-APS6-AWS-In-Bytes
- SAE1-MES1-AWS-In-Bytes
- SAE1-AKL1-AWS-In-Bytes
- SAE1-MIA1-AWS-In-Bytes
- EU-APS7-AWS-In-Bytes
- APS2-EUS1-AWS-In-Bytes
- APS2-TPE1-AWS-In-Bytes
- APS2-APN3-AWS-In-Bytes
- USE2-LOS1-AWS-In-Bytes
- APN1-SAE1-AWS-In-Bytes
- APN1-APN2-AWS-In-Bytes
- APN1-APE1-AWS-In-Bytes
- UGW1-APN1-AWS-In-Bytes
- EUN1-APN2-AWS-In-Bytes
- APE1-EU-AWS-In-Bytes
- APE1-EUC1-AWS-In-Bytes
- APE1-AWS-In-Bytes
- EU-MES1-AWS-In-Bytes
- EU-UGW1-AWS-In-Bytes
- APE1-APS3-AWS-In-Bytes
- EU-EUS2-AWS-In-Bytes
- APE1-APN2-AWS-In-Bytes
- EU-UGE1-AWS-In-Bytes
- APE1-USW1-AWS-In-Bytes
- APE1-APS1-AWS-In-Bytes
- APE1-USW2-AWS-In-Bytes
- APE1-APS2-AWS-In-Bytes
- APE1-APN1-AWS-In-Bytes
- APE1-EUW2-AWS-In-Bytes
- APE1-EUW3-AWS-In-Bytes
- APE1-USE2-AWS-In-Bytes
- APE1-CAN1-AWS-In-Bytes
- APE1-EUN1-AWS-In-Bytes
- USE2-MCT1-AWS-In-Bytes
- USW2-UGE1-AWS-In-Bytes
- EUN1-CAN1-AWS-In-Bytes
- USW1-CCU1-AWS-In-Bytes
- APN1-APS3-AWS-In-Bytes
- AFS1-APS3-AWS-In-Bytes
- AFS1-USW2-AWS-In-Bytes
- AFS1-EUN1-AWS-In-Bytes
- AFS1-EU-AWS-In-Bytes
- AFS1-APS2-AWS-In-Bytes
- AFS1-USE2-AWS-In-Bytes
- AFS1-EUW2-AWS-In-Bytes
- AFS1-EUC1-AWS-In-Bytes
- CAN1-APE1-AWS-In-Bytes
- CAN1-EUS2-AWS-In-Bytes
- CAN1-APS5-AWS-In-Bytes
- CAN1-WAW1-AWS-In-Bytes
- CAN1-MIA1-AWS-In-Bytes
- CAN1-APS4-AWS-In-Bytes
- EUW2-TPE1-AWS-In-Bytes
- EUW2-PDX1-AWS-In-Bytes
- SAE1-APS4-AWS-In-Bytes
- APE1-SAE1-AWS-In-Bytes
- APE1-UGE1-AWS-In-Bytes
- EU-SEA1-AWS-In-Bytes
- EU-PER1-AWS-In-Bytes
- EU-DFW1-AWS-In-Bytes
- EU-LAS1-AWS-In-Bytes
- EU-DEL1-AWS-In-Bytes
- EU-IAH1-AWS-In-Bytes
- APS3-MES1-AWS-In-Bytes
- USW1-MNL1-AWS-In-Bytes
- USW2-LIM1-AWS-In-Bytes
- EUC1-APS7-AWS-In-Bytes
- USW2-CCU1-AWS-In-Bytes
- APS1-APS4-AWS-In-Bytes
- EUW3-AFS1-AWS-In-Bytes
- EUW3-EUC2-AWS-In-Bytes
- USW2-APS7-AWS-In-Bytes
- CAN1-APS7-AWS-In-Bytes
- APS1-MEC1-AWS-In-Bytes
- APS1-AFS1-AWS-In-Bytes
- APS1-MIA1-AWS-In-Bytes
- APS1-SEA1-AWS-In-Bytes
- APS1-LAX1-AWS-In-Bytes
- APS1-LOS1-AWS-In-Bytes
- APS1-MSP1-AWS-In-Bytes
- EUN1-APE1-AWS-In-Bytes
- EUN1-APS6-AWS-In-Bytes
- EUN1-APS5-AWS-In-Bytes
- EUN1-MEC1-AWS-In-Bytes
- EUN1-EUS2-AWS-In-Bytes
- EUN1-WAW1-AWS-In-Bytes
- APS1-PHX1-AWS-In-Bytes
- APS1-CHI1-AWS-In-Bytes
- APS2-APS7-AWS-In-Bytes
- APS2-MES1-AWS-In-Bytes
- APS2-MCI2-AWS-In-Bytes
- USW2-MCT1-AWS-In-Bytes
- USW2-CHI1-AWS-In-Bytes
- APS3-CHI1-AWS-In-Bytes
- EUW2-MEC1-AWS-In-Bytes
- EU-AKL1-AWS-In-Bytes
- APS1-LAS1-AWS-In-Bytes
- APS1-PDX1-AWS-In-Bytes
- APS1-NYC1-AWS-In-Bytes
- APS1-PHL1-AWS-In-Bytes
- APS1-DEN1-AWS-In-Bytes
- APS1-BOS1-AWS-In-Bytes
- APN2-EUW3-AWS-In-Bytes
- APS2-UGW1-AWS-In-Bytes
- APS2-LIM1-AWS-In-Bytes
- EUC1-MNL1-AWS-In-Bytes
- USE2-APS5-AWS-In-Bytes
- USE2-APS7-AWS-In-Bytes
- USE2-SCL1-AWS-In-Bytes
- USE2-WAW1-AWS-In-Bytes
- USE2-MIA1-AWS-In-Bytes
- USE2-QRO1-AWS-In-Bytes
- USE2-CAN2-AWS-In-Bytes
- EUW2-EUS1-AWS-In-Bytes
- EUW2-CCU1-AWS-In-Bytes
- APS1-DFW1-AWS-In-Bytes
- APS1-MES1-AWS-In-Bytes
- USW2-BKK1-AWS-In-Bytes
- USW2-PER1-AWS-In-Bytes
- APE1-APS6-AWS-In-Bytes
- APS1-APS5-AWS-In-Bytes
- APE1-MES1-AWS-In-Bytes
- APE1-MEC1-AWS-In-Bytes
- APE1-WAW1-AWS-In-Bytes
- APE1-LIM1-AWS-In-Bytes
- APE1-APN3-AWS-In-Bytes
- EUN1-ILC1-AWS-In-Bytes
- APS1-PER1-AWS-In-Bytes
- EUW2-APS4-AWS-In-Bytes
- APN2-USW1-AWS-In-Bytes
- APN3-USW2-AWS-In-Bytes
- USW1-PHL1-AWS-In-Bytes
- USW1-CHI1-AWS-In-Bytes
- EU-MCT1-AWS-In-Bytes
- EU-NYC1-AWS-In-Bytes
- APN3-USE2-AWS-In-Bytes
- APN1-AFS1-AWS-In-Bytes
- APN1-APS5-AWS-In-Bytes
- APN2-SAE1-AWS-In-Bytes
- EUW2-ILC1-AWS-In-Bytes
- UGW1-TPE1-AWS-In-Bytes
- UGW1-ILC1-AWS-In-Bytes
- UGW1-APS5-AWS-In-Bytes
- SAE1-TPE1-AWS-In-Bytes
- SAE1-EUS1-AWS-In-Bytes
- APS3-ILC1-AWS-In-Bytes
- EUW3-APS6-AWS-In-Bytes
- EUW3-PER1-AWS-In-Bytes
- EUW3-ILC1-AWS-In-Bytes
- EUW3-APS4-AWS-In-Bytes
- EUW2-APE1-AWS-In-Bytes
- USW1-WAW1-AWS-In-Bytes
- EUW2-EUC2-AWS-In-Bytes
- USW1-CAN2-AWS-In-Bytes
- USE2-AKL1-AWS-In-Bytes
- EUW2-AFS1-AWS-In-Bytes
- EUW2-DFW1-AWS-In-Bytes
- EUW2-BOS1-AWS-In-Bytes
- EUW2-CAN2-AWS-In-Bytes
- EUW2-APS6-AWS-In-Bytes
- EUW2-DEN1-AWS-In-Bytes
- EUW2-IAH1-AWS-In-Bytes
- EUW2-LIM1-AWS-In-Bytes
- EUW2-APN3-AWS-In-Bytes
- EUC1-CHI1-AWS-In-Bytes
- EUW2-MES1-AWS-In-Bytes
- EU-APS6-AWS-In-Bytes
- USW1-LIM1-AWS-In-Bytes
- APS1-EUC2-AWS-In-Bytes
- APS1-LIM1-AWS-In-Bytes
- APS1-WAW1-AWS-In-Bytes
- APS1-CAN2-AWS-In-Bytes
- APS1-APS6-AWS-In-Bytes
- APS1-APS7-AWS-In-Bytes
- APS1-SCL1-AWS-In-Bytes
- APS1-APN3-AWS-In-Bytes
- EUW2-PER1-AWS-In-Bytes
- EUW2-APS7-AWS-In-Bytes
- EUW2-EUS2-AWS-In-Bytes
- EUW2-APS5-AWS-In-Bytes
- EUW3-APS5-AWS-In-Bytes
- EUW3-APS7-AWS-In-Bytes
- EUW3-CAN2-AWS-In-Bytes
- USW2-LOS1-AWS-In-Bytes
- USW2-DEL1-AWS-In-Bytes
- USW2-EUS2-AWS-In-Bytes
- EU-LIM1-AWS-In-Bytes
- EU-EUC2-AWS-In-Bytes
- EUS1-EUC2-AWS-In-Bytes
- USW2-EUC2-AWS-In-Bytes
- EU-CCU1-AWS-In-Bytes
- EUW2-SEA1-AWS-In-Bytes
- EUW2-NYC1-AWS-In-Bytes
- EUN1-APN3-AWS-In-Bytes
- EUN1-LAX1-AWS-In-Bytes
- APN2-MEC1-AWS-In-Bytes
- EUC1-LIM1-AWS-In-Bytes
- USW1-AKL1-AWS-In-Bytes
- EUW2-DEL1-AWS-In-Bytes
- USW2-SCL1-AWS-In-Bytes
- EUW2-LAS1-AWS-In-Bytes
- APS4-APS1-AWS-In-Bytes
- APS4-EUW2-AWS-In-Bytes
- APS4-USE1-AWS-In-Bytes
- EUW2-PHL1-AWS-In-Bytes
- EUW2-ATL1-AWS-In-Bytes
- APN3-EUC1-AWS-In-Bytes
- EUC1-AFS1-AWS-In-Bytes
- EUC1-APS5-AWS-In-Bytes
- APN1-EUN1-AWS-In-Bytes
- SAE1-ILC1-AWS-In-Bytes
- SAE1-UGE1-AWS-In-Bytes
- SAE1-SEA1-AWS-In-Bytes
- EUW2-HAM1-AWS-In-Bytes
- USE2-ILC1-AWS-In-Bytes
- EUW2-APNE1WL1NRT1-AWS-In-Bytes
- APS3-APS6-AWS-In-Bytes
- USW1-DEL1-AWS-In-Bytes
- UGW1-USW1-AWS-In-Bytes
- UGW1-APN3-AWS-In-Bytes
- UGW1-LIM1-AWS-In-Bytes
- UGW1-WAW1-AWS-In-Bytes
- UGW1-PDX1-AWS-In-Bytes
- EUW2-LAX1-AWS-In-Bytes
- EUW2-UGE1-AWS-In-Bytes
- APS2-AFS1-AWS-In-Bytes
- EUW2-UGW1-AWS-In-Bytes
- APS2-DEN1-AWS-In-Bytes
- APN2-APS7-AWS-In-Bytes
- APN2-MES1-AWS-In-Bytes
- EUN1-AWS-In-Bytes
- USW2-CAN2-AWS-In-Bytes
- APE1-ILC1-AWS-In-Bytes
- APN2-APS4-AWS-In-Bytes
- USE2-LIM1-AWS-In-Bytes
- USE2-HAM1-AWS-In-Bytes
- APN1-APS6-AWS-In-Bytes
- APN1-MEC1-AWS-In-Bytes
- UGW1-AFS1-AWS-In-Bytes
- UGW1-APE1-AWS-In-Bytes
- USW1-DFW1-AWS-In-Bytes
- USW1-MCT1-AWS-In-Bytes
- USW1-SCL1-AWS-In-Bytes
- USE2-DEL1-AWS-In-Bytes
- USW1-NYC1-AWS-In-Bytes
- USW1-APS7-AWS-In-Bytes
- USW1-BKK1-AWS-In-Bytes
- EUC1-CPH1-AWS-In-Bytes
- EU-PHX1-AWS-In-Bytes
- APS2-ILC1-AWS-In-Bytes
- EUN1-UGE1-AWS-In-Bytes
- EUN1-MES1-AWS-In-Bytes
- EUN1-TPE1-AWS-In-Bytes
- APS3-QRO1-AWS-In-Bytes
- EUN1-AFS1-AWS-In-Bytes
- APN3-USW1-AWS-In-Bytes
- APN3-EUN1-AWS-In-Bytes
- EU-CAN2-AWS-In-Bytes
- APN2-TPE1-AWS-In-Bytes
- EU-SCL1-AWS-In-Bytes
- APE1-EUC2-AWS-In-Bytes
- APE1-APS7-AWS-In-Bytes
- APE1-MIA1-AWS-In-Bytes
- SAE1-APS7-AWS-In-Bytes
- SAE1-EUC2-AWS-In-Bytes
- SAE1-SCL1-AWS-In-Bytes
- APS3-APS7-AWS-In-Bytes
- USW1-PHX1-AWS-In-Bytes
- APE1-TPE1-AWS-In-Bytes
- APE1-QRO1-AWS-In-Bytes
- USW2-IAH1-AWS-In-Bytes
- EUC1-EUS2-AWS-In-Bytes
- EUC1-MIA1-AWS-In-Bytes
- EUN1-PDX1-AWS-In-Bytes
- EUN1-MNL1-AWS-In-Bytes
- EUN1-CAN2-AWS-In-Bytes
- EUN1-DEN1-AWS-In-Bytes
- UGW1-MIA1-AWS-In-Bytes
- EUC1-PDX1-AWS-In-Bytes
- EUW2-MNL1-AWS-In-Bytes
- APS3-LOS1-AWS-In-Bytes
- APE1-EUS1-AWS-In-Bytes
- EUW2-MSP1-AWS-In-Bytes
- APS2-SEA1-AWS-In-Bytes
- EUW2-AKL1-AWS-In-Bytes
- AFS1-APN2-AWS-In-Bytes
- APS3-AKL1-AWS-In-Bytes
- EUN1-APS7-AWS-In-Bytes
- USW1-LOS1-AWS-In-Bytes
- USE2-EUS2-AWS-In-Bytes
- EUW2-QRO1-AWS-In-Bytes
- EUN1-APS4-AWS-In-Bytes
- APE1-APS5-AWS-In-Bytes
- SAE1-PDX1-AWS-In-Bytes
- SAE1-AFS1-AWS-In-Bytes
- SAE1-LAX1-AWS-In-Bytes
- SAE1-DEN1-AWS-In-Bytes
- SAE1-DFW1-AWS-In-Bytes
- SAE1-QRO1-AWS-In-Bytes
- SAE1-CCU1-AWS-In-Bytes
- SAE1-LAS1-AWS-In-Bytes
- SAE1-PHX1-AWS-In-Bytes
- SAE1-DEL1-AWS-In-Bytes
- SAE1-LOS1-AWS-In-Bytes
- SAE1-LIM1-AWS-In-Bytes
- SAE1-IAH1-AWS-In-Bytes
- SAE1-MCT1-AWS-In-Bytes
- SAE1-BKK1-AWS-In-Bytes
- SAE1-NYC1-AWS-In-Bytes
- SAE1-ATL1-AWS-In-Bytes
- SAE1-MNL1-AWS-In-Bytes
- SAE1-MCI2-AWS-In-Bytes
- SAE1-HAM1-AWS-In-Bytes
- SAE1-MSP1-AWS-In-Bytes
- SAE1-BOS1-AWS-In-Bytes
- SAE1-CHI1-AWS-In-Bytes
- SAE1-PHL1-AWS-In-Bytes
- USW2-UGW1-AWS-In-Bytes
- EUW2-CHI1-AWS-In-Bytes
- APS3-APN3-AWS-In-Bytes
- EU-BKK1-AWS-In-Bytes
- APS3-AFS1-AWS-In-Bytes
- APS3-NYC1-AWS-In-Bytes
- APS3-MCI2-AWS-In-Bytes
- SAE1-CAN2-AWS-In-Bytes
- APS1-IAH1-AWS-In-Bytes
- EUW2-BKK1-AWS-In-Bytes
- EUW2-LOS1-AWS-In-Bytes
- EUW2-MCT1-AWS-In-Bytes
- EU-BOS1-AWS-In-Bytes
- EU-LOS1-AWS-In-Bytes
- EU-CHI1-AWS-In-Bytes
- EU-MCI2-AWS-In-Bytes
- EU-DEN1-AWS-In-Bytes
- EU-MNL1-AWS-In-Bytes
- EU-PDX1-AWS-In-Bytes
- AFS1-TPE1-AWS-In-Bytes
- APS3-DEN1-AWS-In-Bytes
- USW1-APNE1WL1KIX1-AWS-In-Bytes
- USW1-USE1WL1ATL1-AWS-In-Bytes
- USW1-EUW2WL1LON1-AWS-In-Bytes
- AFS1-APE1-AWS-In-Bytes
- AFS1-APN1-AWS-In-Bytes
- USE2-MNL1-AWS-In-Bytes
- APS1-MCI2-AWS-In-Bytes
- APS1-CCU1-AWS-In-Bytes
- APS1-DEL1-AWS-In-Bytes
- APS1-MCT1-AWS-In-Bytes
- APS1-AKL1-AWS-In-Bytes
- APS1-QRO1-AWS-In-Bytes
- APS1-ATL1-AWS-In-Bytes
- APS1-HAM1-AWS-In-Bytes
- UGW1-APS4-AWS-In-Bytes
- EU-ATL1-AWS-In-Bytes
- EU-PHL1-AWS-In-Bytes
- EU-HAM1-AWS-In-Bytes
- APS3-BOS1-AWS-In-Bytes
- UGW1-APS7-AWS-In-Bytes
- USE2-BKK1-AWS-In-Bytes
- UGW1-DEL1-AWS-In-Bytes
- UGW1-MES1-AWS-In-Bytes
- EU-LAX1-AWS-In-Bytes
- EU-QRO1-AWS-In-Bytes
- APS2-DEL1-AWS-In-Bytes
- APS2-MCT1-AWS-In-Bytes
- APS2-BKK1-AWS-In-Bytes
- APS2-MNL1-AWS-In-Bytes
- APS2-HAM1-AWS-In-Bytes
- APS3-PDX1-AWS-In-Bytes
- APS3-BKK1-AWS-In-Bytes
- APS2-BOS1-AWS-In-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
- EUC1-DataTransfer-In-Bytes
- DataTransfer-In-Bytes
- USE2-DataTransfer-In-Bytes
- USW2-DataTransfer-In-Bytes
- USW1-DataTransfer-In-Bytes
- EU-DataTransfer-In-Bytes
- APS1-DataTransfer-In-Bytes
- APN1-DataTransfer-In-Bytes
- SAE1-DataTransfer-In-Bytes
- APS2-DataTransfer-In-Bytes
- APS3-DataTransfer-In-Bytes
- CAN1-DataTransfer-In-Bytes
- EUW3-DataTransfer-In-Bytes
- EUN1-DataTransfer-In-Bytes
- EUW2-DataTransfer-In-Bytes
- EUS1-DataTransfer-In-Bytes
- AFS1-DataTransfer-In-Bytes
- UGW1-DataTransfer-In-Bytes
- APN2-DataTransfer-In-Bytes
- MEC1-DataTransfer-In-Bytes
- APE1-DataTransfer-In-Bytes
- APN3-DataTransfer-In-Bytes
- APS4-DataTransfer-In-Bytes
DataTransfer-Out-Bytes
The amount of data (per GB) transferred out of AWS to the internet.
Billing Codes
- EUC1-DataTransfer-Out-Bytes
- DataTransfer-Out-Bytes
- USE2-DataTransfer-Out-Bytes
- USW2-DataTransfer-Out-Bytes
- USW1-DataTransfer-Out-Bytes
- APS1-DataTransfer-Out-Bytes
- APN1-DataTransfer-Out-Bytes
- SAE1-DataTransfer-Out-Bytes
- APS2-DataTransfer-Out-Bytes
- EU-DataTransfer-Out-Bytes
- CAN1-DataTransfer-Out-Bytes
- APS3-DataTransfer-Out-Bytes
- EUW3-DataTransfer-Out-Bytes
- EUW2-DataTransfer-Out-Bytes
- EUN1-DataTransfer-Out-Bytes
- EUS1-DataTransfer-Out-Bytes
- AFS1-DataTransfer-Out-Bytes
- UGW1-DataTransfer-Out-Bytes
- APN2-DataTransfer-Out-Bytes
- MEC1-DataTransfer-Out-Bytes
- APE1-DataTransfer-Out-Bytes
- APN3-DataTransfer-Out-Bytes
- APS4-DataTransfer-Out-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
- USW2-DataTransfer-xAZ-Out-Bytes
- USE1-DataTransfer-xAZ-Out-Bytes
- EUW3-DataTransfer-xAZ-Out-Bytes
- EUW2-DataTransfer-xAZ-Out-Bytes
- CAN1-DataTransfer-xAZ-Out-Bytes
- EU-DataTransfer-xAZ-Out-Bytes
- APS1-DataTransfer-xAZ-Out-Bytes
- APS2-DataTransfer-xAZ-Out-Bytes
- EUC1-DataTransfer-xAZ-Out-Bytes
- APN1-DataTransfer-xAZ-Out-Bytes
- USE2-DataTransfer-xAZ-Out-Bytes
- APN2-DataTransfer-xAZ-Out-Bytes
- SAE1-DataTransfer-xAZ-Out-Bytes
- UGW1-DataTransfer-xAZ-Out-Bytes
- EUN1-DataTransfer-xAZ-Out-Bytes
- APE1-DataTransfer-xAZ-Out-Bytes
- USW1-DataTransfer-xAZ-Out-Bytes
- APS3-DataTransfer-xAZ-Out-Bytes
- APN3-DataTransfer-xAZ-Out-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
- EUW3-DataTransfer-xAZ-In-Bytes
- EUW2-DataTransfer-xAZ-In-Bytes
- CAN1-DataTransfer-xAZ-In-Bytes
- EU-DataTransfer-xAZ-In-Bytes
- USW2-DataTransfer-xAZ-In-Bytes
- APS2-DataTransfer-xAZ-In-Bytes
- EUC1-DataTransfer-xAZ-In-Bytes
- APN1-DataTransfer-xAZ-In-Bytes
- USE2-DataTransfer-xAZ-In-Bytes
- APN2-DataTransfer-xAZ-In-Bytes
- SAE1-DataTransfer-xAZ-In-Bytes
- UGW1-DataTransfer-xAZ-In-Bytes
- EUN1-DataTransfer-xAZ-In-Bytes
- APE1-DataTransfer-xAZ-In-Bytes
- USW1-DataTransfer-xAZ-In-Bytes
- APS3-DataTransfer-xAZ-In-Bytes
- APN3-DataTransfer-xAZ-In-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
- USE1-CloudFront-In-Bytes
- USE2-CloudFront-In-Bytes
- USW2-CloudFront-In-Bytes
- USW1-CloudFront-In-Bytes
- APN1-CloudFront-In-Bytes
- SAE1-CloudFront-In-Bytes
- EU-CloudFront-In-Bytes
- EUC1-CloudFront-In-Bytes
- APS2-CloudFront-In-Bytes
- EUW3-CloudFront-In-Bytes
- CAN1-CloudFront-In-Bytes
- EUW2-CloudFront-In-Bytes
- APS1-CloudFront-In-Bytes
- EUN1-CloudFront-In-Bytes
- EUS1-CloudFront-In-Bytes
- APS3-CloudFront-In-Bytes
- AFS1-CloudFront-In-Bytes
- APE1-CloudFront-In-Bytes
- UGW1-CloudFront-In-Bytes
- APN2-CloudFront-In-Bytes
- APN3-CloudFront-In-Bytes
CloudFront-Out-Bytes
The amount of data (per GB) transferred out of an AWS region to CloudFront.
Billing Codes
- USE1-CloudFront-Out-Bytes
- USE2-CloudFront-Out-Bytes
- USW2-CloudFront-Out-Bytes
- USW1-CloudFront-Out-Bytes
- APN1-CloudFront-Out-Bytes
- SAE1-CloudFront-Out-Bytes
- EU-CloudFront-Out-Bytes
- EUC1-CloudFront-Out-Bytes
- APS2-CloudFront-Out-Bytes
- EUW3-CloudFront-Out-Bytes
- CAN1-CloudFront-Out-Bytes
- EUW2-CloudFront-Out-Bytes
- EUN1-CloudFront-Out-Bytes
- APS1-CloudFront-Out-Bytes
- EUS1-CloudFront-Out-Bytes
- APS3-CloudFront-Out-Bytes
- AFS1-CloudFront-Out-Bytes
- APE1-CloudFront-Out-Bytes
- UGW1-CloudFront-Out-Bytes
- APN3-CloudFront-Out-Bytes
- APN2-CloudFront-Out-Bytes
CloudFrontChina-Out-Bytes
The amount of data (per GB) transferred out of an AWS region to CloudFront China.
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
Compute
Fargate-GB-Hours
Fargate works on a pay-as-you-go pricing model, where you pay only for the resources that you consume. There is one charge for vCPU and one charge for GB of memory used. This billing code is specific to the per-GB fee for Linux x86 architectures. For Savings Plans, a negation amount will show as a negative number.
Billing Codes
- USE1-Fargate-GB-Hours
- EUC1-Fargate-GB-Hours
- EU-Fargate-GB-Hours
- USE1-Fargate-GB-Hours
- USE2-Fargate-GB-Hours
- CAN1-Fargate-GB-Hours
- EUW3-Fargate-GB-Hours
- UGE1-Fargate-GB-Hours
- APS2-Fargate-GB-Hours
- APS1-Fargate-GB-Hours
- EUW2-Fargate-GB-Hours
- EUC1-Fargate-GB-Hours
- EUW3-Fargate-GB-Hours
- USE2-Fargate-GB-Hours
- CAN1-Fargate-GB-Hours
- APS2-Fargate-GB-Hours
- APS1-Fargate-GB-Hours
- EUW2-Fargate-GB-Hours
- UGE1-Fargate-GB-Hours
- USW2-Fargate-GB-Hours
- APN1-Fargate-GB-Hours
- EU-Fargate-GB-Hours
- UGW1-Fargate-GB-Hours
- SAE1-Fargate-GB-Hours
- UGW1-Fargate-GB-Hours
- USW2-Fargate-GB-Hours
- APN1-Fargate-GB-Hours
- EUS1-Fargate-GB-Hours
- EUN1-Fargate-GB-Hours
- USW1-Fargate-GB-Hours
- APS3-Fargate-GB-Hours
- USW1-Fargate-GB-Hours
- EUN1-Fargate-GB-Hours
- AFS1-Fargate-GB-Hours
- APN2-Fargate-GB-Hours
- EUS1-Fargate-GB-Hours
- AFS1-Fargate-GB-Hours
- SAE1-Fargate-GB-Hours
- APS3-Fargate-GB-Hours
- APN3-Fargate-GB-Hours
- APE1-Fargate-GB-Hours
- APN2-Fargate-GB-Hours
- APE1-Fargate-GB-Hours
- APN3-Fargate-GB-Hours
- MEC1-Fargate-GB-Hours
- CNN1-Fargate-GB-Hours
- APS4-Fargate-GB-Hours
- MEC1-Fargate-GB-Hours
- APS6-Fargate-GB-Hours
Fargate-vCPU-Hours:perCPU
Fargate works on a pay-as-you-go pricing model, where you pay only for the resources that you consume. There is one charge for vCPU and one charge for GB of memory used. This billing code is specific to the per-vCPU fee for Linux x86 architectures. For Savings Plans, a negation amount will show as a negative number.
Billing Codes
- USE1-Fargate-vCPU-Hours:perCPU
- EUC1-Fargate-vCPU-Hours:perCPU
- EU-Fargate-vCPU-Hours:perCPU
- USE1-Fargate-vCPU-Hours:perCPU
- EUW3-Fargate-vCPU-Hours:perCPU
- APS1-Fargate-vCPU-Hours:perCPU
- APS2-Fargate-vCPU-Hours:perCPU
- CAN1-Fargate-vCPU-Hours:perCPU
- EUW2-Fargate-vCPU-Hours:perCPU
- USE2-Fargate-vCPU-Hours:perCPU
- UGE1-Fargate-vCPU-Hours:perCPU
- EUW3-Fargate-vCPU-Hours:perCPU
- CAN1-Fargate-vCPU-Hours:perCPU
- APS1-Fargate-vCPU-Hours:perCPU
- EUC1-Fargate-vCPU-Hours:perCPU
- EUW2-Fargate-vCPU-Hours:perCPU
- USE2-Fargate-vCPU-Hours:perCPU
- APS2-Fargate-vCPU-Hours:perCPU
- UGE1-Fargate-vCPU-Hours:perCPU
- USW2-Fargate-vCPU-Hours:perCPU
- APN1-Fargate-vCPU-Hours:perCPU
- EU-Fargate-vCPU-Hours:perCPU
- UGW1-Fargate-vCPU-Hours:perCPU
- SAE1-Fargate-vCPU-Hours:perCPU
- UGW1-Fargate-vCPU-Hours:perCPU
- USW2-Fargate-vCPU-Hours:perCPU
- APN1-Fargate-vCPU-Hours:perCPU
- EUS1-Fargate-vCPU-Hours:perCPU
- EUN1-Fargate-vCPU-Hours:perCPU
- USW1-Fargate-vCPU-Hours:perCPU
- USW1-Fargate-vCPU-Hours:perCPU
- APS3-Fargate-vCPU-Hours:perCPU
- EUN1-Fargate-vCPU-Hours:perCPU
- AFS1-Fargate-vCPU-Hours:perCPU
- EUS1-Fargate-vCPU-Hours:perCPU
- APE1-Fargate-vCPU-Hours:perCPU
- AFS1-Fargate-vCPU-Hours:perCPU
- SAE1-Fargate-vCPU-Hours:perCPU
- APS3-Fargate-vCPU-Hours:perCPU
- APN2-Fargate-vCPU-Hours:perCPU
- APN3-Fargate-vCPU-Hours:perCPU
- APN3-Fargate-vCPU-Hours:perCPU
- APN2-Fargate-vCPU-Hours:perCPU
- APE1-Fargate-vCPU-Hours:perCPU
- MEC1-Fargate-vCPU-Hours:perCPU
- CNN1-Fargate-vCPU-Hours:perCPU
- CNN1-Fargate-vCPU-Hours:perCPU
- APS4-Fargate-vCPU-Hours:perCPU
- MEC1-Fargate-vCPU-Hours:perCPU
- APS6-Fargate-vCPU-Hours:perCPU
SpotUsage-Fargate-vCPU-Hours:perCPU
For interrupt-tolerant workloads, Fargate Spot offers spare capacity for discounted prices, but the drawback is that AWS can interrupt your process at any time when capacity is needed elsewhere. You pay only for the resources that you consume. There is one charge for vCPU and one charge for GB of memory used. This billing code is specific to the per-vCPU fee for Linux x86 architectures.
Billing Codes
- USE1-SpotUsage-Fargate-vCPU-Hours:perCPU
- EUW3-SpotUsage-Fargate-vCPU-Hours:perCPU
- UGE1-SpotUsage-Fargate-vCPU-Hours:perCPU
- USE2-SpotUsage-Fargate-vCPU-Hours:perCPU
- EUW2-SpotUsage-Fargate-vCPU-Hours:perCPU
- CAN1-SpotUsage-Fargate-vCPU-Hours:perCPU
- APS2-SpotUsage-Fargate-vCPU-Hours:perCPU
- EUC1-SpotUsage-Fargate-vCPU-Hours:perCPU
- APS1-SpotUsage-Fargate-vCPU-Hours:perCPU
- EU-SpotUsage-Fargate-vCPU-Hours:perCPU
- USW2-SpotUsage-Fargate-vCPU-Hours:perCPU
- USW1-SpotUsage-Fargate-vCPU-Hours:perCPU
- APS3-SpotUsage-Fargate-vCPU-Hours:perCPU
- SAE1-SpotUsage-Fargate-vCPU-Hours:perCPU
- APN1-SpotUsage-Fargate-vCPU-Hours:perCPU
- APN2-SpotUsage-Fargate-vCPU-Hours:perCPU
- EUS2-SpotUsage-Fargate-vCPU-Hours:perCPU
- EUN1-SpotUsage-Fargate-vCPU-Hours:perCPU
- APS6-SpotUsage-Fargate-vCPU-Hours:perCPU
SpotUsage-Fargate-GB-Hours
For interrupt-tolerant workloads, Fargate Spot offers spare capacity for discounted prices, but the drawback is that AWS can interrupt your process at any time when capacity is needed elsewhere. You pay only for the resources that you consume. There is one charge for vCPU and one charge for GB of memory used. This billing code is specific to the per-GB fee for Linux x86 architectures.
Billing Codes
- USE1-SpotUsage-Fargate-GB-Hours
- EUW2-SpotUsage-Fargate-GB-Hours
- UGE1-SpotUsage-Fargate-GB-Hours
- APS2-SpotUsage-Fargate-GB-Hours
- USE2-SpotUsage-Fargate-GB-Hours
- CAN1-SpotUsage-Fargate-GB-Hours
- EUW3-SpotUsage-Fargate-GB-Hours
- EUC1-SpotUsage-Fargate-GB-Hours
- APS1-SpotUsage-Fargate-GB-Hours
- EU-SpotUsage-Fargate-GB-Hours
- USW2-SpotUsage-Fargate-GB-Hours
- APS3-SpotUsage-Fargate-GB-Hours
- USW1-SpotUsage-Fargate-GB-Hours
- SAE1-SpotUsage-Fargate-GB-Hours
- APN1-SpotUsage-Fargate-GB-Hours
- APN2-SpotUsage-Fargate-GB-Hours
- EUS2-SpotUsage-Fargate-GB-Hours
- EUN1-SpotUsage-Fargate-GB-Hours
- APS6-SpotUsage-Fargate-GB-Hours
Fargate-EphemeralStorage-GB-Hours
Fargate gives you 20 GB of ephemeral storage included for all Tasks and Pods. However, charges occur per storage-GB per hour for additional storage over the 20 GB limit.
Billing Codes
- USE1-Fargate-EphemeralStorage-GB-Hours
- EU-Fargate-EphemeralStorage-GB-Hours
- USE2-Fargate-EphemeralStorage-GB-Hours
- CAN1-Fargate-EphemeralStorage-GB-Hours
- USW2-Fargate-EphemeralStorage-GB-Hours
- EUW3-Fargate-EphemeralStorage-GB-Hours
- APS2-Fargate-EphemeralStorage-GB-Hours
- UGW1-Fargate-EphemeralStorage-GB-Hours
- USW1-Fargate-EphemeralStorage-GB-Hours
- EUC1-Fargate-EphemeralStorage-GB-Hours
- EUN1-Fargate-EphemeralStorage-GB-Hours
- APS1-Fargate-EphemeralStorage-GB-Hours
- EUW2-Fargate-EphemeralStorage-GB-Hours
- APN2-Fargate-EphemeralStorage-GB-Hours
- APN1-Fargate-EphemeralStorage-GB-Hours
- SAE1-Fargate-EphemeralStorage-GB-Hours
- APS3-Fargate-EphemeralStorage-GB-Hours
Fargate-ARM-vCPU-Hours:perCPU
Fargate works on a pay-as-you-go pricing model, where you pay only for the resources that you consume. There is one charge for vCPU and one charge for GB of memory used. This billing code is specific to the per-vCPU fee for Linux ARM architectures. For Savings Plans, a negation amount will show as a negative number.
Billing Codes
- USE1-Fargate-ARM-vCPU-Hours:perCPU
- USE1-Fargate-ARM-vCPU-Hours:perCPU
- EUW3-Fargate-ARM-vCPU-Hours:perCPU
- EU-Fargate-ARM-vCPU-Hours:perCPU
- USW2-Fargate-ARM-vCPU-Hours:perCPU
- USE2-Fargate-ARM-vCPU-Hours:perCPU
- EUC1-Fargate-ARM-vCPU-Hours:perCPU
- APS2-Fargate-ARM-vCPU-Hours:perCPU
- USE2-Fargate-ARM-vCPU-Hours:perCPU
- USW2-Fargate-ARM-vCPU-Hours:perCPU
- EU-Fargate-ARM-vCPU-Hours:perCPU
- APS2-Fargate-ARM-vCPU-Hours:perCPU
- APN2-Fargate-ARM-vCPU-Hours:perCPU
- EUW2-Fargate-ARM-vCPU-Hours:perCPU
- EUC1-Fargate-ARM-vCPU-Hours:perCPU
- CAN1-Fargate-ARM-vCPU-Hours:perCPU
- CAN1-Fargate-ARM-vCPU-Hours:perCPU
- APN1-Fargate-ARM-vCPU-Hours:perCPU
- APS1-Fargate-ARM-vCPU-Hours:perCPU
- APN1-Fargate-ARM-vCPU-Hours:perCPU
- EUW2-Fargate-ARM-vCPU-Hours:perCPU
- APS1-Fargate-ARM-vCPU-Hours:perCPU
- EUN1-Fargate-ARM-vCPU-Hours:perCPU
- SAE1-Fargate-ARM-vCPU-Hours:perCPU
- UGW1-Fargate-ARM-vCPU-Hours:perCPU
- APS3-Fargate-ARM-vCPU-Hours:perCPU
- APN2-Fargate-ARM-vCPU-Hours:perCPU
- USW1-Fargate-ARM-vCPU-Hours:perCPU
- APS3-Fargate-ARM-vCPU-Hours:perCPU
- UGW1-Fargate-ARM-vCPU-Hours:perCPU
Fargate-ARM-GB-Hours
Fargate works on a pay-as-you-go pricing model, where you pay only for the resources that you consume. There is one charge for vCPU and one charge for GB of memory used. This billing code is specific to the per-GB fee for Linux ARM architectures. For Savings Plans, a negation amount will show as a negative number.
Billing Codes
- USE1-Fargate-ARM-GB-Hours
- USE1-Fargate-ARM-GB-Hours
- EUW3-Fargate-ARM-GB-Hours
- EU-Fargate-ARM-GB-Hours
- USW2-Fargate-ARM-GB-Hours
- USE2-Fargate-ARM-GB-Hours
- EUC1-Fargate-ARM-GB-Hours
- APS2-Fargate-ARM-GB-Hours
- USE2-Fargate-ARM-GB-Hours
- USW2-Fargate-ARM-GB-Hours
- EU-Fargate-ARM-GB-Hours
- APS2-Fargate-ARM-GB-Hours
- APN2-Fargate-ARM-GB-Hours
- EUW2-Fargate-ARM-GB-Hours
- EUC1-Fargate-ARM-GB-Hours
- CAN1-Fargate-ARM-GB-Hours
- CAN1-Fargate-ARM-GB-Hours
- APN1-Fargate-ARM-GB-Hours
- APS1-Fargate-ARM-GB-Hours
- APN1-Fargate-ARM-GB-Hours
- EUW2-Fargate-ARM-GB-Hours
- APS1-Fargate-ARM-GB-Hours
- EUN1-Fargate-ARM-GB-Hours
- SAE1-Fargate-ARM-GB-Hours
- UGW1-Fargate-ARM-GB-Hours
- APS3-Fargate-ARM-GB-Hours
- APN2-Fargate-ARM-GB-Hours
- USW1-Fargate-ARM-GB-Hours
- APS3-Fargate-ARM-GB-Hours
- UGW1-Fargate-ARM-GB-Hours
Fargate-Windows-vCPU-Hours:perCPU
Fargate works on a pay-as-you-go pricing model, where you pay only for the resources that you consume. There is one charge for vCPU and one charge for GB of memory used. This billing code is specific to the per-vCPU fee for Windows x86 architectures. For Savings Plans, a negation amount will show as a negative number.
Billing Codes
Fargate-Windows-GB-Hours
Fargate works on a pay-as-you-go pricing model, where you pay only for the resources that you consume. There is one charge for vCPU and one charge for GB of memory used. This billing code is specific to the per-GB fee for Windows x86 architectures. For Savings Plans, a negation amount will show as a negative number.
Billing Codes
Fargate-Windows-OS-Hours:perCPU
The per vCPU per hour licensing fee for Fargate Windows x86 architectures. For Savings Plans, a negation amount will show as a negative number.
Billing Codes
ECS-Anywhere-Instance-hours
ECS Anywhere is a feature that enables ECS to manage on-premises instances. Charges apply per instance-hour an on-premises instance is running.
ECS-Anywhere-Instance-hours-WithFree
ECS Anywhere is a feature that enables ECS to manage on-premises instances. 2200 instance hours are included per month for the first 6 months at no cost.
Billing Codes
SpotUsage-Fargate-ARM-GB-Hours
For interrupt-tolerant workloads, Fargate Spot offers spare capacity for discounted prices, but the drawback is that AWS can interrupt your process at any time when capacity is needed elsewhere. You pay only for the resources that you consume. There is one charge for vCPU and one charge for GB of memory used. This billing code is specific to the per-GB fee for Linux ARM architectures.
Billing Codes
SpotUsage-Fargate-ARM-vCPU-Hours:perCPU
For interrupt-tolerant workloads, Fargate Spot offers spare capacity for discounted prices, but the drawback is that AWS can interrupt your process at any time when capacity is needed elsewhere. You pay only for the resources that you consume. There is one charge for vCPU and one charge for GB of memory used. This billing code is specific to the per-vCPU fee for Linux ARM architectures.
Billing Codes
Compute Metering
ECS-EC2-vCPU-Hours
The number of CPU-hours used by ECS tasks on EC2 instances. Billing is based on the underlying EC2 instance costs, not these CPU-hours. If you are only using Fargate there will be no additional charge for ECS EC2 compute.
Billing Codes
- EU-ECS-EC2-vCPU-Hours
- USE1-ECS-EC2-vCPU-Hours
- EUS1-ECS-EC2-vCPU-Hours
- USE2-ECS-EC2-vCPU-Hours
- USW2-ECS-EC2-vCPU-Hours
- UGW1-ECS-EC2-vCPU-Hours
- EUC1-ECS-EC2-vCPU-Hours
- USW1-ECS-EC2-vCPU-Hours
- CAN1-ECS-EC2-vCPU-Hours
- APS2-ECS-EC2-vCPU-Hours
- APN1-ECS-EC2-vCPU-Hours
- EUN1-ECS-EC2-vCPU-Hours
- APS3-ECS-EC2-vCPU-Hours
- EUW3-ECS-EC2-vCPU-Hours
- APS1-ECS-EC2-vCPU-Hours
- EUW2-ECS-EC2-vCPU-Hours
- APN2-ECS-EC2-vCPU-Hours
- UGE1-ECS-EC2-vCPU-Hours
- MES1-ECS-EC2-vCPU-Hours
- SAE1-ECS-EC2-vCPU-Hours
- EUS2-ECS-EC2-vCPU-Hours
ECS-EC2-GB-Hours
The number of GB-hours used by ECS tasks on EC2 instances. billing is based on the underlying EC2 instance costs, not these GB-hours. If you are only using Fargate there will be no additional charge for ECS EC2 compute.
Billing Codes
- EU-ECS-EC2-GB-Hours
- USE1-ECS-EC2-GB-Hours
- USW2-ECS-EC2-GB-Hours
- CAN1-ECS-EC2-GB-Hours
- EUS1-ECS-EC2-GB-Hours
- USE2-ECS-EC2-GB-Hours
- APN1-ECS-EC2-GB-Hours
- UGW1-ECS-EC2-GB-Hours
- EUC1-ECS-EC2-GB-Hours
- USW1-ECS-EC2-GB-Hours
- APS2-ECS-EC2-GB-Hours
- EUN1-ECS-EC2-GB-Hours
- APS3-ECS-EC2-GB-Hours
- EUW2-ECS-EC2-GB-Hours
- EUW3-ECS-EC2-GB-Hours
- APS1-ECS-EC2-GB-Hours
- APN2-ECS-EC2-GB-Hours
- UGE1-ECS-EC2-GB-Hours
- MES1-ECS-EC2-GB-Hours
- SAE1-ECS-EC2-GB-Hours
- MEC1-ECS-EC2-GB-Hours
- EUS2-ECS-EC2-GB-Hours
DT-Data Transfer
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.
Billing Codes
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.