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.

Attributes:

aws_access_key_id {string, secret, required}: AWS Access Key ID

aws_secret_access_key {string, secret, required}: AWS Secret Access Key

region {string, required}: AWS Region

endpoint_url {string, optional}: AWS Endpoint URL

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

Dashboard equivalent:

Not all Stack Components support being linked to a Service Connector. This is indicated in the flavor description of each Stack Component. Our example uses the S3 Artifact Store, which does support it:

$ zenml artifact-store flavor describe s3

Configuration class: S3ArtifactStoreConfig

[...]

This flavor supports connecting to external resources with a Service Connector. It requires a 's3-bucket' resource. You can get a list of all available connectors and the compatible resources that they can

access by running:

'zenml service-connector list-resources --resource-type s3-bucket'

If no compatible Service Connectors are yet registered, you can register a new one by running:

'zenml service-connector register -i'