nment or the Stack Component.

End-to-end examplesThis is an example of an end-to-end workflow involving Service Connectors that use a single multi-type AWS Service Connector to give access to multiple resources for multiple Stack Components. A complete ZenML Stack is registered and composed of the following Stack Components, all connected through the same Service Connector:

a Kubernetes Orchestrator connected to an EKS Kubernetes cluster

an S3 Artifact Store connected to an S3 bucket

an ECR Container Registry stack component connected to an ECR container registry

a local Image Builder

As a last step, a simple pipeline is run on the resulting Stack.

Configure the local AWS CLI with valid IAM user account credentials with a wide range of permissions (i.e. by running aws configure) and install ZenML integration prerequisites:Copyzenml integration install -y aws s3Copyaws configure --profile connectors

Example Command Output

```text

AWS Access Key ID [None]: AKIAIOSFODNN7EXAMPLE

AWS Secret Access Key [None]: wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY

Default region name [None]: us-east-1

Default output format [None]: json

```

Make sure the AWS Service Connector Type is availableCopyzenml service-connector list-types --type aws

Example Command Output

```text

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

┃         NAME          │ TYPE   │ RESOURCE TYPES        │ AUTH METHODS     │ LOCAL │ REMOTE ┃

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

┃ AWS Service Connector │ 🔶 aws │ 🔶 aws-generic        │ implicit         │ ✅    │ ✅     ┃

┃                       │        │ 📦 s3-bucket          │ secret-key       │       │        ┃

┃                       │        │ 🌀 kubernetes-cluster │ sts-token        │       │        ┃

┃                       │        │ 🐳 docker-registry    │ iam-role         │       │        ┃