6.SetUp Azure Key vault and RBAC permission
Setting up Azure Key Vault involves creating a Key Vault instance, managing access policies, and assigning RBAC (Role-Based Access Control) permissions. Here are the steps:
Step 1: Create an Azure Key Vault
Navigate to Azure Portal:
Go to Azure Portal.
Create Key Vault:
Click on "+ Create a resource."
Search for "Key Vault" and select it from the results.
Click "Create" and fill in the required information:
Subscription
Resource Group
Key Vault Name
Region
Pricing Tier
Review and Create:
Review your configuration and click "Review + create."
Click "Create" to deploy the Key Vault.
Step 2: Manage Access Policies
Navigate to Key Vault:
After deployment, go to your Key Vault resource.
Access Policies:
In the left menu, under "Settings," select "Access policies."
Add Access Policy:
Click on "Add Access Policy."
Configure the policy settings, including permissions (secrets, keys, certificates), and principal (users, applications, groups) that need access.
Save Access Policy:
Click "Add" to save the access policy.
Step 3: Assign RBAC Permissions
Navigate to Access Control (IAM):
In the left menu, under "Settings," select "Access control (IAM)."
Add Role Assignment:
Click on "+ Add" and select "Add role assignment."
Choose the role (e.g., Key Vault Contributor) and assign it to a user, group, or service principal.
Select the Key Vault resource.
Review and Add:
Review the role assignment and click "Add" to complete the process.
Important Considerations:
Key Vault Contributor Role:
The "Key Vault Contributor" role provides the necessary permissions to manage secrets, keys, and certificates in the Key Vault.
Custom Roles:
You can create custom roles with specific permissions if needed.
Access Policies vs. RBAC:
Access policies within Key Vault control data plane (read/write to secrets, keys, etc.), while RBAC controls management plane access.
Secret Versioning:
Be aware of secret versioning if you plan to rotate secrets.
Always follow the principle of least privilege when assigning permissions. Review and audit permissions regularly.