Plugin does not work with AWS VPCE

[guidhaus]

We are trying to use the plugin in an environment with AWS VPCE using the docker login authentication. When pushing an image to our registry, the plugin tries to connect to api.ecr.eu-south-1.amazonaws.com instead of our VPCE api server.

Are we missing some configuration?

Thanks

[SteveHodson]

This strikes me as a routing issue rather than a plugin issue. When using a private ECR, for example, you would be expected to add a S3 Gateway VPCE. This will generate a prefix list with a small number of public IPs that will be mapped to that Gateway interface, which is used by the VPCs DNS resolver to route to the correct endpoint.
I'm assuming here that you are using a private ECR.

[guidhaus]

Hi Steve,

thanks for your response. I can confirm that we’re trying to use a private ECR.. The issue occurs when the plugin attempts to retrieve the authorization token for our private ECR: the request is sent to api.ecr.eu-south-1.amazonaws.com instead of (as I would expect) our VPCE endpoint (vpce-###########.api.ecr.eu-south-1.vpce.amazonaws.com).

It seems that the API address might be hardcoded here, am I mistaken?

Thank you!

[mbarinc]

Hi, any news about this issue?

Is it possible to make the ECR endpoint configurable, instead of having it hardcoded in the code? If not explicitly specified, "api.ecr." + region + ".amazonaws.com" can be the default, unless a different host is provided as an argument to the plugin (private ECR scenario).

Thanks.

[rohanKanojia]

@mbarinc : Hello, would it be possible for you or someone from your team to submit a PR to make this configurable?