AWS · Cloud service
Amazon Elastic Container Registry with OrchestrAI
Catalog exported 2026-09-02
Manage Amazon ECR from chat: repositories, lifecycle policies, access policies, image listing, and login.
OrchestrAI exposes 9 ECR operations: 6 are low-risk (read-only or low-impact), and 3 create or modify resources and run only after you confirm the plan. 1 of them also carries a step-level approval gate.
What teams use it for
Platform teams use OrchestrAI to create a repository per service, attach a lifecycle policy that expires untagged images, set a repository policy for cross-account pulls, and list which image tags are present before a deploy. Fetching a Docker login password is low risk, and deleting a repository is high risk with confirmation. Pushing, tagging, or deleting individual images is not covered, and neither is image scanning configuration, so those steps stay with your CI pipeline or the console.
Every ECR operation, with its risk level
| Operation | What it does | Risk | Step-level approval |
|---|---|---|---|
Create ECR Repository (Terraform-style) |
Create an ECR container image repository | Low risk | No |
Get ECR Login |
Get Docker login password for ECR | Low risk | No |
List ECR Images |
List images in an ECR repository | Low risk | No |
List ECR Repositories |
List AWS ECR repositories | Low risk | No |
Set ECR Lifecycle Policy |
Set lifecycle policy for ECR repository image cleanup | Low risk | No |
Set ECR Repository Policy |
Set access policy for ECR repository | Low risk | No |
Create ECR Repository |
Create an Amazon ECR container image repository | Creates resources | No |
Create ECR Repository |
Create an AWS ECR repository | Creates resources | No |
Delete ECR Repository |
Delete an AWS ECR repository | Modifies existing | Yes |
Risk tiers come from the catalog: low is read-only or low-impact, medium creates resources and is reversible, high modifies existing resources, destructive may lose data. Every plan that creates or changes resources is shown with its cost estimate and waits for your confirmation. Operations marked with a step-level approval pause again on their own step. Destructive operations require a typed risk phrase.
Prompts that work
- Create an ECR repository named payments-api with a lifecycle policy that keeps only the last 20 images
- List the images in the frontend repository in us-west-2
- Delete the deprecated-worker ECR repository
Before anything runs
Every mutation shows its plan, cost estimate, and blast radius, then waits for your confirmation. Destructive operations require a typed risk phrase. Credentials are minted per run through OIDC federation and discarded afterward; nothing you create here is invisible later, because every resource lands in the desired-state ledger where drift is detected and can be converged. Details on the security page.
Frequently asked questions
- Can OrchestrAI push images to Amazon ECR?
- No, it can list images and provide a login password for Docker, but the push itself happens from your build system.
- Is deleting an ECR repository reversible in OrchestrAI?
- It is not reversible, which is why it is high risk with confirmation; you review the repository name before approving.
- Which ECR operations need an extra approval step?
- One operation carries a step-level approval gate on top of plan confirmation: Delete ECR Repository. None of them is classed destructive.
Other AWS services
Related integrations
Try it on your own account
Connect your cloud read-only and see your resources, drift, and costs before anything runs. $5 minimum to start. Unused credits refunded in your first 14 days.
Unused credits refunded in your first 14 days.