Security in Managed Kubernetes

Who may do what (IAM), what is recorded, how secrets are encrypted, and who can reach a cluster.

Last updated 18 November 2026View as Markdown

IAM actions

Every operation is checked against your IAM policies. A cluster's resource name is rn:ews:<region>:<org>:eks:cluster/<cluster id>; permission checks always use the id, also when you address the cluster by name. Node groups, access entries, add-ons and pod identity associations have resource names of their own under the cluster.

ActionAccessWhat it allows
eks:ListClustersReadList Kubernetes clusters
eks:DescribeClusterReadRead a cluster’s configuration, endpoint, version and status
eks:CreateClusterWriteCreate Kubernetes clusters
eks:UpdateClusterConfigWrite · destructiveChange a cluster’s settings, such as the networks allowed to reach its API endpoint or deletion protection
eks:UpdateClusterVersionWrite · destructiveUpgrade a cluster’s control plane to the next Kubernetes minor; its machines are replaced one at a time
eks:ListClusterSnapshotsReadList a cluster’s etcd snapshots: when, which revision, how large, verified, kind and expiry
eks:CreateClusterSnapshotWriteTake an etcd snapshot of a cluster now (at most one per 10 minutes)
eks:RestoreClusterWrite · destructiveRestore a cluster’s control plane from one of its etcd snapshots: every Kubernetes object returns to that point, the API is down while the control plane is rebuilt
eks:PostponeClusterUpgradeWritePostpone Deutsche Cloud’s control-plane upgrade of a cluster past its end of support, once, by 14 days
eks:DeleteClusterWrite · destructiveDelete clusters, their control plane, node groups and nodes
eks:ListNodegroupsReadList a cluster’s node groups
eks:DescribeNodegroupReadRead a node group’s configuration, size and nodes
eks:CreateNodegroupWriteAdd node groups (compute instances that join the cluster) to a cluster
eks:UpdateNodegroupConfigWrite · destructiveScale a node group or change its labels and taints; scaling down drains and deletes nodes
eks:UpdateNodegroupVersionWrite · destructiveUpgrade a node group to the cluster’s Kubernetes minor; its nodes are replaced one at a time, drained first
eks:DeleteNodegroupWrite · destructiveDelete node groups and their nodes
eks:ListAccessEntriesReadList who has an access entry on a cluster
eks:DescribeAccessEntryReadRead an access entry and the access policies associated with it
eks:CreateAccessEntryWriteGive an IAM user, group or role an entry on a cluster
eks:UpdateAccessEntryWrite · destructiveChange an access entry’s Kubernetes username or extra groups
eks:DeleteAccessEntryWrite · destructiveRemove an access entry, revoking that principal’s access to the cluster
eks:AssociateAccessPolicyWriteGrant an access entry an access policy (ClusterAdmin, Admin, Edit, View), cluster-wide or in namespaces
eks:DisassociateAccessPolicyWrite · destructiveRemove an access policy from an access entry
eks:AccessKubernetesApiWriteGet a short-lived token for a cluster’s Kubernetes API (what kubectl uses); the access entries decide what it may do
eks:ListPodIdentityAssociationsReadList which service accounts of a cluster act as which IAM roles
eks:CreatePodIdentityAssociationWriteLet pods running as a service account act as an IAM role (also needs iam:PassRole on the role)
eks:DeletePodIdentityAssociationWrite · destructiveStop a service account’s pods from getting the role’s credentials
eks:GetClusterAdminCredentialsWriteBreak glass: a one-hour cluster-admin client certificate for when Deutsche Cloud sign-in or RBAC is broken; every issuance is recorded
eks:DescribeAddonVersionsReadList the managed add-ons Deutsche Cloud offers, their versions and the Kubernetes versions each supports
eks:ListAddonsReadList a cluster’s add-ons, the system components included
eks:DescribeAddonReadRead an add-on’s version, options, status and health
eks:CreateAddonWriteInstall a managed add-on on a cluster (for the DNS add-ons: let it change records in the zones it lists)
eks:UpdateAddonWrite · destructiveChange an add-on’s version or options; its workloads are rolled
eks:DeleteAddonWrite · destructiveRemove an add-on’s workloads from a cluster (its CRDs and your resources of them stay)
eks:GetClusterLogsReadRead a cluster’s control-plane logs: the Kubernetes audit log, API server, authenticator, controller manager, scheduler

Generated from the service’s IAM descriptor. Sensitive reads hand over secret material or source code and are recorded in the audit log like writes; destructive writes delete, overwrite or revoke.

  • eks:AccessKubernetesApi issues a token, so it is a write. It is only half of getting in: the caller also needs an access entry (see Cluster access).
  • Handing a role to a node group or a pod identity association also needs iam:PassRole on that role.
  • Installing external-dns, or cert-manager with zones, also needs dns:ChangeRecords on every zone listed.
  • The cluster's own components (load balancers, volumes, DNS add-ons) are not IAM principals; Deutsche Cloud acts for them only on resources that belong to the cluster, or on the zones an add-on lists. Image pulls from your registry are the exception: they use the node group's IAM role.

Audit

Every write that reaches its permission check is recorded in the audit log, allowed or refused. A read is recorded only when it is refused. A request refused before its permission check, for example for an unknown cluster (404), records nothing. Changes to a cluster are also written to its Activity, with who made them: creation, settings, node groups, access entries and policies, pod identity associations, add-ons, upgrades, snapshots and restores, and every issuance of break-glass credentials.

Inside the cluster, the Kubernetes audit log is collected by default (see Read control-plane logs).

Encryption

  • Kubernetes Secrets are encrypted in etcd with KMS v2; the key-encryption key stays with Deutsche Cloud.
  • etcd snapshots are sealed with a key per snapshot under Deutsche Cloud's master key, and cannot be downloaded.
  • Volumes of the default StorageClass ews-volume-encrypted are opened with LUKS on the node; the key is released only to the node the volume is attached to.

Network exposure

  • The API endpoint answers on its public address to the networks you allow, inside the network, or both; see Set API endpoint access. Every request authenticates.
  • Nodes accept no inbound traffic from the internet until you add rules to the cluster's node security group; see What runs on your machines.
  • The control plane reaches kubelets through a tunnel the nodes open (Konnectivity).
Did this page help you?