You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 馃憤 reaction 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.
The text was updated successfully, but these errors were encountered:
Community Note
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.
The text was updated successfully, but these errors were encountered: