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

VPC access to Elastic Search #1949

Closed
iceycake opened this issue Oct 17, 2017 · 10 comments
Closed

VPC access to Elastic Search #1949

iceycake opened this issue Oct 17, 2017 · 10 comments
Labels
enhancement Requests to existing resources that expand the functionality or scope.

Comments

@iceycake
Copy link
Contributor

ElasticSearch can be finally able to be accessed from VPC (https://aws.amazon.com/about-aws/whats-new/2017/10/amazon-elasticsearch-service-announces-support-for-amazon-virtual-private-cloud-vpc/). The required aws-sdk-go is also available (aws/aws-sdk-go@044a61f)

Probably not too difficult to implement that in terraform.

@stuartgrice
Copy link

+1

@handlerbot
Copy link
Contributor

Since I forget if GitHub sends email when a PR references an issue: Please see #1958 if you are interested.

@FrederikNygaardSvendsen

+1

@radeksimko radeksimko added the enhancement Requests to existing resources that expand the functionality or scope. label Oct 23, 2017
@grems6
Copy link

grems6 commented Oct 25, 2017

+1

@handlerbot
Copy link
Contributor

(My PR was merged, this can be closed.)

@Ninir
Copy link
Contributor

Ninir commented Oct 26, 2017

Thanks for the ping @handlerbot :)

@Ninir Ninir closed this as completed Oct 26, 2017
@handlerbot
Copy link
Contributor

@Ninir Anything that helps bring that large issues number down. ;-) BTW, is there guidelines / a schedule board yet for when a new AWS provider release will be cut? From the outside, the timing process looks pretty opaque, and it's hard to tell if I should do my work with a custom-compiled provider, or wait for an imminent official release, etc.

@Ninir
Copy link
Contributor

Ninir commented Oct 26, 2017

We try to release the provider twice a month, which is our will. It mainly depends on the work in the pipe: sometimes we do want to include specific work, and wait until it's ready. When the given work takes too much time, it is delayed to the next milestone.

Please note it's hard to engage on a specific timeline for that, but we do our best to stick to that.

We still need to do a better work here on our side, but things are getting into shape for these bi-releases a month :)

@handlerbot
Copy link
Contributor

@Ninir Excellent info, thanks! I'd be even more interested in signing up for Enterprise if we could get insight into blockers/soft targets for the next milestone, so plz feed that back upstream if that helps. ;-)

Would you say we're on track for an AWS provider release around the start of November?

@ghost
Copy link

ghost commented Apr 10, 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 10, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Requests to existing resources that expand the functionality or scope.
Projects
None yet
Development

No branches or pull requests

7 participants