-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Description
Describe the feature
Describe the feature
The OpenSearch Team has recently launched Coordinator Node Feature for OpenSearch Domain which can be specified under a parameter called NodeOptions in ClusterConfig. API Documentation Link. According to the CDK docs, currently there is no high level CDK construct for this feature.
Use Case
The general recommendation is to use high level constructs and due to lack of High level construct for this feature. The CDK template needs to be migrated to use CFN constructs if there is a need to create an OpenSearchDomain with NodeOptions. This serves as a hindrance to the adoption of the Coordinator Node feature for AWS OpenSearch Domains.
Proposed Solution
Add the NodeOptions to the Domain high level object under ClusterConfig CDK Doc for Domain Options .
A NodeOptions based OpenSearchDomain created using CDK high level constructs should look like
const domain = new Domain(this, 'Domain', {
version: EngineVersion.OPENSEARCH_1_0,
clusterConfig: {
nodeOptions: [{
nodeType: 'coordinator' (possible values: [coordinator])
nodeConfig: {
enabled: true, (boolean)
type: 'm5.xlarge.search', (string)
count: 1 (number)
}
}]
}
});
Other Information
No response
Acknowledgements
- I may be able to implement this feature request
- This feature might incur a breaking change
CDK version used
NA (Yet to be updated)
Environment details (OS name and version, etc.)
macOS Venture 13.7.1