Support for gp3 on aws_elasticsearch_domain ebs_options volume_type

[ryan-dyer-sp]

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 other comments that do not add relevant new information or questions, 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

Description

Elasticsearch now supports GP3 volume types. Please add functionality to support gp3 as a volume type.

New or Affected Resource(s)

aws_elasticsearch_domain

Potential Terraform Configuration

resource "aws_elasticsearch_domain" "domain" {
	ebs_options {
		volume_type = "gp3"
	}
}

References

https://docs.aws.amazon.com/opensearch-service/latest/developerguide/limits.html#ebsresource

[justinretzolk]

Hey @ryan-dyer-sp 👋 Thank you for taking the time to raise this! The aws_elasticsearch_domain resource uses elasticsearch.VolumeType_Values() to validate the value passed to the volume_type argument. This function was updated yesterday in AWS Go SDK version 1.44.65 to include gp3, so this should work automatically in AWS Provider 4.25.0 when it's released.

[ReadyElbow]

@justinretzolk Thanks for quickly acting on this. Do you know if Terraform supports the advanced configuration options that GP3 supports?

Within the AWS GUI, we can control IOPs/Throughput. Terraform appears to support IOPs but not Throughput.

[ewbankkit]

@ReadyElbow The throughput attribute will need to be added to the ebs_options configuration block.

[github-actions]

This functionality has been released in v4.26.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.