[Bug]: aws_elasticsearch_domain ebs_options throughput attribute populated for non-gp3 volume types? #32613
Labels
bug
Addresses a defect in current functionality.
service/elasticsearch
Issues and PRs that pertain to the elasticsearch service.
Terraform Core Version
v1.1.0
AWS Provider Version
v5.8.0
Affected Resource(s)
aws_elasticsearch_domain
Expected Behavior
If the ES domain created with gp3 as volume_type in
aws_elasticsearch_domain.ebs_options
, then when volume_type changed to gp2, no errors related to throughput arise, since the throughput attribute is only applicable to the gp3 volume type.Actual Behavior
The ES domain created with gp3 as volume_type in
aws_elasticsearch_domain.ebs_options
, then when volume_type changed to gp2, getting the below error, and still getting same error even though explicitly setting throughput to null.Error: ValidationException: Throughput is only valid when volume type is GP3.
Relevant Error/Panic Output Snippet
Error: ValidationException: Throughput is only valid when volume type is GP3.
Terraform Configuration Files
please ignore subnet_ids value
Steps to Reproduce
Configure aws_elasticsearch_domain.cluster_config.instance_type to r5.2xlarge.elasticsearch
Run terraform apply
and then
Configure volume_type = "gp2"
Run terraform apply
Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
Same issue raised here with opensearch #27467
and resolved here #28862
Would you like to implement a fix?
Yes
The text was updated successfully, but these errors were encountered: