EKS access policies should be scoped to dedicated namespaces instead of the default namespace

eks
Cette page n'est pas encore disponible en français, sa traduction est en cours.
Si vous avez des questions ou des retours sur notre projet de traduction actuel, n'hésitez pas à nous contacter.

Description

AWS EKS access policies should be scoped to dedicated namespaces that reflect intended team, application, or environment boundaries instead of the default namespace. Relying on the default namespace weakens administrative separation and makes namespace-scoped access control, resource governance, and network segmentation harder to apply consistently. This check evaluates EKS access policy associations and flags those that are cluster-wide or scoped to the default namespace.

Remediation

Associate EKS access policies to specific dedicated namespaces rather than the whole cluster or the default namespace, and migrate workloads into namespaces that align with namespace-scoped Roles, RoleBindings, quotas, limits, service accounts, and network policies. For guidance, see the EKS access policies documentation.

References