─────────────────────────────────────────────────┨┃ 🌀 kubernetes-cluster │ zenml-test-cluster                              ┃

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

┃  🐳 docker-registry   │ gcr.io/zenml-core                               ┃

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

Scopes: multi-type, multi-instance, and single-instance

These terms are briefly explained in the Terminology section: you can register a Service Connector that grants access to multiple types of resources, to multiple instances of the same Resource Type, or to a single resource.

Service Connectors created from basic Service Connector Types like Kubernetes and Docker are single-resource by default, while Service Connectors used to connect to managed cloud resources like AWS and GCP can take all three forms.

The following example shows registering three different Service Connectors configured from the same AWS Service Connector Type using three different scopes but with the same credentials:

a multi-type AWS Service Connector that allows access to every possible resource accessible with the configured credentials

a multi-instance AWS Service Connector that allows access to multiple S3 buckets

a single-instance AWS Service Connector that only permits access to one S3 bucket

zenml service-connector register aws-multi-type --type aws --auto-configure

Example Command Output

⠋ Registering service connector 'aws-multi-type'...

Successfully registered service connector `aws-multi-type` with access to the following resources:

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

┃     RESOURCE TYPE     │ RESOURCE NAMES                               ┃

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

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

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

┃     📦 s3-bucket      │ s3://aws-ia-mwaa-715803424590                ┃