The module should have the option to choose gp3 as volume type too.
Use Case
Replace gp2 volumes with gp3
🔸gp3 volumes are 20% cheaper than gp2
🔸gp3 volumes are at least as performant (in most cases they are more performant) than gp2 volumes
🔸gp3 volumes will give you 3000 base IOPS irrespective of volume size - therefore not increasing your volume costs
🔸You can add additional IOPS to gp3 as needed .
Describe Ideal Solution
master_instance_group_ebs_type
core_instance_group_ebs_type
task_instance_group_ebs_type
variables should be changed to support gp3 as volume type.
Describe the Feature
AWS EMR supports gp3 volume but the module gives the valid options are
gp2
,io1
,standard
andst1
". It should give the option of gp3 as well. https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/emr_clusterExpected Behavior
The module should have the option to choose gp3 as volume type too.
Use Case
Replace gp2 volumes with gp3
🔸gp3 volumes are 20% cheaper than gp2 🔸gp3 volumes are at least as performant (in most cases they are more performant) than gp2 volumes 🔸gp3 volumes will give you 3000 base IOPS irrespective of volume size - therefore not increasing your volume costs 🔸You can add additional IOPS to gp3 as needed .
Describe Ideal Solution
master_instance_group_ebs_type core_instance_group_ebs_type task_instance_group_ebs_type variables should be changed to support gp3 as volume type.
Alternatives Considered
No response
Additional Context
No response