Shared access signatures can be a great way to share files between microservices in a larger application, as well as making files available to end users for download or display in a webpage. Z%2FRHIX5Xcg0Mq2rqI3OlWTjEg2tYkboXr1P9ZUXDtkk%3D SAS Usage Guidelines Note that creating this signature is purely in-memory operation – as long as you have the Storage Account connection string, you can generate one without the target blob needing to exist, or needing access to the Storage Account REST API. This is calculated from the rest of the SAS URI, and requires the Storage Account connection string to calculate. Here I have highlighted just the signature only.
This is the query string appended to the blob’s URI: Here I have highlighted just the SAS Token portion of the SAS URI. This is a full URI that can be used to access a blob:
Here's my understanding of what the terms are: The terminology is confusing, as “SAS” on its own can be used to refer to the entire “SAS URI” or sometimes the “SAS Token”, or even just the “signature”. Azure Blob Storage provides the concept of “ shared access signatures”, which are a great way to grant time-limited access to read from (or write to) a specific blob in your container.
0 kommentar(er)
