━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛

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

┃ PROPERTY              │ VALUE     ┃

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

┃ region                │ us-east-1 ┃

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

┃ aws_access_key_id     │ [HIDDEN]  ┃

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

┃ aws_secret_access_key │ [HIDDEN]  ┃

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

┃ aws_session_token     │ [HIDDEN]  ┃

┗━━━━━━━━━━━━━━━━━━━━━━━┷━━━━━━━━━━━┛

As can be seen, this configuration is of a temporary STS AWS token that will expire in 12 hours. The AWS Secret Key is not visible on the client side.

The next step in this journey is configuring and connecting one (or more) Stack Components to a remote resource via the Service Connector registered in the previous step. This is as easy as saying "I want this S3 Artifact Store to use the s3://my-bucket S3 bucket" and doesn't require any knowledge whatsoever about the authentication mechanisms or even the provenance of those resources. The following example creates an S3 Artifact store and connects it to an S3 bucket with the earlier connector:

zenml artifact-store register s3-zenfiles --flavor s3 --path=s3://zenfiles

zenml artifact-store connect s3-zenfiles --connector aws-s3

Example Command Output

$ zenml artifact-store register s3-zenfiles --flavor s3 --path=s3://zenfiles

Successfully registered artifact_store `s3-zenfiles`.

$ zenml artifact-store connect s3-zenfiles --connector aws-s3

Successfully connected artifact store `s3-zenfiles` to the following resources:

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

┃             CONNECTOR ID             │ CONNECTOR NAME │ CONNECTOR TYPE │ RESOURCE TYPE │ RESOURCE NAMES ┃

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

┃ 96a92154-4ec7-4722-bc18-21eeeadb8a4f │ aws-s3         │ 🔶 aws         │ 📦 s3-bucket  │ s3://zenfiles  ┃