An Azure storage account can be used to store various types of data objects. There are many types of data objects like blobs, files, queues, tables, and disks, for example, blob storage is used to store large data files such as video, audio files, or any kind of large data objects. All different types of Azure data objects are used to store different type of data safely. The storage account provides a unique namespace for your Azure Storage data that is accessible from anywhere in the world over HTTP or HTTPS. Data in a storage account is durable and highly available, secure, and massively scalable.
Access Tiers?
There are different access tiers, allowing you to store blob object data in the most cost-effective manner. Available access tiers include:
- Hot - Optimized for storing data that is accessed frequently.
- Cool - Optimized for storing data that is infrequently accessed and stored for at least 30 days.
- Archive - Optimized for storing data that is rarely accessed and stored for at least 180 days with flexible latency requirements, on the order of hours.
Types of storage accounts
Azure Storage offers several types of storage accounts. Each type supports different features and has its own pricing model. Consider these differences before you create a storage account to determine the type of account that is best for your applications.
Standard
Basic storage account type for blobs, files, queues, and tables. Recommended for most scenarios using Azure Storage.
Premium
Recommended for scenarios that require low latency.
Redundancy Options
Data in an Azure Storage account can be replicated in different regions. It offers two options for how data is replicated,
Locally redundant storage (LRS) copies your data synchronously three times within a single physical location in the primary region. LRS is the least expensive replication option but is not recommended for applications requiring high availability.
Geo-redundant storage (GRS) copies your data synchronously three times within a single physical location in the primary region using LRS. It then copies your data asynchronously to a single physical location in the secondary region. Within the secondary region, your data is copied synchronously three times using LRS.
Storage account endpoints
As a storage account provides a unique namespace in Azure for your data. Every object that is stored in Azure Storage has an address that includes your unique account name. The combination of the account name and the Azure Storage service endpoint forms the endpoints for your storage account.
for e.g. endpoint of an account which we are going to create.
| Storage service |
Endpoint |
| Blob storage |
https://itma63110.blob.core.windows.net/ |
Steps 1
Create a storage account in Azure, log in to the Azure portal, and search for a “storage account” in the marketplace to create a new resource.
Step 2
Choose your subscription and enter the following details, enter the below information and click next.
Step 3
Click next with default values or change according to requirement.
Step 4
Click next with default values or change according to requirement.
Step 5
Click next with default values or change according to requirement.
Step 6
Click "Review+Create" with default values or change according to requirement.
Step 7
Step 8
Wait for some time to complete the deployment. usually, it takes 2-3 minutes.
Step 9
Go to resource and click on the container.
Step 10
Step 11
Enter
“terraform-state” as Name.
Step 12
The highlighted container will be created, go to the container.
Step 13
Upload a file to the blob container by click on the Upload button and then choose your file from the local file system and upload.
Step 14
The upload file will be shown in the portal.
Conclusion
We have successfully created a storage account "itma63110" in resource group "terraform_remotestate_rg" and stored a sample file "BlobStorageFile.txt" under blob storage in Azure from the local file system using Azure portal. It is very simple to create such a powerful service and use it as remote storage according to requirements.