36a885: Pull complete

c9c0554c8e6a: Pull completebacdcd847a66: Pull complete

482033770844: Pull complete

Digest: sha256:bf2cc3895e70dfa1ee1cd90bbfa599fa4cd8df837e27184bac1ce1cc239ecd3f

Status: Downloaded newer image for 715803424590.dkr.ecr.us-east-1.amazonaws.com/zenml-server:latest

715803424590.dkr.ecr.us-east-1.amazonaws.com/zenml-server:latest

It is also possible to update the local AWS CLI configuration with credentials extracted from the AWS Service Connector:

zenml service-connector login aws-session-token --resource-type aws-generic

Example Command Output

Configured local AWS SDK profile 'zenml-c0f8e857'.

The 'aws-session-token' AWS Service Connector connector was used to successfully configure the local Generic AWS resource client/SDK.

A new profile is created in the local AWS CLI configuration holding the credentials. It can be used to access AWS resources and services, e.g.:

aws --profile zenml-c0f8e857 s3 ls

Stack Components use

The S3 Artifact Store Stack Component can be connected to a remote AWS S3 bucket through an AWS Service Connector.

The AWS Service Connector can also be used with any Orchestrator or Model Deployer stack component flavor that relies on Kubernetes clusters to manage workloads. This allows EKS Kubernetes container workloads to be managed without the need to configure and maintain explicit AWS or Kubernetes kubectl configuration contexts and credentials in the target environment and in the Stack Component.

Similarly, Container Registry Stack Components can be connected to an ECR Container Registry through an AWS Service Connector. This allows container images to be built and published to ECR container registries without the need to configure explicit AWS credentials in the target environment or the Stack Component.

End-to-end examples