AWS App Mesh now supports routing based on HTTP headers and specifying route priorities

AWS App Mesh now supports HTTP header-based routing to manage traffic between services, in addition to the previously available path prefix based and host based routing capabilities. With this feature, you can create rules and route traffic based on standard and custom HTTP headers and methods, which includes cookie data. Additionally, you can use route priorities to control the order of matching rules.

Using header-based routing, you can create patterns such as session persistence (sticky sessions) or an enhanced experience using "state". HTTP header-based routing enables using HTTP header information as a basis to determine how to route a request. This might be a standard header, like Accept or Cookie, or it might be a custom header, like my-own-header-key-value. Header-based routing can also be used to enable use cases such as A/B testing (e.g.: custom headers using any string), canary or blue/green deployments, delivering different pages or user experiences based on categories of devices. (e.g.: using regex in header), handling traffic from different browsers differently (e.g. using user-agent) or configuring access restrictions based on IP address or CDN. (e.g. using X-Forwarded-for).

This feature is available in all regions where AWS App Mesh is available. To learn more and get started with this feature, see our Documentation.