IS ECR strongly read-after-write consistent?

Question

My team has a pipeline which deploys to ECR then immediately requests that deployed container. We have had some issues with this test behaving non-deterministically, so I want to narrow down if ECR might be causing these issues with its consistency model.

I cannot find any information about the consistency of ECR, so any input would be appreciated :)

Answer

One of the core ECR internal component provides fast access to repository, image and layer information. Additionally it provides transactional guarantees around an eventually consistent storage backend allowing for the ability to offer deletes and do garbage collection on layers.
In general ECR should guarantee the transactions including ordering

IS ECR strongly read-after-write consistent?

Contenus pertinents