-
Notifications
You must be signed in to change notification settings - Fork 12
Description
Category
Documentation
Description
Normally the Invictus installation would expect a Service Principal that has contributor rights on a certain resource group.
However, some customers do not want this, and instead require more specificity in their roles to adhere to the principle of least privilige. Would be good to have some documentation on this to speed up installations at those customers.
Additional context
This is what I have so far at my client, maybe it could serve as a headstart.
Azure Event Hubs Data Owner
Azure Service Bus Data Owner
Container Apps ManagedEnvironments Contributor
Container Registry Contributor and Data Access Configuration Administrator
Container Registry Tasks Contributor
Custom invictus Deployment:
actions: "Microsoft.App/containerApps/write",
"Microsoft.App/containerApps/authConfigs/write",
"microsoft.app/jobs/start/action",
"microsoft.app/jobs/stop/action",
"microsoft.app/jobs/read",
"microsoft.app/jobs/write",
"microsoft.app/jobs/delete",
"microsoft.app/register/action",
"microsoft.app/managedenvironments/write",
"microsoft.app/managedenvironments/join/action",
"Microsoft.Authorization/locks/write",
"Microsoft.ManagedIdentity/userAssignedIdentities/assign/action",
"Microsoft.ManagedIdentity/userAssignedIdentities/write",
"Microsoft.OperationalInsights/workspaces/listKeys/action"
EventGrid Contributor
Key Vault Contributor
Key Vault Data Access Administrator
Logic App Contributor
Monitoring Contributor
Network Contributor
Role Based Access Control Administrator (Optionally scoped to specific roles it itself needs to assign).
Storage Account Contributor
Web Plan Contributor
Website Contributor
Cosmos DB Operator