opensearch: add throughput to EbsOptions

[richardwu]

Describe the feature

The interface EbsOptions for the opensearchservices CDK construct is missing a provisioned throughput option for eg gp3 instance types.

iops is there, but not throughput (which can be configured in the web console.

Use Case

To configure provisioned throughput in CDK.

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.83.1

Environment details (OS name and version, etc.)

macOS

[pahud]

Yes we can add this in the EbsOptions interface:

aws-cdk/packages/aws-cdk-lib/aws-opensearchservice/lib/domain.ts

Lines 113 to 149 in 0e251e6

	export interface EbsOptions {
	/**
	* Specifies whether Amazon EBS volumes are attached to data nodes in the
	* Amazon OpenSearch Service domain.
	*
	* @default - true
	*/
	readonly enabled?: boolean;
	/**
	* The number of I/O operations per second (IOPS) that the volume
	* supports. This property applies only to the Provisioned IOPS (SSD) EBS
	* volume type.
	*
	* @default - iops are not set.
	*/
	readonly iops?: number;
	/**
	* The size (in GiB) of the EBS volume for each data node. The minimum and
	* maximum size of an EBS volume depends on the EBS volume type and the
	* instance type to which it is attached. For valid values, see
	* [EBS volume size limits]
	* (https://docs.aws.amazon.com/opensearch-service/latest/developerguide/limits.html#ebsresource)
	* in the Amazon OpenSearch Service Developer Guide.
	*
	* @default 10
	*/
	readonly volumeSize?: number;
	/**
	* The EBS volume type to use with the Amazon OpenSearch Service domain, such as standard, gp2, io1.
	*
	* @default gp2
	*/
	readonly volumeType?: ec2.EbsDeviceVolumeType;
	}

Making this a p2 feature request and we welcome community pull requests for this.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.