Closed Aman199825 closed 6 months ago
I'll take this.
Thank you @msambol as always!
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.
Describe the feature
The OpenSearch Team allows customers to configure Cold Storage options on their cluster which is a cost efficient way to store infrequently and historical data https://docs.aws.amazon.com/opensearch-service/latest/developerguide/cold-storage.html
The CFN support for this feature is already there please refer: CFN Docs link for ColdStroageOptions
Use Case
he 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 ColdStorageOptions. This serves as a hinderance to the adoption of the ColdStorageOptions feature for AWS OpenSearch Domains.
Proposed Solution
Add a seperate field for ColdStorageOptions in the existing Domain CDK construct refer below const domain = new Domain(this, 'Domain', { version: EngineVersion.OPENSEARCH_1_0, capacity: { masterNodes: 2, warmNodes: 2, warmInstanceType: 'ultrawarm1.medium.search', }, ColdStorageOptions: { Enabled: true } });
Other Information
No response
Acknowledgements
CDK version used
2.84.0
Environment details (OS name and version, etc.)
macOS Ventura 13.4