Geek asks and answers

How to protect azure spots

I am using azure blab storage service for windows. I want to protect my drops from public access (except for my users). For this, I used a shared signature (SAS), and it works fine. But my problem is that I have a Container that contains a blob in the directory structure, for example:

  https://xxxxxxx.blob.core.windows.net/myContainer/directory1/blob1
  https://xxxxxxx.blob.core.windows.net/myContainer/directory1/blob2
  https://xxxxxxx.blob.core.windows.net/myContainer/directory1/blob3
  https://xxxxxxx.blob.core.windows.net/myContainer/directory1/blob4
  https://xxxxxxx.blob.core.windows.net/myContainer/directory1/blob5

  https://xxxxxxx.blob.core.windows.net/myContainer/directory2/blob1       
  https://xxxxxxx.blob.core.windows.net/myContainer/directory2/blob2      
  https://xxxxxxx.blob.core.windows.net/myContainer/directory2/blob3      
  https://xxxxxxx.blob.core.windows.net/myContainer/directory2/blob4      
  https://xxxxxxx.blob.core.windows.net/myContainer/directory2/blob5

  and so on...

Now my requirement is that I want to provide open access to all blocks in myContainer under directory2, but not to the blocks under directory1, I want all drops in directory1 to be private. How can I achieve this?

+5
source share
3 answers

You can create two containers.

One closed container with SAS at the container level and one shared container

  https://xxxxxxx.blob.core.windows.net/private/blob1
  https://xxxxxxx.blob.core.windows.net/private/blob2
  https://xxxxxxx.blob.core.windows.net/private/blob3
  https://xxxxxxx.blob.core.windows.net/private/blob4
  https://xxxxxxx.blob.core.windows.net/private/blob5

  https://xxxxxxx.blob.core.windows.net/public/blob1       
  https://xxxxxxx.blob.core.windows.net/public/blob2      
  https://xxxxxxx.blob.core.windows.net/public/blob3      
  https://xxxxxxx.blob.core.windows.net/public/blob4      
  https://xxxxxxx.blob.core.windows.net/public/blob5
+2

Azure blob . "", , /, . , .

+3

You can only set permissions at the container level, so you have two options.

Preferred option) Create an additional open container and move your drops. Worse option) Create a seemingly endless valid sas link for all of your files.

+1
source

More articles:


All Articles