Understanding Your AWS Billing and Usage Reports

Understanding Your AWS Billing and Usage Reports for Amazon S3

Amazon S3 billing and usage reports use codes and abbreviations. For example, for usage type, which is defined in the following table, region is replaced with one of the following abbreviations:

  • APE1: Asia Pacific (Hong Kong)
  • APN1: Asia Pacific (Tokyo)
  • APN2: Asia Pacific (Seoul)
  • APS1: Asia Pacific (Singapore)
  • APS2: Asia Pacific (Sydney)
  • APS3: Asia Pacific (Mumbai)
  • CAN1: Canada (Central)
  • EUN1: Europe (Stockholm)
  • EUC1: Europe (Frankfurt)
  • EU: Europe (Ireland)
  • EUW2: Europe (London)
  • EUW3: Europe (Paris)
  • MES1: Middle East (Bahrain)
  • SAE1: South America (São Paulo)
  • UGW1: AWS GovCloud (US-West)
  • UGE1: AWS GovCloud (US-East)
  • USE1 (or no prefix): US East (N. Virginia)
  • USE2: US East (Ohio)
  • USW1: US West (N. California)
  • USW2: US West (Oregon)

For information about pricing by AWS Region, see Amazon S3 Pricing.

The first column in the following table lists usage types that appear in your billing and usage reports.

Usage Types

Usage TypeUnitsGranularityDescription
region1-region2-AWS-In-BytesBytesHourlyThe amount of data transferred in to AWS Region1 from AWS Region2
region1-region2-AWS-Out-BytesBytesHourlyThe amount of data transferred from AWS Region1 to AWS Region2
region-BatchOperations-JobsCountHourlyThe number of Amazon S3 batch operations jobs performed.
region-BatchOperations-ObjectsCountHourlyThe number of object operations performed by Amazon S3 batch operations.
region-DataTransfer-In-BytesBytesHourlyThe amount of data transferred into Amazon S3 from the internet
region-DataTransfer-Out-BytesBytesHourlyThe amount of data transferred from Amazon S3 to the internet1
region-C3DataTransfer-In-BytesBytesHourlyThe amount of data transferred into Amazon S3 from Amazon EC2 within the same AWS Region
region-C3DataTransfer-Out-BytesBytesHourlyThe amount of data transferred from Amazon S3 to Amazon EC2 within the same AWS Region
region-S3G-DataTransfer-In-BytesBytesHourlyThe amount of data transferred into Amazon S3 to restore objects from GLACIER or DEEP ARCHIVE storage
region-S3G-DataTransfer-Out-BytesBytesHourlyThe amount of data transferred from Amazon S3 to transition objects to GLACIER or DEEP ARCHIVE storage
region-DataTransfer-Regional-BytesBytesHourlyThe amount of data transferred from Amazon S3 to AWS resources within the same AWS Region
StorageObjectCountCountDailyThe number of objects stored within a given bucket
region-CloudFront-In-BytesBytesHourlyThe amount of data transferred into an AWS Region from a CloudFront distribution
region-CloudFront-Out-BytesBytesHourlyThe amount of data transferred from an AWS Region to a CloudFront distribution
region-EarlyDelete-ByteHrsByte-Hours2HourlyProrated storage usage for objects deleted from, GLACIER storage before the 90-day minimum commitment ended3
region-EarlyDelete-GDAByte-Hours2HourlyProrated storage usage for objects deleted from DEEP ARCHIVE storage before the 180-day minimum commitment ended 3
region-EarlyDelete-SIAByte-HoursHourlyProrated storage usage for objects deleted from STANDARD_IA before the 30-day minimum commitment ended4
region-EarlyDelete-ZIAByte-HoursHourlyProrated storage usage for objects deleted from ONEZONE_IA before the 30-day minimum commitment ended4
region-EarlyDelete-SIA-SmObjectsByte-HoursHourlyProrated storage usage for small objects (smaller than 128 KB) that were deleted from STANDARD_IA before the 30-day minimum commitment ended4
region-EarlyDelete-ZIA-SmObjectsByte-HoursHourlyProrated storage usage for small objects (smaller than 128 KB) that were deleted from ONEZONE_IA before the 30-day minimum commitment ended4
region-Inventory-ObjectsListedObjectsHourlyThe number of objects listed for an object group (objects are grouped by bucket or prefix) with an inventory list
region-Requests-GLACIER-Tier1CountHourlyThe number of PUT, COPY, POST, InitiateMultipartUpload, UploadPart, or CompleteMultipartUpload requests on GLACIER objects
region-Requests-GLACIER-Tier2CountHourlyThe number of GET and all other requests not listed on GLACIER objects
region-Requests-SIA-Tier1CountHourlyThe number of PUT, COPY, POST, or LIST requests on STANDARD_IA objects
region-Requests-ZIA-Tier1CountHourlyThe number of PUT, COPY, POST, or LIST requests on ONEZONE_IA objects
region-Requests-SIA-Tier2CountHourlyThe number of GET and all other non-SIA-Tier1 requests on STANDARD_IA objects
region-Requests-ZIA-Tier2CountHourlyThe number of GET and all other non-ZIA-Tier1 requests on ONEZONE_IA objects
region-Requests-Tier1CountHourlyThe number of PUT, COPY, POST, or LIST requests for STANDARD, RRS, and tags
region-Requests-Tier2CountHourlyThe number of GET and all other non-Tier1 requests
region-Requests-Tier3CountHourlyThe number of lifecycle requests to GLACIER or DEEP ARCHIVE and standard GLACIER restore requests
region-Requests-Tier4CountHourlyThe number of lifecycle transitions to INTELLIGENT_TIERING, STANDARD_IA, or ONEZONE_IA storage
region-Requests-Tier5CountHourlyThe number of Bulk GLACIER restore requests
region-Requests-GDA-Tier1CountHourlyThe number of PUT, COPY, POST, InitiateMultipartUpload, UploadPart, or CompleteMultipartUpload requests on DEEP Archive objects
region-Requests-GDA-Tier2CountHourlyThe number of GET, HEAD, and LIST requests
region-Requests-GDA-Tier3CountHourlyThe number of DEEP ARCHIVE standard restore requests
region-Requests-GDA-Tier5CountHourlyThe number of Bulk DEEP ARCHIVE restore requests
region-Requests-Tier6CountHourlyThe number of Expedited GLACIER restore requests
region-Bulk-Retrieval-BytesBytesHourlyThe number of bytes of data retrieved with Bulk GLACIER or DEEP ARCHIVE requests
region-Requests-INT-Tier1CountHourlyThe number of PUT, COPY, POST, or LIST requests on INTELLIGENT_TIERING objects
region-Requests-INT-Tier2CountHourlyThe number of GET and all other non-Tier1 requests for INTELLIGENT_TIERING objects
region-Select-Returned-INT-BytesBytesHourlyThe number of bytes of data returned with Select requests from INTELLIGENT_TIERING storage
region-Select-Scanned-INT-BytesBytesHourlyThe number of bytes of data scanned with Select requests from INTELLIGENT_TIERING storage
region-EarlyDelete-INTByte-HoursHourlyProrated storage usage for objects deleted from INTELLIGENT_TIERING before the 30-day minimum commitment ended
region-Monitoring-Automation-INTObjectsHourlyThe number of unique objects monitored and auto-tiered in the INTELLIGENT_TIERING storage class
region-Expedited-Retrieval-BytesBytesHourlyThe number of bytes of data retrieved with Expedited GLACIER requests
region-Standard-Retrieval-BytesBytesHourlyThe number of bytes of data retrieved with standard GLACIER or DEEP ARCHIVE requests
region-Retrieval-SIABytesHourlyThe number of bytes of data retrieved from STANDARD_IA storage
region-Retrieval-ZIABytesHourlyThe number of bytes of data retrieved from ONEZONE_IA storage
region-StorageAnalytics-ObjCountObjectsHourlyThe number of unique objects in each object group (where objects are grouped by bucket or prefix) tracked by storage analytics
region-Select-Scanned-BytesBytesHourlyThe number of bytes of data scanned with Select requests from STANDARD storage
region-Select-Scanned-SIA-BytesBytesHourlyThe number of bytes of data scanned with Select requests from STANDARD_IA storage
region-Select-Scanned-ZIA-BytesBytesHourlyThe number of bytes of data scanned with Select requests from ONEZONE_IA storage
region-Select-Returned-BytesBytesHourlyThe number of bytes of data returned with Select requests from STANDARD storage
region-Select-Returned-SIA-BytesBytesHourlyThe number of bytes of data returned with Select requests from STANDARD_IA storage
region-Select-Returned-ZIA-BytesBytesHourlyThe number of bytes of data returned with Select requests from ONEZONE_IA storage
region-TagStorage-TagHrsTag-HoursDailyThe total of tags on all objects in the bucket reported by hour
region-TimedStorage-ByteHrsByte-HoursDailyThe number of byte-hours that data was stored in STANDARD storage
region-TimedStorage-GLACIERByteHrsByte-HoursDailyThe number of byte-hours that data was stored in GLACIER storage
region-TimedStorage-GlacierStagingByte-HoursDailyThe number of byte-hours that data was stored in GLACIER staging storage
region-TimedStorage-GDA-ByteHrsByte-HoursDailyThe number of byte-hours that data was stored in DEEP ARCHIVE storage
region-TimedStorage-GDA-StagingByte-HoursDailyThe number of byte-hours that data was stored in DEEP ARCHIVE staging storage
region-TimedStorage-INT-FA-ByteHrsByte-HoursDailyThe number of byte-hours that data was stored in the frequent access tier of INTELLIGENT_TIERING storage
region-TimedStorage-INT-IA-ByteHrsByte-HoursDailyThe number of byte-hours that data was stored in the infrequent access tier of INTELLIGENT_TIERING storage
region-TimedStorage-RRS-ByteHrsbByte-HoursDailyThe number of byte-hours that data was stored in Reduced Redundancy Storage (RRS) storage
region-TimedStorage-SIA-ByteHrsByte-HoursDailyThe number of byte-hours that data was stored in STANDARD_IA storage
region-TimedStorage-ZIA-ByteHrsByte-HoursDailyThe number of byte-hours that data was stored in ONEZONE_IA storage
region-TimedStorage-SIA-SmObjectsByte-HoursDailyThe number of byte-hours that small objects (smaller than 128 KB) were stored in STANDARD_IA storage
region-TimedStorage-ZIA-SmObjectsByte-HoursDailyThe number of byte-hours that small objects (smaller than 128 KB) were stored in ONEZONE_IA storage

Notes:

  1. If you terminate a transfer before completion, the amount of data that is transferred might exceed the amount of data that your application receives. This discrepancy can occur because a transfer termination request cannot be executed instantaneously, and some amount of data might be in transit pending execution of the termination request. This data in transit is billed as data transferred “out.”

  2. For more information on the byte-hours unit, see Converting Usage Byte-Hours to Billed GB-Months.

  3. When objects that are archived to the GLACIER or DEEP ARCHIVE storage class are deleted, overwritten, or transitioned to a different storage class before the minimum storage commitment has passed, which is 90 days for GLACIER or 180-days for DEEP ARCHIVE, there is a prorated charge per gigabyte for the remaining days.

  4. For objects that are in INTELLIGENT_TIERING, STANDARD_IA, or ONEZONE_IA storage, when they are deleted, overwritten, or transitioned to a different storage class prior to 30 days, there is a prorated charge per gigabyte for the remaining days.

  5. For small objects (smaller than 128 KB) that are in STANDARD_IA or ONEZONE_IA storage, when they are deleted, overwritten, or transitioned to a different storage class prior to 30 days, there is a prorated charge per gigabyte for the remaining days.

  6. There is no minimum billable object size for objects in the INTELLIGENT_TIERING storage class, but objects that are smaller than 128 KB are not eligible for auto-tiering and are always charged at the rate for the INTELLIGENT_TIERING frequent access tier.

Tracking Operations in Your Usage Reports

Operations describe the action taken on your AWS object or bucket by the specified usage type. Operations are indicated by self-explanatory codes, such as PutObject or ListBucket. To see which actions on your bucket generated a specific type of usage, use these codes. When you create a usage report, you can choose to include All Operations, or a specific operation, for example, GetObject, to report on.

Converting Usage Byte-Hours to Billed GB-Months

The volume of storage that we bill you for each month is based on the average amount of storage you used throughout the month. You are billed for all of the object data and metadata stored in buckets that you created under your AWS account. For more information about metadata, see Object Key and Metadata.

We measure your storage usage in TimedStorage-ByteHrs, which are totaled up at the end of the month to generate your monthly charges. The usage report reports your storage usage in byte-hours and the billing reports report storage usage in GB-months. To correlate your usage report to your billing reports, you need to convert byte-hours into GB-months.

For example, if you store 100 GB (107,374,182,400 bytes) of STANDARD Amazon S3 storage data in your bucket for the first 15 days in March, and 100 TB (109,951,162,777,600 bytes) of STANDARD Amazon S3 storage data for the final 16 days in March, you will have used 42,259,901,212,262,400 byte-hours.

First, calculate the total byte-hour usage:

[107,374,182,400 bytes x 15 days x (24 hours/day)]
+ [109,951,162,777,600 bytes x 16 days x (24 hours/day)]
= 42,259,901,212,262,400 byte-hours

Then convert the byte-hours to GB-Months:

42,259,901,212,262,400 byte-hours/1,073,741,824 bytes per GB/24 hours per day
/31 days in March
=52,900 GB-Months

More Info