EKS clusters that the connector will be allowed toaccess (e.g. arn:aws:eks:{region}:{account}:cluster/* represents all the EKS

clusters available in the target AWS region).

eks:ListClusters

eks:DescribeCluster

In addition to the above permissions, if the credentials are not associated with

the same IAM user or role that created the EKS cluster, the IAM principal must

be manually added to the EKS cluster's aws-auth ConfigMap, otherwise the

Kubernetes client will not be allowed to access the cluster's resources. This

makes it more challenging to use the AWS Implicit and AWS Federation Token

authentication methods for this resource. For more information, see this

documentation.

If set, the resource name must identify an EKS cluster using one of the

following formats:

EKS cluster name (canonical resource name): {cluster-name}

EKS cluster ARN: arn:aws:eks:{region}:{account}:cluster/{cluster-name}

EKS cluster names are region scoped. The connector can only be used to access

EKS clusters in the AWS region that it is configured to use.

────────────────────────────────────────────────────────────────────────────────

zenml service-connector describe-type aws --auth-method secret-key

Example Command Output

╔══════════════════════════════════════════════════════════════════════════════╗

║                 🔒 AWS Secret Key (auth method: secret-key)                  ║

╚══════════════════════════════════════════════════════════════════════════════╝

Supports issuing temporary credentials: False

Long-lived AWS credentials consisting of an AWS access key ID and secret access

key associated with an AWS IAM user or AWS account root user (not recommended).

This method is preferred during development and testing due to its simplicity

and ease of use. It is not recommended as a direct authentication method for

production use cases because the clients have direct access to long-lived

credentials and are granted the full set of permissions of the IAM user or AWS