-
Notifications
You must be signed in to change notification settings - Fork 8
Explore running some instances on Graviton instance types #745
Copy link
Copy link
Open
Labels
breaking changeThis issue or pull request involves changes to existing functionalityThis issue or pull request involves changes to existing functionalityimprovementThis issue or pull request will add or improve functionality, maintainability, or ease of useThis issue or pull request will add or improve functionality, maintainability, or ease of useterraformPull requests that update Terraform codePull requests that update Terraform code
Metadata
Metadata
Assignees
Labels
breaking changeThis issue or pull request involves changes to existing functionalityThis issue or pull request involves changes to existing functionalityimprovementThis issue or pull request will add or improve functionality, maintainability, or ease of useThis issue or pull request will add or improve functionality, maintainability, or ease of useterraformPull requests that update Terraform codePull requests that update Terraform code
Type
Fields
Give feedbackNo fields configured for issues without a type.
Projects
Status
No status
🚀 Feature Proposal
We should look at building ARM64 AMIs for some instance types (
bastion,docker,portscan, andvulnscancome to mind) to run on Graviton instance types.Note
We would need to ensure that all dependencies on these instances support ARM64.
Motivation
Leveraging Graviton instance types might gain us both price and performance wins. On the price point for example (in
us-east-1):bastiont3.small$0.0208t4g.small$0.0168dockeerr5.xlarge$0.252r7g.xlarge$0.2142portscant3.medium$0.0416t4g.medium$0.0336vulnscanc5.9xlarge$1.53c7g.8xlarge$1.16Pitch
Using Graviton instances where viable could net us cost-savings, performance gains, and since they are lower power it could be better for the planet.