How do tokens and ECR repositories work across different plans and regions?

Context When setting up CI/CD pipelines, customers need to understand how authentication tokens work across different plans (prod/nonprod) and how container images are stored in Amazon ECR repositories across different regions. Answer Here's how our platform handles tokens and ECR repositories: Authentication Tokens The CICD token (sometimes labeled as DUPLO_NONPROD_TOKEN or similar in GitHub) works at the account level, not the plan or tenant level A single token can be used across all plans (prod and nonprod) and tenants within your account The token corresponds to a GITHUB-ACTIONS user with admin privileges in the portal ECR Repositories ECR repositories are region-specific: Production (prod01) ECR is located in eu-west-1 Non-production (nonprod01, nonprod02) ECR is located in us-west-2 Images are not automatically shared between regions You can distinguish between prod and nonprod images through image naming conventions within the same ECR Best Practice: When pushing container images, ensure they are available in the appropriate region for your environment. Use clear naming conventions to distinguish between production and non-production images.