# What is TimedStorage-ByteHrs?

AWS cost guides · Updated 17 November 2026

**Short answer:** In Amazon S3, TimedStorage-ByteHrs is the usage type for data stored in S3 Standard, measured as byte-hours and shown on the bill as GB-months. Other storage classes have their own variants, such as TimedStorage-SIA-ByteHrs for Standard-IA and TimedStorage-GlacierByteHrs for Glacier Flexible Retrieval. No prefix means us-east-1; otherwise the Region code comes first, as in EUW2-TimedStorage-ByteHrs.

## The family of storage usage types

| Usage type | Storage class |
|---|---|
| `TimedStorage-ByteHrs` | S3 Standard |
| `TimedStorage-SIA-ByteHrs` / `-SIA-SmObjects` | Standard-IA / small-object minimum |
| `TimedStorage-ZIA-ByteHrs` | One Zone-IA |
| `TimedStorage-INT-FA-ByteHrs`, `-INT-IA-`, `-INT-AIA-` | Intelligent-Tiering access tiers |
| `TimedStorage-GIR-ByteHrs` | Glacier Instant Retrieval |
| `TimedStorage-GlacierByteHrs` | Glacier Flexible Retrieval |
| `TimedStorage-GDA-ByteHrs` | Glacier Deep Archive |

The same name appears under CloudWatch for log storage and under DynamoDB for table storage, so always check the service. The `-SmObjects` lines are the 128 KB minimum billable size in the IA classes: a 10 KB object is billed as 128 KB.

## What counts as stored data

- Every object version, current and noncurrent, in versioned buckets.
- Parts of multipart uploads that were started and never completed or aborted.
- Data in buckets you have forgotten, including log, inventory and Athena result buckets.
- Metadata for archived objects: each object in Glacier Flexible Retrieval or Deep Archive carries 40 KB of extra metadata, 32 KB billed at the archive rate and 8 KB billed at the S3 Standard rate. Millions of tiny archived objects therefore keep adding to `TimedStorage-ByteHrs`.

Glacier Flexible Retrieval and Deep Archive restores also create a temporary copy that is billed for as long as you asked to keep it, on top of the archived original.

Storage is measured daily and averaged over the month, so deleting 10 TB halfway through the month saves about half of that month's charge for it.

## Find the buckets behind it

```
# Standard storage per bucket (daily metric, reported in the bucket's Region)
aws cloudwatch get-metric-statistics --namespace AWS/S3 \
  --metric-name BucketSizeBytes \
  --dimensions Name=BucketName,Value=my-bucket Name=StorageType,Value=StandardStorage \
  --start-time 2026-11-14T00:00:00Z --end-time 2026-11-16T00:00:00Z \
  --period 86400 --statistics Average --region eu-west-2

# Incomplete multipart uploads hiding in a bucket
aws s3api list-multipart-uploads --bucket my-bucket \
  --query 'Uploads[].[Key,Initiated]' --output table
```

S3 Storage Lens gives the same view across all buckets and accounts, including noncurrent version bytes. For a quick ranking by size, see [finding the largest buckets](https://cloudconsole.dev/how-to/find-largest-s3-buckets).

## Reduce it

1. **Expire what you do not need**: lifecycle rules for logs, temporary exports and build artefacts.
2. **Abort incomplete multipart uploads** after a few days with a lifecycle rule.
3. **Expire noncurrent versions** in versioned buckets ([S3 versioning cost](https://cloudconsole.dev/costs/s3-versioning-cost)).
4. **Move cold data to a cheaper class**, or use Intelligent-Tiering when access is unpredictable ([storage classes](https://cloudconsole.dev/costs/s3-storage-classes-cost)).

```
{
  "Rules": [{
    "ID": "abort-incomplete-mpu",
    "Status": "Enabled",
    "Filter": {},
    "AbortIncompleteMultipartUpload": {"DaysAfterInitiation": 7}
  }]
}
```

Apply it with `aws s3api put-bucket-lifecycle-configuration --bucket my-bucket --lifecycle-configuration file://lifecycle.json`. That call replaces the bucket's whole lifecycle configuration, so merge with any existing rules first.

Expect the saving to show gradually: lifecycle actions run asynchronously, and because storage is averaged over the month, the first bill after a clean-up only partly reflects it.

## Questions

### What does TimedStorage-ByteHrs mean?

It is S3 Standard storage over time: bytes stored multiplied by hours, reported as GB-months on the bill.

### Why is TimedStorage-ByteHrs higher than my bucket sizes?

Noncurrent versions, incomplete multipart uploads and forgotten buckets all count as stored data.

### Is TimedStorage-ByteHrs only S3?

No. CloudWatch Logs and DynamoDB use the same name for their storage, so read it together with the service.

## When this happens away from your desk

S3 storage only goes one way unless something expires it. CloudConsole, a phone app for AWS, shows spend by usage type and explains TimedStorage-ByteHrs and its per-class variants, so storage growth is visible from your phone.

[About the CloudConsole app](https://cloudconsole.dev/aws-console-app) · [Download on the App Store](https://apps.apple.com/app/cloudconsole-for-aws/id6835419710)

## Sources

- [Understanding your AWS billing and usage reports for Amazon S3](https://docs.aws.amazon.com/AmazonS3/latest/userguide/aws-usage-report-understand.html)
- [Configuring a lifecycle rule to delete incomplete multipart uploads](https://docs.aws.amazon.com/AmazonS3/latest/userguide/mpu-abort-incomplete-mpu-lifecycle-config.html)

## Related

- [S3 storage classes and cost](https://cloudconsole.dev/costs/s3-storage-classes-cost)
- [Does S3 versioning cost more?](https://cloudconsole.dev/costs/s3-versioning-cost)
- [S3 Requests-Tier1 and Requests-Tier2](https://cloudconsole.dev/costs/s3-requests-tier1-tier2)
- [How to find S3 bucket size](https://cloudconsole.dev/how-to/find-largest-s3-buckets)
- [aws s3api put-bucket-lifecycle-configuration](https://cloudconsole.dev/cli/s3api-put-bucket-lifecycle-configuration)
- [Aurora I/O-Optimized vs Aurora Standard](https://cloudconsole.dev/costs/aurora-io-optimized-vs-standard)

---

Source: https://cloudconsole.dev/costs/s3-timedstorage-bytehrs

CloudConsole is an independent iPhone and Android app for Amazon Web Services by Cloudconcur Ltd. It is not affiliated with Amazon Web Services.
