neptune: (add storageType field to support the I/O optimized storage configuration)

[Bombsam]

Describe the feature

AWS has announced the general availability of Amazon Neptune I/O-Optimized, a new configuration for Amazon Neptune Database that provides improved price performance and predictable # for customers with I/O-intensive applications. With Neptune I/O-Optimized, there are zero charges for read and write I/O operations—you only pay for your database instances and storage usage, making it easy to predict your database spend up front. Neptune I/O-Optimized offers up to 40% cost savings for I/O-intensive applications where I/O charges exceed 25% of the total Neptune database spend.

Use Case

The support for feature seems to be already added for the rds module (issue link, PR link), I would like to request it to be added for the neptune module as well.

One of our projects has heavy write loads, and I believe being able to switch to the I/O optimized configuration using the cdk module is going to be quite beneficial both in terms of speed and cost.

Unfortunately we can only perform production deployments through cdk, so we really need the module to be updated so we can perform the upgrade!

Proposed Solution

No response

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

CDK version used

2.146.0

Environment details (OS name and version, etc.)

Linux

[pahud]

Just checked this doc
https://docs.aws.amazon.com/neptune/latest/userguide/storage-types.html#provisioned-iops-storage
Looks like the key is to select iopt1 storage-type. But I can't find relevant prop in CFN https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-neptune-dbcluster.html

I am not sure if CFN has supported it yet. I will create an internal ticket for clarifying.

[pahud]

internal tracking: V1483035394

[pahud]

Hi

Unfortunately cloudformation for that feature is not available at this moment so CDK would not be able to support that.

The best place to bring it up though is https://github.com/aws-cloudformation/cloudformation-coverage-roadmap/issues to help the CFN team prioritize this FR.

I have submit the request internally but it would be helpful for CFN team to prioritize from the cloudformation-coverage-roadmap repo.

For now, I will leave this issue open as p2 pending on CFN support but we still welcome all upvotes here from the CDK community as well.

[Bombsam]

Thanks Pahud, I have opened an issue on the cloudformation-coverage-roadmap.

Will hopefully comment once the CFN support is added.