AWS - ECR Persistence
ECR
For more information check:
Hidden Docker Image with Malicious Code
An attacker could upload a Docker image containing malicious code to an ECR repository and use it to maintain persistence in the target AWS account. The attacker could then deploy the malicious image to various services within the account, such as Amazon ECS or EKS, in a stealthy manner.
Repository Policy
Add a policy to a single repository granting yourself (or everybody) access to a repository:
Note that ECR requires that users have permission to make calls to the ecr:GetAuthorizationToken
API through an IAM policy before they can authenticate to a registry and push or pull any images from any Amazon ECR repository.
Registry Policy & Cross-account Replication
It's possible to automatically replicate a registry in an external account configuring cross-account replication, where you need to indicate the external account there you want to replicate the registry.
First, you need to give the external account access over the registry with a registry policy like:
Then apply the replication config:
Last updated