AWS prescriptive-guidance documentation change
Summary
Updated author attribution and reformatted a note about cert-manager's namespace and cluster role usage.
Security assessment
The change restructures existing documentation about cert-manager's security configuration but does not introduce new security features or address a specific security issue. The encryption setup is security-related by nature, but the change itself is purely editorial.
Diff
diff --git a/prescriptive-guidance/latest/patterns/set-up-end-to-end-encryption-for-applications-on-amazon-eks-using-cert-manager-and-let-s-encrypt.md b/prescriptive-guidance/latest/patterns/set-up-end-to-end-encryption-for-applications-on-amazon-eks-using-cert-manager-and-let-s-encrypt.md index ae7fc5f6c..8c5aedf1a 100644 --- a//prescriptive-guidance/latest/patterns/set-up-end-to-end-encryption-for-applications-on-amazon-eks-using-cert-manager-and-let-s-encrypt.md +++ b//prescriptive-guidance/latest/patterns/set-up-end-to-end-encryption-for-applications-on-amazon-eks-using-cert-manager-and-let-s-encrypt.md @@ -9 +9 @@ SummaryPrerequisites and limitationsArchitectureToolsEpicsRelated resources - _Created by Mahendra Revanasiddappa (AWS) and Vasanth Jeyaraj (AWS)_ + _Mahendra Revanasiddappa and Vasanth Jeyaraj, Amazon Web Services_ @@ -88,3 +88 @@ The diagram shows the following workflow: -###### Note - -Cert-manager runs in its own namespace. It uses a Kubernetes cluster role to provision certificates as secrets in specific namespaces. You can attach those namespaces to application pods and NGINX Ingress Controller. +Note: Cert-manager runs in its own namespace. It uses a Kubernetes cluster role to provision certificates as secrets in specific namespaces. You can attach those namespaces to application pods and NGINX Ingress Controller.