Give someone access

Give an IAM user, group or role an access entry on a cluster with an access policy, change it, or remove it.

Last updated 18 November 2026View as Markdown

Replace my-cluster with your cluster's name or id, jane with the IAM user's name, and payments with a namespace. The person also needs eks:AccessKubernetesApi on the cluster in IAM to get a token; see Cluster access.

Prerequisites

  • Permission for eks:CreateAccessEntry on the cluster, and eks:AssociateAccessPolicy to give policies with it. The console always gives one policy, so it needs both.
  • To remove an entry, eks:DeleteAccessEntry; to add or remove a policy later, eks:AssociateAccessPolicy or eks:DisassociateAccessPolicy; to change the username or extra groups, eks:UpdateAccessEntry. The console enables Remove, Associate and a policy's Remove only with these on every cluster (eks:*).
  • In the console, also eks:DescribeCluster to open the cluster and eks:ListAccessEntries to see the entries.

Give access

  1. Open Kubernetes, open the cluster, then choose Access.
  2. Under Give access, choose the principal type (IAM user, group or role) and enter its name.
  3. Choose the access policy, and (except for ClusterAdmin) enter namespaces to limit it to, or leave them empty for the whole cluster.
  4. Choose Give access.

The entry appears under Access entries.

Optional fields: username (the Kubernetes username its tokens carry, seen as ews:<username>) and kubernetesGroups (up to 20 extra groups for your own RBAC). Change them later with dcloud eks access-entries update; tokens issued before keep the old name and groups until they expire.

Add or remove a policy

  1. On the Access tab, choose Policies on the entry's row.
  2. To add one, choose the policy, enter namespaces or leave them empty, and choose Associate. Associating a policy the entry already has replaces its namespaces.
  3. To remove one, choose Remove beside it.
  4. Choose Done.

Remove access

On the Access tab, choose Remove on the entry's row and confirm "Remove jane's access to my-cluster?", or run dcloud eks access-entries delete my-cluster entry-id. No new token is issued on the entry from then on; tokens already issued last until they expire (ten minutes).

Refusals

  • 404 "No IAM user named "jane"" (or group, or role), "Access entry not found", or "Access policy not found" when removing a policy the entry does not have.
  • 409 "The user "jane" already has an access entry on this cluster", or the access-entries quota is full.
Did this page help you?