AWS App Mesh introduces timeout configuration support
Share
Services
You can now configure timeouts on your AWS App Mesh virtual nodes and individual routes. Configuring timeouts will allow you to add resiliency to your system with no changes to your services. AWS App Mesh is a service mesh that provides application-level networking to make it easy for your services to communicate with each other across multiple types of compute infrastructure. App Mesh standardizes how your services communicate, giving you end-to-end visibility and ensuring high-availability for your applications.
AWS App Mesh supports two types of timeouts: per-request, which controls the amount of time that a requester will wait to complete a response, and idle, that controls the time at which the connection will be terminated if there are no active streams. Now you can control these timeouts on the virtual node listener level, or at each individual route.
To get started, you can create an App Mesh virtual node and specify the desired timeout values in the listener configuration. For an end-to-end walk through of using a virtual node listener timeout, see [Timeout Policy Example](https://github.com/aws/aws-app-mesh-examples/tree/master/walkthroughs/howto-timeout-policy) on GitHub. To learn more about App Mesh, see the [product page](/app-mesh/) or [documentation](https://docs.aws.amazon.com/app-mesh/).
What else is happening at Amazon Web Services?
Read update
Services
Share
Read update
Services
Share
Amazon Managed Service for Prometheus now supports configuring a minimum firing period for alerts
October 16th, 2024
Services
Share