(elasticsearch) instance type and ebs validation doesn't distinguish data and master node during domain creation.
See original GitHub issueWhen trying to create Elasticsearch domain with master node type c5.2xlarge.elasticsearch
, data node type i3.2xlarge.elasticsearch
, with ebs disabled, cdk throws exception says
throw new Error('EBS volumes are required when using instance types other than r3 or i3.');
If I enable ebs, it throws exception:
throw new Error('I3 instance types do not support EBS storage volumes.');
The version I am using is 1.76.
From API reference, the ebs suppose to be only attached to master node in my case, however the validation couldn’t distinguish data node and master node. With my instance config, it thinks c5 should have ebs, but i3 shouldn’t.
c5 is recommended for master node, and i3 for data node. With this bug, there is no way to use CDK to create Elasticsearch domain with master nodes.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:13 (5 by maintainers)
Top Results From Across the Web
Supported instance types in Amazon OpenSearch Service
Amazon OpenSearch Service supports the following instance types. Not all Regions support all instance types. For availability details, see Amazon OpenSearch ...
Read more >Making configuration changes in Amazon OpenSearch Service
Enabling fine-grained access control. Performing service software updates. If your domain doesn't have dedicated master nodes, changing data instance count.
Read more >Use Amazon Elasticsearch Service to Log and Monitor ...
Pushing Log data from EC2 instances into Amazon ES . ... configure a search domain by creating and managing a multi-node Elasticsearch cluster...
Read more >Goodbye AWS OpenSearch, hello self-hosted ElasticSearch ...
Create ES Node AMI. The ES instance is now in a state ready to be reused for creating multiple master and data nodes...
Read more >Elasticsearch Service - LocalStack Docs
Creating an Elasticsearch cluster. You can go ahead and use awslocal to create a new elasticsearch domain via the aws es create-elasticsearch- ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@AlvinMengCao Thanks.
You’re right, seems like the console does make this distinction and your configuration is valid:
We will look into it, might indeed be a CloudFormation only validation.
Thanks for reporting!
If there is a way to +1 this issue, I would like to add mine. We are using i3 for data nodes, and m5 for masters. The current ES Domain construct does not allow for this mix – and unfortunately it is one we already have in production. This was originally created without issue using the
cfnDomain
construct, so I am not at all sure how this construct missed that you can define data and master nodes separately. @iliapolo Thank you for your workaround, but this bug has now been around for several months, is there any update?