gistry or even more than one type of AWS resource:zenml service-connector register --type aws -i

A non-interactive CLI example that leverages the AWS CLI configuration on your local machine to auto-configure an AWS Service Connector targeting an ECR registry is:

zenml service-connector register <CONNECTOR_NAME> --type aws --resource-type docker-registry --auto-configure

Example Command Output

$ zenml service-connector register aws-us-east-1 --type aws --resource-type docker-registry --auto-configure

⠸ Registering service connector 'aws-us-east-1'...

Successfully registered service connector `aws-us-east-1` with access to the following resources:

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

┃   RESOURCE TYPE    │ RESOURCE NAMES                               ┃

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

┃ 🐳 docker-registry │ 715803424590.dkr.ecr.us-east-1.amazonaws.com ┃

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

Note: Please remember to grant the entity associated with your AWS credentials permissions to read and write to one or more ECR repositories as well as to list accessible ECR repositories. For a full list of permissions required to use an AWS Service Connector to access an ECR registry, please refer to the AWS Service Connector ECR registry resource type documentation or read the documentation available in the interactive CLI commands and dashboard. The AWS Service Connector supports many different authentication methods with different levels of security and convenience. You should pick the one that best fits your use case.

If you already have one or more AWS Service Connectors configured in your ZenML deployment, you can check which of them can be used to access the ECR registry you want to use for your AWS Container Registry by running e.g.:

zenml service-connector list-resources --connector-type aws --resource-type docker-registry

Example Command Output