Storage account access tier 'cool'
See original GitHub issueIs there any way to set the access tier on a storage account object? My understanding is that there is a significant cost difference between coold and hot tier access so would like to configure the tier to reduce cost.
let storageAcc = storageAccount {
name "myStorageAccount"
sku Storage.Sku.Standard_LRS
use_static_website contentPath "index.html"
}
produces
{
"apiVersion": "2019-06-01",
"dependsOn": [],
"kind": "StorageV2",
"location": "uksouth",
"name": "myStorageAccount",
"properties": {},
"sku": {
"name": "Standard_LRS"
},
"type": "Microsoft.Storage/storageAccounts"
}
I believe the difference I would like is
"location": "uksouth",
"name": "myStorageAccount",
- "properties": {},
+ "properties": {
+ "accessTier": "Cool"
+ },
"type": "Microsoft.Storage/storageAccounts"
}
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Access tiers for blob data - Azure Storage
Cool tier - An online tier optimized for storing data that is infrequently accessed or modified. Data in the cool tier should be...
Read more >Best practices for using blob access tiers - Azure Storage
If you plan to read data less frequently, the cool, cold or archive tier might make the most sense because it raises the...
Read more >Azure Blob storage: hot, cool, and archive access tiers
In opposed to hot storage, the cool access tier has lower storage costs but higher access costs. Not to mention, this tier is...
Read more >Change Access Tiers of a blob and Azure storage account
Cool tier. This tier is suitable for infrequent data access requirements. It also gives good performance and durability. The pricing for this ...
Read more >Microsoft Azure Cool Blob Storage Overview
Azure Blob Storage Cool access tier is intended for data that you expect to access less often than once a month, but more...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
So this is indeed the “default” tier for new blobs. Interesting. I guess it only works for StorageV2 or Blob Storage accounts.
BTW the CDN enhancements are now published as part of 1.3.0-beta1.
Do you think that adding a
default_access_tier
operator to the storage builder would be a good solution?