-
Notifications
You must be signed in to change notification settings - Fork 988
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Patch ESLZ ARM #727
Patch ESLZ ARM #727
Conversation
Fix value for sqlEncryptionPolicyAssignment variable
I don't believe there are any specific updates needed on the "What's new" page as these are all covered under the existing descriptions, but please let me know if you think it needs an addition. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All looks good to me @krowlandson!
Just a couple of questions/notes:
- Did you also change the Azure Backup Policy Assignment variable as the
azBackupIdentityPolicyAssignment
variable was never used? - You dont need to update the RIs in the
docs/reference/xxxx/
folders now for Adventure Works, Contoso, WingTip & Trey separately anymore; only the files ineslzArm/
👍
@@ -20173,7 +20173,7 @@ | |||
"Disabled" | |||
], | |||
"metadata": { | |||
"displayName": "Cognitive Services accounts should enable data encryption with a customer-managed key (CMK)", | |||
"displayName": "Cognitive Services accounts should enable data encryption with a customer-managed key (CMK)", | |||
"description": "Customer-managed keys (CMK) are commonly required to meet regulatory compliance standards. CMKs enable the data stored in Cognitive Services to be encrypted with an Azure Key Vault key created and owned by you. You have full control and responsibility for the key lifecycle, including rotation and management. Learn more about CMK encryption at https://aka.ms/cosmosdb-cmk." | |||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We are no longer using this template.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any harm in this fix?
@@ -20173,7 +20173,7 @@ | |||
"Disabled" | |||
], | |||
"metadata": { | |||
"displayName": "Cognitive Services accounts should enable data encryption with a customer-managed key (CMK)", | |||
"displayName": "Cognitive Services accounts should enable data encryption with a customer-managed key (CMK)", | |||
"description": "Customer-managed keys (CMK) are commonly required to meet regulatory compliance standards. CMKs enable the data stored in Cognitive Services to be encrypted with an Azure Key Vault key created and owned by you. You have full control and responsibility for the key lifecycle, including rotation and management. Learn more about CMK encryption at https://aka.ms/cosmosdb-cmk." | |||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We are no longer using this template.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any harm in this fix?
@@ -20173,7 +20173,7 @@ | |||
"Disabled" | |||
], | |||
"metadata": { | |||
"displayName": "Cognitive Services accounts should enable data encryption with a customer-managed key (CMK)", | |||
"displayName": "Cognitive Services accounts should enable data encryption with a customer-managed key (CMK)", | |||
"description": "Customer-managed keys (CMK) are commonly required to meet regulatory compliance standards. CMKs enable the data stored in Cognitive Services to be encrypted with an Azure Key Vault key created and owned by you. You have full control and responsibility for the key lifecycle, including rotation and management. Learn more about CMK encryption at https://aka.ms/cosmosdb-cmk." | |||
} | |||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We are no longer using this template.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any harm in this fix?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No harm, but we are planning to delete these files so I don't see any reason to why we need to update them
@@ -607,8 +607,7 @@ | |||
"ascConfigPolicyInitiative": "[uri(deployment().properties.templateLink.uri, 'managementGroupTemplates/policyAssignments/DINE-ASCConfigPolicyAssignment.json')]", | |||
"azVmMonitorPolicyAssignment": "[uri(deployment().properties.templateLink.uri, 'managementGroupTemplates/policyAssignments/DINE-VMMonitoringPolicyAssignment.json')]", | |||
"azVmssMonitorPolicyAssignment": "[uri(deployment().properties.templateLink.uri, 'managementGroupTemplates/policyAssignments/DINE-VMSSMonitoringPolicyAssignment.json')]", | |||
"azBackupLzPolicyAssignment": "[uri(deployment().properties.templateLink.uri, 'managementGroupTemplates/policyAssignments/DINE-VMBackupPolicyAssignment.json')]", | |||
"azBackupIdentityPolicyAssignment": "[uri(deployment().properties.templateLink.uri, 'managementGroupTemplates/policyAssignments/DINE-VMBackupPolicyAssignment.json')]", | |||
"azVmBackupPolicyAssignment": "[uri(deployment().properties.templateLink.uri, 'managementGroupTemplates/policyAssignments/DINE-VMBackupPolicyAssignment.json')]", | |||
"azPolicyForAksPolicyAssignment": "[uri(deployment().properties.templateLink.uri, 'managementGroupTemplates/policyAssignments/DINE-AksPolicyPolicyAssignment.json')]", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If identity subscription is enabled, we also recommend to assign VM Backup policy to the identity management group, hence we need a deterministic guid for the subsequent role assignment for that policy, so we need both these variables.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As azBackupIdentityPolicyAssignment
isn't referenced anywhere else in the repository and the values are the same, how does this make a difference when an identity subscription is enabled?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is it's own (optional) deployment name, and we cannot have duplicated resource name in the same ARM template.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just my 2 cents here 😃
I have tested a deployment from @krowlandson's branch for this PR and it works 👍
Including the Backup policies involved also:
From my initial review, and re-review today, the ARM deployment names are unchanged just the reference to the deployment template URI and a de-duplication of a variable that holds this (which from looking at the current templates, it looks like the azBackupIdentityPolicyAssignment
variable is not referenced anywhere as the azBackupLzPolicyAssignment
is used for all nested deployments which do the assignments. Also as the conditionals are not based on these and other parameters/variables from the portal UX experience then I think this is all good 👍
Overview/Summary
Minor updates to the ESLZ ARM templates to fix a few issues observed during development of the Terraform Module.
This PR fixes/adds/changes/removes
Deny-Priv-Esc-AKS
-->Deny-Priv-Escalation-AKS
Deny-Privileged-AKS
-->Deny-Priv-Containers-AKS
description
forDeny-Subnet-Without-Nsg
Policy Assignmentmetadata.displayName
forCognitiveServicesCMKEffect
parameter inEnforce-Encryption-CMK
Policy Set Definition to remove unusual whitespace character (discovered during testing, as per the below image)Breaking Changes
n/a
Testing Evidence
These changes replicate values set in a working deployment using the Terraform version of ES.
For the update on
Enforce-Encryption-CMK
, please see the below evidence of how this change effects the resource in question:As part of this Pull Request I have
main
branch/docs/wiki/whats-new.md
)