eks.access-entries.getOne access entry and its access policies
GET /eks/api/clusters/{cluster}/access-entries/{id}IAM eks:DescribeAccessEntryRead
Request syntax
GET /eks/api/clusters/{cluster}/access-entries/{id}Path parameters
clusterRequiredstring
Constraints: /^(ewk-[0-9a-f]{12}|[a-z]([a-z0-9-]{0,38}[a-z0-9])?)$/
idRequiredstring
Response
200 with the access entry: id, principalType, principalId, principalName, username, kubernetesGroups, policies (policy, namespaces, scope: cluster | namespaces), createdAt. 404 for an unknown cluster or entry (403 without eks:DescribeAccessEntry on it, checked before the entry is looked up).
A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.
Errors
- 400The request does not pass the schema above. The body is { "error": …, "issues": […] }, one issue per field.
- 401No credentials, or an access key that is unknown, revoked or expired.
- 403The caller's policies do not allow eks:DescribeAccessEntry on this resource. The body names the action and the resource, and the refusal is recorded in the audit log.
- 404The resource does not exist in your organization.
Examples
The required parameters only, with example values. Replace id and the other placeholders with your own.
dcloud eks access-entries get cluster idcurl -X GET "https://console.platform-development.deutschecloud.app/eks/api/clusters/cluster/access-entries/id" \
-H "Authorization: EWS-ACCESS-KEY $ACCESS_KEY"Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_eks_access-entries_get.