Token or AWS Session Token authentication methods.Note that the discovered credentials inherit the full set of permissions of the local AWS client configuration, environment variables, or remote AWS IAM role. Depending on the extent of those permissions, this authentication instead method might not be recommended for production use, as it can lead to accidental privilege escalation. It is recommended to also configure an IAM role when using the implicit authentication method, or to use the AWS IAM Role, AWS Session Token, or AWS Federation Token authentication methods instead to limit the validity and/or permissions of the credentials being issued to connector clients.

If you need to access an EKS Kubernetes cluster with this authentication method, please be advised that the EKS cluster's aws-auth ConfigMap may need to be manually configured to allow authentication with the implicit IAM user or role picked up by the Service Connector. For more information, see this documentation.

An AWS region is required and the connector may only be used to access AWS resources in the specified region.

The following assumes the local AWS CLI has a connectors AWS CLI profile already configured with credentials:

AWS_PROFILE=connectors zenml service-connector register aws-implicit --type aws --auth-method implicit --region=us-east-1

Example Command Output

⠸ Registering service connector 'aws-implicit'...

Successfully registered service connector `aws-implicit` with access to the following resources:

┏━━━━━━━━━━━━━━━━━━━━━━━┯━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓

┃     RESOURCE TYPE     │ RESOURCE NAMES                               ┃

┠───────────────────────┼──────────────────────────────────────────────┨

┃    🔶 aws-generic     │ us-east-1                                    ┃

┠───────────────────────┼──────────────────────────────────────────────┨

┃     📦 s3-bucket      │ s3://zenfiles                                ┃

┃                       │ s3://zenml-demos                             ┃