 not scoped to a single ECR repository. Instead, aconnector configured with this resource type will grant access to all the ECR

repositories that the credentials are allowed to access under the configured AWS

region (i.e. all repositories under the Docker registry URL

https://{account-id}.dkr.ecr.{region}.amazonaws.com).

The resource name associated with this resource type uniquely identifies an ECR

registry using one of the following formats (the repository name is ignored,

only the registry URL/ARN is used):

ECR repository URI (canonical resource name):

[https://]{account}.dkr.ecr.{region}.amazonaws.com[/{repository-name}]

ECR repository ARN:

arn:aws:ecr:{region}:{account-id}:repository[/{repository-name}]

ECR repository names are region scoped. The connector can only be used to access

ECR repositories in the AWS region that it is configured to use.

────────────────────────────────────────────────────────────────────────────────

The Service Connector is how you configure ZenML to authenticate and connect to one or more external resources. It stores the required configuration and security credentials and can optionally be scoped with a Resource Type and a Resource Name.

Depending on the Service Connector Type implementation, a Service Connector instance can be configured in one of the following modes with regards to the types and number of resources that it has access to:

a multi-type Service Connector instance that can be configured once and used to gain access to multiple types of resources. This is only possible with Service Connector Types that support multiple Resource Types to begin with, such as those that target multi-service cloud providers like AWS, GCP and Azure. In contrast, a single-type Service Connector can only be used with a single Resource Type. To configure a multi-type Service Connector, you can simply skip scoping its Resource Type during registration.