Skip to content
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

Can't use i3 instance type with Elasticsearch #203

Open
CVirus opened this issue Jul 6, 2020 · 2 comments
Open

Can't use i3 instance type with Elasticsearch #203

CVirus opened this issue Jul 6, 2020 · 2 comments
Labels

Comments

@CVirus
Copy link

CVirus commented Jul 6, 2020

Describe the bug
I'm trying to deploy an elasticsearch domain with the following configuration and it is failing:

    CidrSize: 27
    EngineVersion: 6.7
    ESDomainName: "graylog-cvirus-test"
    NodeAvailabilityZones: 2
    NodeInstanceType: i3.xlarge.elasticsearch
    StorageType: standard
    NodeInstanceCount: 6
    DedicatedMasterInstanceType: c5.large.elasticsearch
    DedicatedMasterInstanceCount: 3
    PreferredSnapshotTime: 0
    NodeToNodeEncryption: true
    EncryptionAtRest: true

The error:
CloudFormationError; Description: ElasticsearchDomain Instance type i3.xlarge.elasticsearch does not support EBS storage

Expected behavior
I expect ES domain to be created.

Environment:

  • Application Platform: Kubernetes
  • Application Platform Version: k8s 1.16.8
  • Broker Version:1.0.1
@rniksch
Copy link
Contributor

rniksch commented Jul 22, 2020

Looking into this as a possible change that need to be made to the template. so when selecting i3 instance types that the correct storage match is done. https://docs.aws.amazon.com/elasticsearch-service/latest/developerguide/aes-supported-instance-types.html

I just want to confirm your requirements:
do you specifically need the i3 instance type? can you provide some detail on the use case vs other instance type?

and do you have specific requirements around the storage ?

having this info will help us cater for customer use cases

@CVirus
Copy link
Author

CVirus commented Jul 24, 2020

@rniksch Thanks for your reply. We decided on i3 instance type because we were migrating an old elasticsearch cluster that is already using them. i3 was decided for because it comes with its own storage.
Since the broker CF template didn't support that; we decided to go for r5 instances + EBS storage.
I came to realize that the CF template is not flexible enough and at some point we're going to end up creating our own catalog with our own templates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants