(opensearch): Some configuration options are not available for use
- Dominant language
- TypeScript
- Stars
- 12.9k
- Forks
- 4.6k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 83
Description
### Describe the feature
This is duplicated from https://github.com/aws/aws-cdk/issues/16575 which should not have been closed. This is blocked on [Cloudformation support](https://github.com/aws-cloudformation/cloudformation-coverage-roadmap/issues/832), but should be added once this support is available.
It is not possible to disable Auto-Tune when creating a new OpenSearch domain.
### Use Case
To allow use of domains without Auto-Tune. To allow for use of cheap instances that don't support Auto-Tune without custom resources or other hacks.
### Proposed Solution
Once Cloudformation supports Auto-Tune, expose the parameter in the CDK construct.
### 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.110.1
### Environment details (OS name and version, etc.)
Ubuntu (Windows Subsystem for Linux)
Contributor guide
Research direction
First verify whether CloudFormation support has landed for the Auto-Tune setting in coverage-roadmap issue 832. Then locate the AWS CDK OpenSearch domain construct and its tests; done means exposing the setting once the underlying CloudFormation property is available. No file or test path is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100