# Manage EKS clusters through an AWS Organization With Elastic Kubernetes Service (EKS) on AWS, EKS simplifies the management complexities of Kubernetes. This integration allows Apono to securely manage access to your AWS Elastic Kubernetes cluster by connecting to your AWS Organization using ECS. {% hint style="success" %} You can also [integrate directly with EKS](/docs/aws-environment/aws-integrations/integrate-with-eks.md) to manage cluster access without an AWS Organization integration. {% endhint %} *** ### Prerequisites
ItemDescription
Apono ConnectorThe Apono connector serves as the bridge between AWS and Apono.
Learn how to install a connector on ECS to manage EKS clusters.
EKS Access Entries

Connection between EKS permissions and an IAM identity

EKS access entries must be enabled for Apono to discover and manage EKS clusters. Access entries define how IAM principals are granted access to Kubernetes resources.

Learn how to set up access entries.

*** ### Integrate an AWS Organization with EKS resources

Integrating an AWS Organization

{% hint style="success" %} You can also use the steps below to integrate with Apono using Terraform. In step **10**, instead of clicking **Confirm**, follow the **Are you integrating with Apono using Terraform?** guidance. {% endhint %} Follow these steps to complete the integration: 1. On the [**Catalog**](https://app.apono.io/catalog?search=aws) tab, click **AWS**. The **Connect Integrations Group** page appears. 2. Under **Discovery**, click **Amazon Organization**. 3. Select the **EKS Cluster** resource type to sync with Apono. You can select other resource types as well. {% hint style="info" %} Apono automatically discovers and syncs all the instances in the environment. After syncing, you can manage access flows to these resources. {% endhint %} 4. Click **Next**. The **Apono connector** section expands. 5. From the dropdown menu, select a connector. Choosing a connector links Apono to all the services available on the account where the connector is located. {% hint style="success" %} If the desired connector is not listed, click **+ Add new connector** and follow the instructions to [install the connector to manage EKS clusters](broken://pages/SdCpxRGlRYJGPBp8uUS6). {% endhint %} 6. Click **Next**. The **Integration Config** section expands. 7. Define the **Integration Config** settings.
SettingDescription
Integration NameUnique, alphanumeric, user-friendly name used to identify this integration when constructing an access flow
RegionRegion in which the organization runs
AWS SSO RegionRegion for which your single sign-on is configured
SSO PortalSingle sign-on URL

This is required for Apono to generate a sign-in link for end users to use their granted access.
Management Account Role ARN(Optional) ARN (step 5) of the role to assume in the management account
Exclude Organization Unit IDs(Optional) Comma-separated list of organizational unit IDs to exclude

Example: ou-aaa1-1111,ou-bbb2-2222
Session Duration (in hours)(Optional) Length of time in hours that Apono’s assumed AWS role remains authenticated and authorized to access your EKS resources before the session expires
Exclude Account IDs(Optional) Comma-separated list of account IDs to exclude

Example: 7665544332211,7665544332222,766554433333333
8. Click **Next**. The **Get more with Apono** section expands. 9. Define the **Get more with Apono** settings.
SettingDescription
Custom Access Details(Optional) Instructions explaining how to access this integration's resources

Upon accessing an integration, a message with these instructions will be displayed to end users in the User Portal. The message may include up to 400 characters.

To view the message as it appears to end users, click Preview.
Integration Owner

(Optional) Fallback approver if no resource owner is found

Follow these steps to define one or several integration owners:

  1. From the Attribute dropdown menu, select User or Group under the relevant identity provider (IdP) platform.
  2. From the Value dropdown menu, select one or multiple users or groups.


NOTE: When Resource Owner is defined, an Integration Owner must be defined.

Resource Owner

(Optional) Group or role responsible for managing access approvals or rejections for the resource

Follow these steps to define one or several resource owners:

  1. Enter a Key name. This value is the name of the tag created in your cloud environment.
  2. From the Attribute dropdown menu, select an attribute under the IdP platform to which the key name is associated.

    Apono will use the value associated with the key (tag) to identify the resource owner. When you update the membership of the group or role in your IdP platform, this change is also reflected in Apono.


NOTE: When this setting is defined, an Integration Owner must also be defined.

10. Click **Confirm**.
đź’ˇAre you integrating with Apono using Terraform? If you want to integrate with Apono using Terraform, follow these steps instead of clicking **Confirm**: 1. At the top of the screen, click **View as Code**. A modal appears with the completed Terraform configuration code. 2. Click to copy the code. 3. Make any additional edits. 4. Deploy the code in your Terraform. Refer to [Integration Config Metadata](broken://spaces/qaP0ACE1sJSbll3NK7Yo/pages/EGSohwFf855FCTZVdK68) for more details about the schema definition.
Now that you have completed this integration, you can [create access flows](/docs/access-flows/access-flows.md) that grant permission to your AWS Organization’s EKS clusters. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.apono.io/docs/aws-environment/aws-integrations/integrate-an-aws-account-or-organization/manage-eks-clusters-through-an-aws-organization.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.