Resource aws_fsx_ontap_file_system does not allow throughput capacity lower than 512

[varunrai]

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

Terraform CLI and Terraform AWS Provider Version

Terraform v1.1.7
on windows_amd64
provider registry.terraform.io/hashicorp/aws v3.75.0

Affected Resource(s)

• aws_fsx_ontap_file_system

Terraform Configuration Files

Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.

resource "aws_fsx_ontap_file_system" "fsx_ontap_fs" {
  storage_capacity    = 1024
  subnet_ids          = [aws_subnet.fsxsubnet01.id, aws_subnet.fsxsubnet02.id]
  deployment_type     = "MULTI_AZ_1"
  throughput_capacity = 128
  preferred_subnet_id = aws_subnet.fsxsubnet01.id
  fsx_admin_password  = var.default_password
}

Expected Behavior

As per the documentation and AWS Console, the resource should be able to accept 128 and 256 as the throughput capacity values.

Actual Behavior

Fails with the error

│ Error: expected throughput_capacity to be one of [512 1024 2048], got 128     
│ 
│   with aws_fsx_ontap_file_system.fsx_ontap_fs,
│   on main.tf line 195, in resource "aws_fsx_ontap_file_system" "fsx_ontap_fs":
│  195:   throughput_capacity = 128
│ 

Steps to Reproduce

1. terraform apply

Important Factoids

References

• AWS Doc - FSxN Throughput Capacity

[github-actions]

This functionality has been released in v4.9.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.