-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
EbsDeviceProps missing support for setting throughput on GP3 volumes, yet VolumeProps has support for it #24341
Comments
Yes we probably should add this property in EbsDeviceOptionsBase or other interfaces. I'm making this a p2 feature request and any PR submission will be more than welcome and appreciated. |
Comments on closed issues and PRs are hard for our team to see. |
1 similar comment
Comments on closed issues and PRs are hard for our team to see. |
### Issue # (if applicable) Fixes aws#24341. ### Reason for this change You currently can't specify `throughput` on LaunchTemplate EBS volumes. ### Description of changes This support was simply not included in ec2 when it was added to autoscaling in aws#22441. I have copied that PR's implementation implementation to ec2 and similarly adapted its tests. ### Description of how you validated changes Unit and integration tests. ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Describe the feature
When creating and EC2 instance, and configuring a blockDevices property, this uses the BlockDeviceVolume type, which accepts an ebsDevice parameter of type EbsDeviceProps. EbsDeviceProps does not have the option to set a throughput property.
However, if you look at VolumeProps, when creating a volume separately, it does support the throughput property.
Use Case
I've seen examples where people are creating volumes outside of the blockDevices property of an Instance, then have to deal with attaching the volume.
Having the option to create a gp3 volume along with all of its configuration properties (including throughput) directly via the instance as part of the blockDevices property simplifies the deployment of an instance. iops is already an accepted property as part of EbsDeviceProps, why not throughput?
Proposed Solution
No response
Other Information
No response
Acknowledgements
CDK version used
2.66.1
Environment details (OS name and version, etc.)
OSX 12.6.3
The text was updated successfully, but these errors were encountered: