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

aws_elasticsearch_domain: vpc_options - subnet_ids asks for list but can only be a single value. #2333

Closed
ccslamstack opened this issue Nov 17, 2017 · 3 comments

Comments

@ccslamstack
Copy link

ccslamstack commented Nov 17, 2017

AWS released the new VPC endpoint feature for ElasticSearch:
vpc_options:
subnet_ids - (Required) List of VPC Subnet IDs for the Elasticsearch domain endpoints to be created in.

This can only accept a single subnet-id currently, was this added as a list for future development for multiple subnet-id's?

Also can an attribute be created to specify the vpc-id?

@devopsrick
Copy link

Any reason this was closed without comment? Definitely still a bug, which I just ran into. At minimum documentation really should be updated to correctly state only a single subnet is supported!

@rajdev127
Copy link

@rickrdvaughn enabling zone awareness will allow you to point to two or more subnets.

set
cluster_config {
zone_awareness_enabled = true
}

``If you enable zone awareness for your domain, Amazon ES places an endpoint into two subnets. The subnets must be in different Availability Zones in the same region. If you don't enable zone awareness, Amazon ES places an endpoint into only one subnet```

https://docs.aws.amazon.com/elasticsearch-service/latest/developerguide/es-vpc.html

@ghost
Copy link

ghost commented Apr 7, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!

@ghost ghost locked and limited conversation to collaborators Apr 7, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants