cloud:azure
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| cloud:azure [2024/04/27 16:11] – skipidar | cloud:azure [2024/07/22 20:15] (current) – [IAM and Role Based Access Control] skipidar | ||
|---|---|---|---|
| Line 22: | Line 22: | ||
| - | ==== Azure function ==== | ||
| - | === Azure functions in Azure Portal === | ||
| - | |||
| - | The runtime | ||
| - | {{https:// | ||
| - | |||
| - | |||
| - | The trigger and code. | ||
| - | |||
| - | Only available after uploading the code into the function, via | ||
| - | |||
| - | '' | ||
| - | |||
| - | which uploads the '' | ||
| - | from where it automatically is executed by the azure_function. | ||
| - | |||
| - | {{https:// | ||
| - | {{https:// | ||
| - | |||
| - | Here the function '' | ||
| - | |||
| - | {{https:// | ||
| - | |||
| - | The Function URL | ||
| - | {{https:// | ||
| - | |||
| - | The URL response | ||
| - | {{https:// | ||
| - | |||
| - | |||
| - | === Limitations of Azure functions === | ||
| - | |||
| - | |||
| - | * Azure functions - are NOT only serverless. | ||
| - | * You can choose a premium subscription and deploy your **Azure function** | ||
| - | * You CAN'T use a serverless function - in a private network | ||
| - | * You **CAN' | ||
| - | * http_trigger | ||
| - | * Blob trigger | ||
| - | * CosmosDB trigger | ||
| - | * EventHub trigger | ||
| - | * Queue trigger | ||
| - | * ServiceBus Queue trigger | ||
| - | * ServiceBus Topic trigger | ||
| - | * Timer Trigger | ||
| - | |||
| - | === Serverless Azure functions === | ||
| - | |||
| - | https:// | ||
| - | |||
| - | |||
| - | |||
| - | === Python linux functions === | ||
| - | |||
| - | https:// | ||
| - | |||
| - | |||
| - | Run like https:// | ||
| - | |||
| - | <sxh shell> | ||
| - | |||
| - | func start | ||
| - | |||
| - | </ | ||
| - | |||
| - | IN general read about developing locally: | ||
| - | https:// | ||
| ==== Azure Messaging services ==== | ==== Azure Messaging services ==== | ||
| Line 177: | Line 110: | ||
| + | |||
| + | ==== Azure API Management ==== | ||
| + | |||
| + | |||
| + | === Policies === | ||
| + | |||
| + | * Intro https:// | ||
| + | * Example https:// | ||
| + | |||
| + | |||
| + | === Evaluation order === | ||
| + | |||
| + | Policies are **executed sequentially** based on their placement within the policy configuration. | ||
| ==== Network ==== | ==== Network ==== | ||
| Line 194: | Line 140: | ||
| https:// | https:// | ||
| {{https:// | {{https:// | ||
| + | |||
| + | |||
| + | |||
| + | ==== Azure Data Ops ==== | ||
| + | |||
| + | Data Management Landing Zone: | ||
| + | |||
| + | {{https:// | ||
| + | |||
| + | Source: | ||
| + | https:// | ||
| + | |||
| + | |||
| + | |||
| + | 2) Data Landing Zone: | ||
| + | |||
| + | {{https:// | ||
| + | |||
| + | Source: | ||
| + | https:// | ||
| + | |||
| + | |||
| + | |||
| + | ==== IAM and Role Based Access Control ==== | ||
| + | |||
| + | see | ||
| + | https:// | ||
| + | |||
| + | {{https:// | ||
| + | |||
| + | |||
| + | Azure Custom Roles: | ||
| + | |||
| + | * https:// | ||
| + | |||
| + | IAM and Role Based Access Control | ||
| + | |||
| + | <sxh java> | ||
| + | { | ||
| + | " | ||
| + | "/" | ||
| + | ], | ||
| + | " | ||
| + | " | ||
| + | " | ||
| + | " | ||
| + | { | ||
| + | " | ||
| + | " | ||
| + | " | ||
| + | " | ||
| + | ], | ||
| + | " | ||
| + | " | ||
| + | " | ||
| + | ], | ||
| + | " | ||
| + | } | ||
| + | ], | ||
| + | " | ||
| + | " | ||
| + | " | ||
| + | } | ||
| + | </ | ||
| + | |||
| + | |||
| + | Custom role, which allows to assign roles to Azure API Managers. | ||
| + | <sxh java> | ||
| + | { | ||
| + | " | ||
| + | " | ||
| + | " | ||
| + | " | ||
| + | " | ||
| + | " | ||
| + | ], | ||
| + | " | ||
| + | " | ||
| + | " | ||
| + | " | ||
| + | "/ | ||
| + | ] | ||
| + | } | ||
| + | </ | ||
| + | |||
cloud/azure.1714234276.txt.gz · Last modified: by skipidar
