Setting iops on non-provisioned IOPS EBS volumes should be a validation error

[gdavison]

When creating or updating an EBS volume, either as a bare resource or as a root volume or attached volume on an EC2 instance, the code either logs a warning (root devices and creating a standalone resource) or does nothing (attached volumes or updating a standalone resource).

This should be treated as a validation error instead.

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

Affected Resource(s)

• aws_instance
• aws_ebs_volume

[anGie44]

The associated changes in #14310 have been merged and will release with the upcoming v3.0.0 of the Terraform AWS Provider.

[ghost]

This has been released in version 3.0.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 for triage. Thanks!

[ghost]

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!