---
title: Getting Started with Datadog
description: Datadog, the leading service for cloud-scale monitoring.
breadcrumbs: Docs > Infrastructure > Datadog Resource Catalog
---

# aws_eks_access_entry{% #aws_eks_access_entry %}

## `access_entry_arn`{% #access_entry_arn %}

**Type**: `STRING`**Provider name**: `accessEntryArn`**Description**: The ARN of the access entry.

## `account_id`{% #account_id %}

**Type**: `STRING`

## `cluster_name`{% #cluster_name %}

**Type**: `STRING`**Provider name**: `clusterName`**Description**: The name of your cluster.

## `created_at`{% #created_at %}

**Type**: `TIMESTAMP`**Provider name**: `createdAt`**Description**: The Unix epoch timestamp at object creation.

## `kubernetes_groups`{% #kubernetes_groups %}

**Type**: `UNORDERED_LIST_STRING`**Provider name**: `kubernetesGroups`**Description**: A `name` that you've specified in a Kubernetes `RoleBinding` or `ClusterRoleBinding` object so that Kubernetes authorizes the `principalARN` access to cluster objects.

## `modified_at`{% #modified_at %}

**Type**: `TIMESTAMP`**Provider name**: `modifiedAt`**Description**: The Unix epoch timestamp for the last modification to the object.

## `principal_arn`{% #principal_arn %}

**Type**: `STRING`**Provider name**: `principalArn`**Description**: The ARN of the IAM principal for the access entry. If you ever delete the IAM principal with this ARN, the access entry isn't automatically deleted. We recommend that you delete the access entry with an ARN for an IAM principal that you delete. If you don't delete the access entry and ever recreate the IAM principal, even if it has the same ARN, the access entry won't work. This is because even though the ARN is the same for the recreated IAM principal, the `roleID` or `userID` (you can see this with the Security Token Service `GetCallerIdentity` API) is different for the recreated IAM principal than it was for the original IAM principal. Even though you don't see the IAM principal's `roleID` or `userID` for an access entry, Amazon EKS stores it with the access entry.

## `tags`{% #tags %}

**Type**: `UNORDERED_LIST_STRING`

## `type`{% #type %}

**Type**: `STRING`**Provider name**: `type`**Description**: The type of the access entry.

## `username`{% #username %}

**Type**: `STRING`**Provider name**: `username`**Description**: The `name` of a user that can authenticate to your cluster.