Skip to main content
Azure - Shared Access Signature (SAS) - Account key vs User Delegation

#cloud #azure

Hi All!

I would say Azure storage account is a long last service. Whatever the services overcome one another, azure storage stays active. For example, we can take a .NET web application which can be hosted in IIS of a Azure VM, App service with or without Docker, Function app for event based. Here based on requirements App service sometimes overcome VM and function app overcomes rest of others and so on.

When we use any of the cloud service, security is one of the main pillar need to consider. Here we are going to talk about Blob storage account access granting to customer or somebody else who requires it.

Consider a scenario that customer application place a file, it would be csv or JSON or XML what ever it may be but a single type. Let's take JSON here.

We need to allow some people to access that file. Here we have two questions as below

  1. Who are those some people whether Azure AD user or Non-Azure AD user?
  2. What permission we need to grant? so only granting Read permission is sufficient or should we grant some additional access as well?

For #2, If they want to only access / download, we can grant only Read and List permission is SAS. No need to grant Write, Delete, Create etc.,

The main purpose of this post is to discuss the question no.1

we have 2 types of signing method

  1. User Delegation
  2. Account Key

If the team or specific users who are part of Azure AD needs to access blob(s), we can go for user delegation.

If the team or specific users who are not part of Azure AD needs to access blob(s), we can go for Account Key.

The vital part of Account key SAS is, If any body rotate the key (Access Key), SAS may become invalid. We need to recreate the SAS to share with the people who already has previous one.

Account Key based SAS can be generated based on Key1 or Key2 as you can see in the below image,If you rotate key1, only key1 gets afftected.

Comments

Post a Comment

Popular posts from this blog

Azure Static Web Apps - Plan Comparison #cloud #azure Hi All! Azure Static web app is a good service when we have static web apps like javacript frameworks and libraries applictions (Ex: Angular, React, Svelte, Vue, Blazor). It also supports Python 3.10 based static web app as well as per the latest azure news. Other advantage of it is coupled with your Azure AD. so that your code can be directly pushed to azure static web app via either Azure DevOps or Github whenever code push occurs. At the time of azure static web app creation, it asks for deployment source as any one of the below. Based on the selection, it allows you to select the organization, project and repositories from the source. Azure DevOps - Azure AD connected Devops organizations will be listed out Github Other - For ex: If you want to deploy code from other organization. Below table will be helpful to choose the best pricing plan for your workload. Plan/Feature Free Standard ...
1 comment
Read more
Azure - Change custom lookback period for Azure Advisor VM/VMSS right-sizing recommendations #cloud #azure Hi All! Azure Advisor advises/recommeds us to optimize our cloud resources in various places like scaling, security, sizing, performace, cost etc., Now azure releases a new feature that changing lookback period for azure VM/VMSS to get right sizing. Let's consider a scenario that a company is running business and it has some workloads in either azure VM or VMSS. Some of the times VM's usage like CPU or memory is high. Due to this, application performace may be slower adnd user feels some bad experience. Company asks its azure admin to investigate it and when he/she viewd at azure advisor first, it recommends some solution based on last 7 days usage of VM. Here, Company needs the VM usage details biweekly or in someother pattern, not with the default 7 days. Here the new custom lookback period helps to achieve what the company wants. By this featur...
Post a Comment
Read more
Difference between failed() vs succeededorFailed() in Devops YAML Every organizations embrace Devops culture for CI & CD. Nowadays, everybody prefers YAML which is IaC (Infrastructure as Code) instead of classic UI editor. YAML consists main components as stages, jobs, steps, tasks.... etc., Based on the requirement, Devops engineers need to apply conditions on pipline between tasks or jobs or stages. what is condition? when I want to run a task or job based on some condition like only when my preferred another job failed or succeeded. Here I job1 and job2. I need to run job2 only if job1 fails. Let's see the difference between failed() and succeededorFailed() through the below image.
Post a Comment
Read more