fargate: add ability to register both SRV and A records

aws / containers-roadmap

This is the public roadmap for AWS container services (ECS, ECR, Fargate, and EKS).

https://aws.amazon.com/about-aws/whats-new/containers/

Other

5.21k stars 317 forks source link

fargate: add ability to register both SRV and A records #1699

Open kjpgit opened 2 years ago

kjpgit commented 2 years ago

I have a fargate service.

Its internal IP should be discoverable via A records to other ec2 instances, for low latency. Tools like curl and .net core libraries don't even support SRV records, so moving exclusively to SRV is painful.
But it also seems to need a SRV record for HTTP API (api gateway) to create a private integration with 'vpc link'. This is for our "Slack" integration, which needs a public URL. API GW demands a SRV record, not A. (even though it uses the Discover API, not DNS!)

It's frustrating that both record types aren't supported.

Alternatively, if api gw could just use A records...that would work for us.

kjpgit commented 2 years ago

To add insult to injury, when you select "SRV" it still creates A records, but they're not usable by normal clients. At least, I don't think they're usable, because they have a very random prefix.

e.g. a SRV record points to an A record like f712d9193f964d158b438c4943773e09.api.cps-dev.mycompany.com

herrhound commented 1 year ago

We released ECS Service Connect which specifically addresses this problem. In Service Connect you provide a discoverable name for each of the containers / ports that you want to address. Even though it doesn't use Route 53 DNS and resolves the DNS at the client-side proxy level, it should address your use-case. And you can create an API Gateway's HTTP API that points to ECS Service Connect service.

kjpgit commented 1 year ago

The request was for low latency and overhead from an ec2 instance client, using standard DNS. No desire for proxies or service connect in this case.