Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: aws_fsx_windows_file_system throughput_capacity can be only 2048MB/s but in AWS console 12288MB/s #40289

Closed
wsmolkowski opened this issue Nov 25, 2024 · 6 comments · Fixed by #40468
Labels
bug Addresses a defect in current functionality. enhancement Requests to existing resources that expand the functionality or scope. service/fsx Issues and PRs that pertain to the fsx service.
Milestone

Comments

@wsmolkowski
Copy link

wsmolkowski commented Nov 25, 2024

Terraform Core Version

1.5.7

AWS Provider Version

5.77.0

Affected Resource(s)

aws_fsx_windows_file_system throughput_capacity can be only 2048MB/s but in AWS console 12288MB/s

Expected Behavior

can set throughput_capacity to 12288MB/s

Actual Behavior

max is 2048 MB/s

Relevant Error/Panic Output Snippet

Planning failed. Terraform encountered an error while generating this plan.
╷
│ Error: expected throughput_capacity to be in the range (8 - 2048), got 4608
│

Terraform Configuration Files

resource "aws_fsx_windows_file_system" "example" {
  active_directory_id = aws_directory_service_directory.example.id
  kms_key_id          = aws_kms_key.example.arn
  storage_capacity    = 300
  subnet_ids          = [aws_subnet.example.id]
  throughput_capacity = 4096
}

Steps to Reproduce

create resource with throughput_capacity > 2048

Debug Output

Planning failed. Terraform encountered an error while generating this plan.
╷
│ Error: expected throughput_capacity to be in the range (8 - 2048), got 4608

Panic Output

No response

Important Factoids

No response

References

No response

Would you like to implement a fix?

None

@wsmolkowski wsmolkowski added the bug Addresses a defect in current functionality. label Nov 25, 2024
Copy link

Community Note

Voting for Prioritization

  • Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
  • Please see our prioritization guide for information on how we prioritize.
  • 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.

Volunteering to Work on This Issue

  • If you are interested in working on this issue, please leave a comment.
  • If this would be your first contribution, please review the contribution guide.

@github-actions github-actions bot added service/fsx Issues and PRs that pertain to the fsx service. needs-triage Waiting for first response or review from a maintainer. labels Nov 25, 2024
@stefanfreitag
Copy link
Contributor

stefanfreitag commented Nov 25, 2024

Hi @wsmolkowski,

thank you for reporting the issue.

I had a quick look into the AWS provider source code. The allowed range is specified here and a valid value is between 8 and 2048.
This is also mentioned in the providers resource documentation

In the AWS documentation I found a section that explains that the supported max value depends on the region:

Amazon FSx file systems provide up to 2 GB/s and 80,000 IOPS in all AWS Regions where Amazon FSx is available, and 12 GB/s of throughput and 400,000 IOPS in US East (N. Virginia), US West (Oregon), US East (Ohio), Europe (Ireland), Asia Pacific (Tokyo), and Asia Pacific (Singapore).

Hope that helps to understand the current situation.

@ewbankkit ewbankkit added enhancement Requests to existing resources that expand the functionality or scope. and removed needs-triage Waiting for first response or review from a maintainer. bug Addresses a defect in current functionality. labels Dec 5, 2024
@github-actions github-actions bot added the bug Addresses a defect in current functionality. label Dec 5, 2024
@ewbankkit
Copy link
Contributor

Copy link

github-actions bot commented Dec 6, 2024

Warning

This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them.

Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed.

@github-actions github-actions bot added this to the v5.81.0 milestone Dec 6, 2024
Copy link

This functionality has been released in v5.81.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!

Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 12, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Addresses a defect in current functionality. enhancement Requests to existing resources that expand the functionality or scope. service/fsx Issues and PRs that pertain to the fsx service.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants