─────────────────────────────────────────────────┨┃ b551f3ae-1448-4f36-97a2-52ce303f20c9 │ kube-auto             │ 🌀 kubernetes  │ 🌀 kubernetes-cluster │ A5F8F4142FB12DDCDE9F21F6E9B07A18.gr7.us-east-1.eks.amazonaws.com ┃

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

Every Service Connector Type defines its own rules for how Resource Names are formatted. These rules are documented in the section belonging each resource type. For example:

zenml service-connector describe-type aws --resource-type docker-registry

Example Command Output

╔══════════════════════════════════════════════════════════════════════════════╗

║        🐳 AWS ECR container registry (resource type: docker-registry)        ║

╚══════════════════════════════════════════════════════════════════════════════╝

Authentication methods: implicit, secret-key, sts-token, iam-role,

session-token, federation-token

Supports resource instances: False

Authentication methods:

🔒 implicit

🔒 secret-key

🔒 sts-token

🔒 iam-role

🔒 session-token

🔒 federation-token

Allows users to access one or more ECR repositories as a standard Docker

registry resource. When used by Stack Components, they are provided a

pre-authenticated python-docker client instance.

The configured credentials must have at least the following AWS IAM permissions

associated with the ARNs of one or more ECR repositories that the connector will

be allowed to access (e.g. arn:aws:ecr:{region}:{account}:repository/*

represents all the ECR repositories available in the target AWS region).

ecr:DescribeRegistry

ecr:DescribeRepositories

ecr:ListRepositories

ecr:BatchGetImage

ecr:DescribeImages

ecr:BatchCheckLayerAvailability

ecr:GetDownloadUrlForLayer

ecr:InitiateLayerUpload

ecr:UploadLayerPart

ecr:CompleteLayerUpload

ecr:PutImage

ecr:GetAuthorizationToken

This resource type is not scoped to a single ECR repository. Instead, a