-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ElasticSearch] UltraWarm Elasticsearch #6462
Comments
Hi @9tontruck - Thanks for reporting this! Unfortunately, this feature is not yet supported by CloudFormation. I'm marking this request as |
Thank you! |
Any updates on this? |
@9tontruck It still is not available in CloudFormation unfortunately. I encourage you to open a feature request for CloudFormation as well. |
Reference to CloudFormation feature request: aws-cloudformation/cloudformation-coverage-roadmap#283 |
Support for CF has been published: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-elasticsearch-domain-elasticsearchclusterconfig.html |
I will implement the support for UltraWarm instances and create a pull request. |
ElasticSearch-support for UltraWarm nodes including validations for necessary pre-requirements. Closes #6462. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
ElasticSearch-support for UltraWarm nodes including validations for necessary pre-requirements. Closes aws#6462. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
I would like to make a feature request for UltraWarm Elasticsearch features.
AWS UltraWarm Elasticsearch:
https://docs.aws.amazon.com/elasticsearch-service/latest/developerguide/ultrawarm.html
The biggest benefit of UltraWarm is about 90% reduced storage cost by storing data in S3 instead of SSD.
Use Case
We are building a project that involves indexing visual features of more than 100 million images and we planned to use an Elasticsearch. Because the size of data we need to index is extremely huge, the expected resource cost is also really high. By using UltraWarm, we are expecting about 90% of storage cost drop.
Proposed Solution
When Elasticsearch is being created,
ElasticsearchClusterConfigProperty would need to accept following parameters
The text was updated successfully, but these errors were encountered: