AWS Cloud Containers Conference - Deep Dive on Configuring AWS App Mesh

[@vijayamahesh3325]

that was a beautiful session , worth a 100$

[@jonathanhle]

Really great demo. Totally clear and helpful.

[@mikedqin]

Excellent demo with concepts! One of the very best deep dives. If you can add virtual router to the demo, it's even better. Thanks.

[@AWSEventsChannel]

Thank you 🙌

[@geraldlerman786]

Excellent presentation! Clear and concise and it covers all questions. Thank you!

[@anhphan5621]

Thanks for the excellent explanation and super great demo!

[@MBJ2323]

Thanks for the demo, great work!

[@mridulagrandhi8896]

Thank you! Glad you found it informative.

[@santhoshkumarballu3661]

I have not seen in this how envoy is configured and used as a sidecar, it directly started with app mesh configurations, could you please update with the correct steps to configure end-end tls configurations for AWS ECS farmgate

[@awssupport]

Sorry for any trouble! We appreciate your feedback. I found a few resources that might help you: go.aws/3YgOJ0Y & go.aws/3qmxQFw. I'd also recommend asking our community for additional insight, on re:Post, if needed: go.aws/aws-repost. 📝 ^AD

[@JamalKhaffaf]

anyone know how to get app mesh to work with an ECS service sitting behind a load balancer? I have an ECS service sitting behind a load balancer and I created a virtual node to point at a DNS address so I chose the load balancer URL which is sitting in Route 53 (so that it would be resolvable DNS address). When I send a POST request, I dont see the request is getting intercepted by Envoy proxy. The request is going directly to the load balancer > then my application. Any help would be appreciated it. thanks!

[@LuisRuizHalo]

Maybe you need to deploy a NLB with a envoy proxy instance itself just like a virtual gateway

[@JamalKhaffaf]

​@@LuisRuizHalo thats a good point, i was planning to get a gateway in front of my services which actually eases up app mesh setup and configuration .... having said that, the above setup for some reason on its own, it started working one day. Neither me or 3 other developers or aws support figured out why it started working on its own. Given the fact we all agreed that I followed the documentation to the T. Anyway all good now. Thanks for your support

[@ryandsouza2962]

Great talk! Will try this with EKS :)

[@manipal2011]

A Virtual Service can send Traffic -> Virtual Router or a Virtual Node

[@abiegross7458]

The key step that was not covered was configuring App Mesh in the task definition. It is assumed to be straight forward but my envoy is unhealthy and the misconfiguration is difficult to determine.

[@Singhcityshenanigans]

Yeah, I am stuck here as well. Did you get it working ?? Any suggestions?

[@trisalrahul]

Very good presentation

[@manipal2011]

You cannot connect Virtual Nodes without a Virtual Service

[@AleLopesYTube]

Excellent presentation

[@AmleshKumar-xd1bi]

Seems like Robot is speaking based on backend program..

[@manipal2011]

In AWS App Mesh - the Virtual Node is a pointer to -> [Kubernetes Pod or AWS ECS Task or AWS EC2 instance]

[@manipal2011]

Routing rules are specified in Virtual Router. The Virtual Router will do the actual Traffic control and routing of packets

[@manipal2011]

If a Virtual Node wants to talk to another Virtual Node, then we will create and use a Virtual Service

[@MDzaman-bg7fn]

Thanks a lot.Almighty bless you.Thanks again.

[@sudhiseshachala3664]

All services are within mesh. Without backend configuration it should still work.

[@蔡明-h3p]

really? why still need beckend

[@manipal2011]

Virtual Service will forward the Packet to Virtual Router

[@DemonicDaron]

Im baffled by how bad this presentation is. Not the content, but the way it is presented. This is not a presentation. This is a document read by a person on video. Very far away from a presentation. Much much faster to just read the docs yourself.

[@kelvinonuchukwu8215]

True. Very true. It's so bad.