S3 contd
Storage Classes in S3
-
The default storage class in S3 is standard
- Access cost is less
- Storage cost is high
- when you upload any object 3 copies are made and are stored in 3 zones in same region.
-
Refer Here for storage classes
- Reduced Redundancy Storage – REDUCED_REDUNDANCY
- S3 Express One Zone – EXPRESS_ONEZONE
- S3 Intelligent-Tiering – INTELLIGENT_TIERING
- S3 One Zone-IA – ONEZONE_IA
- S3 Standard – STANDARD
- S3 Standard-IA – STANDARD_IA
- Amazon’s guarantee (SLA)
| S3 Storage Class | Durability | Availability SLA | Designed Availability |
|---|---|---|---|
| S3 Standard | 99.999999999% (11 9’s) | 99.9% | 99.99% |
| S3 Intelligent-Tiering | 99.999999999% | 99.9% | 99.9% |
| S3 Standard-IA (Infrequent Access) | 99.999999999% | 99.9% | 99.9% |
| S3 One Zone-IA | 99.999999999% | 99.5% | 99.5% |
| S3 Glacier Instant Retrieval | 99.999999999% | 99.9% | 99.9% |
| S3 Glacier Flexible Retrieval (formerly Glacier) | 99.999999999% | 99.9% | 99.9% |
| S3 Glacier Deep Archive | 99.999999999% | 99.9% | 99.9% |
| S3 Reduced Redundancy (RRS) (legacy, not recommended) | 99.99% | 99.9% | 99.99% |
Lets create objects with different storage classes
- While uploading the objects set the storage class under properties section.
- Post uploading use actions
-
Lets assume there is a pattern as shown below, AWS S3 supports lifecycle rules
- first 100 days in standard
- 101-365 Standard-IA
- Post 1 year Glacier.
-
S3 supports versioning: Properties -> Bucket Versioning
Azure Blob Storage
Azure Access Tiers & Redundancy
- Refer Here for official docs of Access tiers
- Hot
- Cool
- Cold
- Archive
- Refer Here for official docs on redundancy
- LRS
- ZRS
- GRS
- GZRS
- Durability and Availability parameters Refer Here
-
Setting Redundancy during creation of storage account
-
Setting default Access tier during creation of storage account
- Versioning in Azure Blob storage
- Lifecycle rules in Azure Blob Storage
