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.

Sign up for GitHub

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

Jump to bottom

Support for exporting Redshift cluster nodes and/or IP addresses #3394

Closed
dnedev opened this issue Feb 15, 2018 · 3 comments · Fixed by #4563
Closed

Support for exporting Redshift cluster nodes and/or IP addresses #3394

dnedev opened this issue Feb 15, 2018 · 3 comments · Fixed by #4563
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/redshift Issues and PRs that pertain to the redshift service. stale Old or inactive issues managed by automation, if no further action taken these will get closed.
Milestone
v3.57.0

Comments

@dnedev
Copy link

dnedev commented Feb 15, 2018

Currently aws_redshift_cluster resources do not support exporting the cluster nodes. However it is already possible to get those back from AWS using the CLI. The cluster nodes are useful for determining the public and private IP addressed of the nodes.

While attaching an EIP seems like a possible workaround, it is quite limited when the cluster is not publicly accessible and deployed in a private subnet (which is the recommended way).

Here's a small example for to do that using the AWS CLI:
aws redshift describe-clusters --cluster-identifier <cluster-identifier>
https://docs.aws.amazon.com/redshift/latest/dg/load-from-host-steps-retrieve-key-and-ips.html

Terraform Version

+ provider.aws v1.8.0
+ provider.template v1.0.0

Affected Resource(s)

  • aws_redshift_cluster
@bflad bflad added enhancement Requests to existing resources that expand the functionality or scope. service/redshift Issues and PRs that pertain to the redshift service. labels Feb 15, 2018
@russellsherman
Copy link
Contributor

I'd like this as well, going to go ahead and take a crack at a PR

@russellsherman russellsherman mentioned this issue May 17, 2018
Merged
@github-actions
Copy link

github-actions bot commented May 6, 2020

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

@github-actions github-actions bot added the stale Old or inactive issues managed by automation, if no further action taken these will get closed. label May 6, 2020
@github-actions github-actions bot closed this as completed Jun 6, 2020
@ghost
Copy link

ghost commented Jul 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 Jul 7, 2020
@github-actions github-actions bot added this to the v3.57.0 milestone Aug 31, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/redshift Issues and PRs that pertain to the redshift service. stale Old or inactive issues managed by automation, if no further action taken these will get closed.
Projects
None yet
Milestone
v3.57.0
Development

Successfully merging a pull request may close this issue.

3394 redshift node output russellsherman/terraform-provider-aws
3 participants
@bflad @dnedev @russellsherman