Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[ec2] add gp3 support to EbsDeviceVolumeType

See original GitHub issue

The newly released gp3 volumes are supported by Cloudformation. But aws_cdk.aws_ec2.EbsDeviceVolumeType does not support it yet. Ref: https://docs.aws.amazon.com/cdk/api/latest/python/aws_cdk.aws_ec2/EbsDeviceVolumeType.html#aws_cdk.aws_ec2.EbsDeviceVolumeType

Work-around:

perf_server = ebs_gp3_perf_server.node.default_child
# Assuming the gp3 volume is the first device in the list, accessed by index '0'
perf_server.add_property_override("BlockDeviceMappings.0.Ebs.VolumeType", "gp3")

Cdk gives you a warning [Warning at /stack/Ec2Server] iops will be ignored without volumeType: EbsDeviceVolumeType.IO1 But gp3 allows your to have provisioned IOPS

Issue Analytics

State:
Created 3 years ago
Reactions:9
Comments:10 (6 by maintainers)

Top GitHub Comments

3reactions

tpundercommented, Dec 16, 2020

Don’t forget about supporting the Throughput and IOPS configuration for GP3 volumes. It probably makes sense also add in IO2 support at the same time too.

2reactions

jumiccommented, Aug 15, 2021

There are three topics mentioned in this issue:

Volume type GP3 in ec2 --> Resolved by PR #12074.
Volume type GP3 for EmrCreateCluster.EbsBlockDeviceVolumeType --> This must not be implemented because GP3 is not supported there, see service documentation and cloudformation documentation.
New property Throughput in EbsDeviceOptionsBase. --> New feature request, related to GP3. However, GP3 can also used with the default value for property troughput. @peterwoodworth To keep it clean: should we add a new feature request (low priority) for this property and close this issue?