Optimising Global Content Delivery: Ensuring Low Latency for Expanding Worldwide Demand
Tags: lowlatency, cloudcomputing, worldwide
Published: 2024-05-27 05:44:12

**Create a storage account to support the public website.**

**In the portal, select storage accounts**

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/4ywprcvbnuaoi9sjiucp.png)

**Select "+ Create"**

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/iahds4e0vt4ia2gq3rxh.png)

**Create new resource group and select "OK"**

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/9efnai15ry7dkzc4cnoc.png)

**Name storage account**

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/2571pic54elzyfkan9hd.png)

**Select "Review and Create"**

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/p3wkyqihaivnv8g501yc.png)

**Select "Create"**

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/2re6gqy2pngtzwi0w9a3.png)

Select Go to Resourcce

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/3bxt0n3cwrhusfr2ie2m.png)


**This storage requires high availability if there’s a regional outage. Additionally, enable read access to the secondary region,**

**In the Data management section**

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/tq6u403pvc8vt6nn73kv.png)

**Select Redundancy**

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/b4wjqmyj4e31rk8m31of.png)

**Select Read-access geo-redundant storage**

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/59sj16klb46xux2ag1zn.png)

**Review primary and secondary location**

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/qy5tj2608jefgce9sfi0.png)


**Information on the public website should be accessible without requiring customers to login.**

**In the settings section**

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/vmdybw8c9vhyq49v5ygp.png)

**Ensure Allow Blob anonymous access is Enabled**

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/9iivm6d49941wby9oan4.png)

**Save your changes**

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/7z9451r8umsg076ada5r.png)

**Create a blob storage container with anonymous read access**
**The public website has various images and documents. Create a blob storage container for the content**

**In your storage account, select Data storage and select Containers blade**

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/g0gmp4e1h5k5w1p32mak.png)

**Select "+ Container"**

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/39tsomduml4zh69z650t.png)

**Name the container**

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/3sz9382ywijmlcrg014e.png)


Select "Create"

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/3lol73dsw5i86f0879ca.png)
**
Customers should be able to view the images without being authenticated. Configure anonymous read access for the public container blobs**

**Select the public container**

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/z0f10xzsu1vwj56olr4f.png)

**Select change access level**

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/o8fym12uv54x1rioxfpp.png)

**Ensure public access level is Blob**

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/d1swma703fjzgw6yy1lz.png)

**Select "OK"**

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/ji9s0t2p4kyrjnqqfpd6.png)

**Practice uploading files and testing access
For testing, upload a file to the public container. The type of file doesn’t matter**

**Select "Upload" from the Container**

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/od7fxqiqdl0txyoh1ft1.png)

**Upload file**

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/jvrbkbof4hhl95ssd9jj.png)

**Copy URL annd paste in a new browser tab**

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/ko0ia0llewvpzctza58e.png)

**File should display**

**Configure soft delete**
It’s important that the website documents can be restored if they’re deleted

**Go to the overview blade of the storage account**

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/s1z2924sc5s14h8xc1rl.png)

**On the properties page, loacte blob service section**

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/555ymvf81od3uvu9q53w.png)


**Select the Blob soft delete setting**

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/rhphkdozqr4f5yvs1z5v.png)

**Ensure the Enable soft delete for blobs is checked.**

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/o124yjgikyvlfluzhie5.png)


**Change the Keep deleted blobs for (in days setting is 21.**

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/vqfje5zweskkgkzfadef.png)


**Don’t forget to Save your changes.**

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/5whmsp4uo9mbb4jugj20.png)

**If something gets deleted, you need to practice using soft delete to restore the files.**

**Navigate to your container where you uploaded a file.
Select the file you uploaded and then select Delete.**

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/pfzwtilha205ykh05jbn.png)


**Select OK to confirm deleting the file.**

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/kluwvckz58p6618nnree.png)


**On the container Overview page, toggle the slider Show deleted blobs. This toggle is to the right of the search box.
Select your deleted file, and use the ellipses on the far right, to Undelete the file.**

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/mnif3wffk7ytjyvrr2ha.png)


**Refresh the container and confirm the file has been restored.**

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/0ns3ruar0zhbmp0skzm8.png)

**Configure blob versioning**

**It’s important to keep track of the different website product document versions. **

**Go to the Overview blade of the storage account.**

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/xzpqjqhhmkliuhbngzkp.png)


**In the Properties section, locate the Blob service section.
Select the Versioning setting.**

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/nrt3mxkb7u72n9vqgn72.png)


**Ensure the Enable versioning for blobs checkbox is checked.**

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/mhick5i0foa0k4grqx16.png)


**Notice your options to keep all versions or delete versions after.
Don’t forget to Save your changes.**

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/ohyqum3gd3ek8sapv933.png)


As you have time experiment with restoring previous blob versions.
Upload another version of your container file. This overwrites your existing file.
Your previous file version is listed on Show deleted blobs page.