aws / aws/containers-roadmap

[ECS] [request]: Cannot call ECS services from lambda

Open
#2,344 0 comments 8 reactions 1 assignee Claimed by @kshivaz View on GitHub
ECS Proposed Service Connect
Dominant language
Shell
Stars
5.4k
Forks
334
PR merge metrics
No merged PRs in 30d

Description

### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment

**Tell us about your request**
Recently we migrated from AWS Appmesh to ECS Service Connect. We noticed that we can not call our services from lambda anymore. It was working properly under Appmesh.

**Which service(s) is this request for?**
ECS, fargate

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
We want to call services from lambda. So let say we have a service configured with service connect like serviceA.local. We want to be able to connect to this service and send requests.

**Are you currently working around this issue?**
Because the CloudMap that the service connect builds is API-only and not DNS Query, we need to use AWS SDK ServiceDiscovery to get the IP of the service and then connect to it using IP.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.