AWS App Mesh HTTP-header-based routing and route priorities

[ewbankkit]

Community Note

• 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

Description

AWS App Mesh HTTP-header-based routing and route priorities are now available.

New or Affected Resource(s)

• aws_appmesh_route

Potential Terraform Configuration

resource "aws_appmesh_route" "serviceb" {
  name                = "serviceB-route"
  mesh_name           = "${aws_appmesh_mesh.simple.id}"
  virtual_router_name = "${aws_appmesh_virtual_router.serviceb.name}"

  spec {
    http_route {
      match {
        prefix = "/"
      }

      header {
        name = "clientRequestId"

        match {
          prefix = "123"
        }
      }

      action {
        weighted_target {
          virtual_node = "${aws_appmesh_virtual_node.serviceb1.name}"
          weight       = 90
        }

        weighted_target {
          virtual_node = "${aws_appmesh_virtual_node.serviceb2.name}"
          weight       = 10
        }
      }
    }
  }
}

References

Announcement.
User Guide.
API Reference.

Available in AWS SDK v1.23.2.

AWS App Mesh roadmap:

• HTTP Header based routing aws/aws-app-mesh-roadmap#15
• Explicit Route Priorities  aws/aws-app-mesh-roadmap#77

Requires:

• Update module aws/aws-sdk-go to v1.23.12 #9770

[ewbankkit]

Related:

• [WIP] App Mesh preview - HTTP header based routing, route priorities, cookie based routing and retry policy #9468

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!