Skip to main content

Amazon EKS

Amazon EKS (Elastic Kubernetes Service) by Amazon Web Services (AWS) is a managed Kubernetes service that simplifies running Kubernetes on AWS. You can bring EKS cluster and node group data from Amazon EKS into Brinqa to gain a unified view of your attack surface, thus strengthening your cybersecurity posture.

This document details the information you must provide for the connector to authenticate with Amazon EKS and how to obtain that information from Amazon. See create a data integration for step-by-step instructions on setting up the integration.

Required connection settings

When setting up a data integration, select Amazon EKS from the Connector dropdown. If you cannot find the connector in the dropdown, make sure that you have installed it first. You must provide the following information to authenticate Amazon EKS with Brinqa:

  • Access key ID and Secret access key: The access keys associated with the AWS account. The account must have the required read-only permissions for the Amazon EKS service. For additional information, see Create an IAM user for AWS access.

  • Default region: The AWS region for the connector. If not specified, the connector uses the AWS Default Region Provider Chain.

Create an IAM user for AWS access

For the Amazon EKS connector to interact with the AWS SDK and retrieve data, you must provide specific AWS credentials and permissions. To create an IAM user, follow these steps:

  1. Log in to your organization's AWS Management Console as an administrator.

  2. Navigate to the Identity and Access Management (IAM) dashboard.

  3. From the navigation pane under Access management, click Users, and then click Create user.

  4. Provide a User name, leave the Provide user access to AWS Management Console option unchecked, and then click Next.

  5. Click the Attach policies directly option and then click Create policy.

  6. Click the JSON tab and paste the following minimum required policy:

    {
    "Version": "2012-10-17",
    "Statement": [
    {
    "Effect": "Allow",
    "Action": [
    "eks:ListClusters",
    "eks:DescribeCluster",
    "eks:ListNodegroups",
    "eks:DescribeNodegroup"
    ],
    "Resource": "*"
    }
    ]
    }
  7. Click Next, provide a name for the policy, and then click Create policy.

  8. Back on the Add permissions page, search for and select the policy you just created, and then click Next.

  9. Click Create user.

Obtain access keys

After you have created an IAM user, generate the access keys that are required for the connector. To do so, follow these steps:

  1. Navigate to the IAM dashboard.

  2. From the navigation pane under Access management, click Users.

  3. Choose the IAM user you created in the earlier steps.

  4. Click the Security credentials tab and then click Create access key.

  5. Select the Application running outside AWS use case and then click Next.

  6. Provide a description and then click Create access key.

    The access key ID and secret access key display. The secret access key is shown only once and cannot be retrieved again, so copy the key and save it to a secure location.

note

If you do not have the permissions to create access keys, contact your AWS administrator. For additional information, see AWS documentation.

The connector authenticates using the AWS SDK's credential resolution chain. If an assume-role ARN is configured, the connector assumes that IAM role using the provided credentials. Otherwise, it uses the provided access keys directly, falling back to the AWS Default Credential Provider Chain (environment variables, ~/.aws/credentials, or EC2 instance metadata).

Additional settings

The Amazon EKS connector contains additional options for specific configuration:

  • Assume role ARN: ARN of an IAM role to assume. Comma-separated to assume multiple roles in the same sync.
  • Session duration: Assume-role session duration in seconds. The default setting is 3600.
  • Page size: The maximum number of records to get per API request. The default setting is 100. It is not recommended to go over 100.
  • Parallel requests: The maximum number of parallel API requests. The default setting is 8.
  • Maximum retries: The maximum number of times that the integration attempts to connect to the Amazon EKS API before giving up and reporting a failure. The default setting is 10.

Types of data to retrieve

The Amazon EKS connector can retrieve the following types of data from the Amazon EKS API:

Table 1: Data retrieved from Amazon EKS

Connector ObjectRequiredMaps to Data Model
EksClusterYesCloud Resource
EksNodegroupYesCloud Resource
info

The Amazon EKS connector does not currently support operation options for the types of data it retrieves.

For detailed steps on how to view the data retrieved from Amazon EKS in the Brinqa Platform, see How to view your data.

Attribute mappings

Expand the sections below to view the mappings between the source and the Brinqa data model attributes.

EksCluster

Table 2: EksCluster attribute mappings

Source Field NameSDM Attribute
cluster.arnARN
cluster.arnUID
cluster.createdAtFIRST_SEEN
cluster.endpointENDPOINT
cluster.nameCLUSTER_NAME
cluster.name (fallback: ARN)NAME
cluster.platformVersionPLATFORM_VERSION
cluster.roleArnCLUSTER_ROLE_ARN
cluster.statusAsString()SOURCE_STATUS
cluster.tagsTAGS
cluster.versionVERSION
Generated (derived: true when public access enabled AND CIDRs contain 0.0.0.0/0)PUBLIC_OPEN_TO_INTERNET
Generated (set to "AWS")CLOUD_PROVIDER
Generated (sync capture timestamp)LAST_CAPTURED
identity.oidc.issuerOIDC_ISSUER
resourcesVpcConfig.clusterSecurityGroupIdCLUSTER_SECURITY_GROUP_ID
resourcesVpcConfig.endpointPrivateAccessENDPOINT_PRIVATE_ACCESS
resourcesVpcConfig.endpointPublicAccessENDPOINT_PUBLIC_ACCESS
resourcesVpcConfig.publicAccessCidrsPUBLIC_ACCESS_CIDRS
resourcesVpcConfig.securityGroupIdsSECURITY_GROUP_IDS
resourcesVpcConfig.subnetIdsSUBNET_IDS
resourcesVpcConfig.vpcIdVPC_ID
sync regionREGION
EksNodegroup

Table 3: EksNodegroup attribute mappings

Source Field NameSDM Attribute
Generated (set to "AWS")CLOUD_PROVIDER
Generated (sync capture timestamp)LAST_CAPTURED
nodegroup.amiTypeAsString()AMI_TYPE
nodegroup.capacityTypeAsString()CAPACITY_TYPE
nodegroup.clusterNameCLUSTER_NAME
nodegroup.createdAtFIRST_SEEN
nodegroup.diskSizeDISK_SIZE_GIB
nodegroup.instanceTypesINSTANCE_TYPES
nodegroup.modifiedAtSOURCE_LAST_MODIFIED
nodegroup.nodegroupArnNODEGROUP_ARN
nodegroup.nodegroupArnUID
nodegroup.nodegroupNameNODEGROUP_NAME
nodegroup.nodegroupName (fallback: ARN)NAME
nodegroup.nodeRoleNODE_ROLE_ARN
nodegroup.releaseVersionRELEASE_VERSION
nodegroup.scalingConfig.desiredSizeSCALING_DESIRED
nodegroup.scalingConfig.maxSizeSCALING_MAX
nodegroup.scalingConfig.minSizeSCALING_MIN
nodegroup.statusAsString()SOURCE_STATUS
nodegroup.subnetsSUBNET_IDS
nodegroup.tagsTAGS
nodegroup.versionVERSION
sync regionREGION

APIs

The Amazon EKS connector uses the Amazon EKS API. Specifically, it uses the following endpoints:

Table 4: Amazon EKS API endpoints

Connector ObjectAPI Endpoint
EksClustereks:ListClusters
eks:DescribeCluster
EksNodegroupeks:ListClusters
eks:ListNodegroups
eks:DescribeNodegroup

Changelog

The Amazon EKS connector has undergone the following changes:

note

This connector is part of a bundled release with other connectors from the same vendor. If a version shows "No change", it means that the connector version was updated for consistency as part of the bundle, but no functional changes were made to this specific connector. You can update to or skip this version without affecting your existing configuration.

Table 5: Amazon EKS connector changelog

VersionDescriptionDate Published
3.1.0Initial Integration+ release.June 1st, 2026