ot recommended) have a maximum duration of 1 hour.As a precaution, when long-lived credentials (i.e. AWS Secret Keys) are detected on your environment by the Service Connector during auto-configuration, this authentication method is automatically chosen instead of the AWS Secret Key authentication method alternative.

Generated STS tokens inherit the full set of permissions of the IAM user or AWS account root user that is calling the GetSessionToken API. Depending on your security needs, this may not be suitable for production use, as it can lead to accidental privilege escalation. Instead, it is recommended to use the AWS Federation Token or AWS IAM Role authentication methods to restrict the permissions of the generated STS tokens.

For more information on session tokens and the GetSessionToken AWS API, see the official AWS documentation on the subject.

The following assumes the local AWS CLI has a connectors AWS CLI profile already configured with an AWS Secret Key:

AWS_PROFILE=connectors zenml service-connector register aws-session-token --type aws --auth-method session-token --auto-configure

Example Command Output

⠸ Registering service connector 'aws-session-token'...

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

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

┃     RESOURCE TYPE     │ RESOURCE NAMES                               ┃

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

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

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

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

┃                       │ s3://zenml-demos                             ┃

┃                       │ s3://zenml-generative-chat                   ┃

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

┃ 🌀 kubernetes-cluster │ zenhacks-cluster                             ┃