Aws-app-mesh-roadmap: Provide the Envoy software in each region where App Mesh is available

[jtoberon]

You should not have to do cross-region pulls in order to deploy the Envoy sidecar. Cross-region traffic can affect both performance and availability.

[Y0Username]

Envoy image is now available in all the regions where AppMesh is available with URI:

111345817488.dkr.ecr._region_.amazonaws.com/aws-appmesh-envoy:v1.11.1.0-prod

Example:

$(aws ecr get-login --region us-east-1 --no-include-email)
docker pull 111345817488.dkr.ecr.us-east-1.amazonaws.com/aws-appmesh-envoy:v1.11.1.0-prod

[ehough]

Potentially stupid question, could anyone tell me why I can't pull this image from any region?

$(aws ecr get-login --no-include-email)
docker pull 111345817488.dkr.ecr.us-east-1.amazonaws.com/aws-appmesh-envoy:v1.11.1.0-prod

Results in an error:

Error response from daemon: Get https://111345817488.dkr.ecr.us-east-1.amazonaws.com/v2/aws-appmesh-envoy/manifests/v1.11.1.0-prod: no basic auth credentials

[bcelenza]

@ehough Try this login command instead:

$(aws ecr get-login --no-include-email --registry-ids 111345817488)

Hopefully that resolves the issue.

[ehough]

$(aws ecr get-login --no-include-email --registry-ids 111345817488)

That worked, thank you @bcelenza :tada:

The docs talk about pushing to an ECR repo, but I should've figured it would be the same solution for pulling.

[bcelenza]

@ehough Sweet! I've submitted some feedback on the documentation you linked to get it reworded to include pull as well :)