aws
[Fargate] [request]: Add support for Graviton4
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
Tell us about your request Add support for Graviton4
Which service(s) is this request for? Fargate
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
AWS Graviton4-based Amazon EC2 R8g instances deliver up to 30% better performance than AWS Graviton3-based Amazon EC2 R7g instances
https://aws.amazon.com/blogs/aws/aws-graviton4-based-amazon-ec2-r8g-instances-best-price-performance-in-amazon-ec2/
Are you currently working around this issue? .
Additional context .
Attachments If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.) Similar Request to support Graviton 3 on Fargate: https://github.com/aws/containers-roadmap/issues/2230
One thing we noticed when moving our EC2 workloads from Graviton2/3 to Graviton4 was that some of our binaries failed and needed to be recompiled to avoid 32-bit instructions, which are no longer supported in Graviton4 (vs Graviton 2/3). We'd also like to have Fargate on Graviton4 but this compatibility issue may mean that it would need to be a separate Fargate cpu architecture.
Some details on this from the honeycomb team: https://www.honeycomb.io/blog/engineering-teams-should-embrace-graviton4
One thing we noticed when moving our EC2 workloads from Graviton2/3 to Graviton4 was that some of our binaries failed and needed to be recompiled to avoid 32-bit instructions, which are no longer supported in Graviton4 (vs Graviton 2/3). We'd also like to have Fargate on Graviton4 but this compatibility issue may mean that it would need to be a separate Fargate cpu architecture.
Some details on this from the honeycomb team: https://www.honeycomb.io/blog/engineering-teams-should-embrace-graviton4
Good call-out. Thanks for sharing!
