AWS App Mesh – Service Mesh for Microservices on AWS

[willejs]

I am looking forwards to digging in to this a bit more and figuring out how this compares to Istio. I am guessing integration with AWS services such as X-ray and Cloudwatch/logs are the selling point. Still, I am a bit weary about configuring things that run inside your Kubernetes cluster through amazon apis, and not k8s resources. However, you could easily create a custom resource for this. Maybe that is to come? EKS is still young and they are yet to figure a lot of things out, from what i've seen, the roadmap is promising though. I have been working with it a lot, kops still wins for small/medium workloads in production, but I doubt for much longer.

[shubha-aws]

shubha from AWS here, we built App Mesh to enable customers to use microservices in any compute service in AWS - be it ECS, Fargate, EKS or even directly on EC2. You configure capabilities using APIs and App Mesh configures Envoy proxies deployed with your pods.

[burtonator]

IS it Istio? Someone on Twitter mentioned it uses the same ports and MIGHT just be Istio...

[paulannesley]

I wonder if this integrates with AWS Certificate Manager to provision HTTPS certificates so that traffic can be end-to-end encrypted. That's one of the reasons I've stuck to Application Load Balancers in front of services instead of using ECS/Route53 service discovery.

[shubha-aws]

Not yet. On the roadmap. Leave us your inputs https://github.com/awslabs/aws-app-mesh-examples/issues/33

[yodon]

Would this be suitable for an actor-based system (where we want to think of each actor as a routeable microservice)?

[staticassertion]

Assuming your actors use queues, as they traditionally would, I don't think so. You don't really need service mesh if your communication is a queue, right?

[caniszczyk]

Good timing since Envoy just became a graduated project at CNCF.io

https://blog.envoyproxy.io/envoy-graduates-a6f71879852e

[gauravphoenix]

like Istio?

[jsmeaton]

Perhaps you can help me out. I'm wondering where Istio (and other meshes) fit into the picture when deploying to k8s. The Itsio docs mention it is deployed as a side car, but is that within each pod? And are Service objects still required?

Here is my mental model of a traditional deployment (EKS):

Service[Type: LoadBalancer] -> Deployment[Pod]

How does Itsio fit into this scenario, or what does it replace?

[rodgerd]

It rather looks that way, although it seems like it requires more explicit configuration.

[lcalcote]

The service mesh landscape will be updated soon - https://layer5.io/landscape

[xmly]

Just wonder how this could connect with Fargate and possibly support scale-down to zero with power of firecracker?

[shubha-aws]

You can use app mesh with fargate services, support coming by GA

[sandstrom]

Sounds similar to Consul, which has a similar architecture.

[jugg1es]

AWS is totally killing it this week. This is like the 10th major release I've seen since monday.

[sokoloff]

Well, it’s Re:Invent this week (AWS’ major annual conference), so this is fairly typical. Expect another handful or so of announcements tomorrow during Werner Vogel’s keynote as well.

[devonkim]

Happens every time at re:Invent

[bg4]

More cool stuff you probably don't need whatsoever.