AWS resilience-hub: Note on private EKS cluster discovery without PrivateLink
Summary
Adds a note that next-gen Resilience Hub supports public, private, and CIDR-restricted EKS clusters, and that a cluster with endpointPublicAccess=false needs no VPC endpoint, PrivateLink, peering, or VPN and no network/security-baseline changes.
Security assessment
The note documents network-exposure posture for EKS clusters (endpointPublicAccess, PrivateLink, VPN) and reassures users their security baseline need not change, which is security-relevant configuration guidance rather than a fix for a specific weakness.
Evidence
+the next generation of Resilience Hub supports public, private, and CIDR-restricted Amazon EKS clusters. A cluster with `endpointPublicAccess=false` requires no VPC endpoint, AWS PrivateLink, peering, or VPN to be discovered. You do not need to change your cluster's network configuration or security baseline.
Diff
diff --git a/resilience-hub/latest/userguide/next-gen-add-input-source.md b/resilience-hub/latest/userguide/next-gen-add-input-source.md index 212ebaf..7b7cc90 100644 --- a//resilience-hub/latest/userguide/next-gen-add-input-source.md +++ b//resilience-hub/latest/userguide/next-gen-add-input-source.md @@ -26,0 +27,4 @@ +###### Note + +the next generation of Resilience Hub supports public, private, and CIDR-restricted Amazon EKS clusters. A cluster with `endpointPublicAccess=false` requires no VPC endpoint, AWS PrivateLink, peering, or VPN to be discovered. You do not need to change your cluster's network configuration or security baseline. +