Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HTTP/2 not enabled for target groups #391

Open
universam1 opened this issue Jan 14, 2021 · 4 comments · May be fixed by #460
Open

HTTP/2 not enabled for target groups #391

universam1 opened this issue Jan 14, 2021 · 4 comments · May be fixed by #460

Comments

@universam1
Copy link
Contributor

HTTP/2 is enabled per default for the load balancer, but for the target group!

According to this announcement and the AWS console the target groups do support HTTP/2 as well.

https://aws.amazon.com/blogs/aws/new-application-load-balancer-support-for-end-to-end-http-2-and-grpc/

However, the target groups are always configured to forward to connect via HTTP/1.1

This might have a performance impact

@szuecs
Copy link
Member

szuecs commented Jan 15, 2021

@universam1 normally it should not have an impact because of connection pools. Maybe for frontends it would benefit to do full H2 support.
Do you want to work on an option to enable H2 backend?
I don't want to have this as default set, but the feature would be great to have!

@universam1
Copy link
Contributor Author

pending on Cloudformation support: aws-cloudformation/cloudformation-coverage-roadmap#713

@universam1
Copy link
Contributor Author

@szuecs Cloudformation support is present in meantime, but the underlying CFN lib fork seems to be unmaintained.

Any idea @mikkeloscar how to continue here, guess that's a project relevant question?

@szuecs
Copy link
Member

szuecs commented Jul 5, 2021

I see. I think we have 2 possible ways:

  • fork the dependency project
  • internal it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants