You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Valid protocol values are "HTTP", "HTTP2", and "GRPC". I would like to request the addition of support for "HTTPS" as an application protocol in AWS Service Connect.
Which service(s) is this request for?
ECS, Service Connect.
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
Currently, when using Service Connect, the available application protocols are limited to HTTP, HTTP2, and gRPC, with no support for HTTPS. As a result, applications that require HTTPS must implement workarounds, such as using load balancers to handle HTTPS traffic.
Are you currently working around this issue?
I am using load balancers to handle HTTPS traffic, which adds complexity and overhead to the deployment process.
The text was updated successfully, but these errors were encountered:
Community Note
Tell us about your request
When setting up Service Connect you can optionally set a field for
appProtocol
in the task definition, https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definition_parameters.html.Valid protocol values are "HTTP", "HTTP2", and "GRPC". I would like to request the addition of support for "HTTPS" as an application protocol in AWS Service Connect.
Which service(s) is this request for?
ECS, Service Connect.
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
Currently, when using Service Connect, the available application protocols are limited to HTTP, HTTP2, and gRPC, with no support for HTTPS. As a result, applications that require HTTPS must implement workarounds, such as using load balancers to handle HTTPS traffic.
Are you currently working around this issue?
I am using load balancers to handle HTTPS traffic, which adds complexity and overhead to the deployment process.
The text was updated successfully, but these errors were encountered: