Stax Networking ECR VPC Endpoint Fix
A bug has been resolved that prevented the deployment of Fargate containers into a private subnet within a Stax Networks VPC. When trying to deploy a container, you may have received an error message similar to the following:
CannotPullContainerError: failed to resolve ref
"123456789012.dkr.ecr.ap-southeast-2.amazonaws.com/nginx:latest": failed to do
request: Head
https://123456789012.dkr.ecr.ap-southeast-2.amazonaws.com/v2/nginx/manifests/latest:
dial tcp: lookup 751463547...
This error was caused by the absence of a specific DNS record for the ECR VPC Interface endpoint.
To resolve this issue, when the ECR Interface endpoint is enabled in
a Networking Hub, a new Route 53 resource record will be created for
*.dkr.ecr.
If you have existing Networking Hubs in place, you must disable and enable the ECR Interface endpoint to create the new Route 53 resource record.