Skip to content
Slipwaydocs

Amazon ECR

Use ECR repositories with workload identity, no stored keys.

At a glance

Section titled “At a glance”
Category Registries & artifact repositories
Authentication IAM role via OIDC (no static keys)
Provider id ecr

What it does

Section titled “What it does”
  • Repository and tag listing
  • Digest resolution
  • Push from build steps (aws ecr get-login-password replaced by federation)

Set up

Section titled “Set up”
  1. Create a read (and optionally push) credential in the registry; prefer short-lived or workload-identity credentials.
  2. In Settings, Integrations, add the registry and store the credential as a Slipway secret reference.
  3. Use it as a service artifact source, or reference it from slipway/docker-build@v1 for pushes.

Configuration

Section titled “Configuration”

Illustrative configuration. Non-secret settings are stored as integration config; credentials are stored as encrypted Slipway secrets and referenced by name.

provider: ecr
config:
  region: eu-west-1
  account_id: "123456789012"
  role_arn: arn:aws:iam::123456789012:role/slipway-ecr-read

Notes

Section titled “Notes”

See OIDC with AWS for the trust policy.

Section titled “Related”