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

resource_aws_redshift_cluster does not support cross-region snapshot configurations #1226

Closed
rblumen-desk opened this issue Jul 24, 2017 · 2 comments
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.

Comments

@rblumen-desk
Copy link

The AWS redshift cluster supports the following parameters relating to cross-region replication. This is how they appear in the console:

Cross-Region Snapshots EnabledWhether automated snapshots are automatically copied to another region. |(yes|no)
Cross-Region Snapshots DestinationThe region to which snapshots are copied. | (region)
Cross-Region Snapshots Retention PeriodThe number of days for which automated snapshots copied to the destination region are retained. Note that this does not apply to manual snapshots. | (number).

These parameters can be set from the CLI aws redshift enable-snapshot-copy (http://docs.aws.amazon.com/cli/latest/reference/redshift/enable-snapshot-copy.html).

The terraform implementation of resource "aws_redshift_cluster" does not provide a way to set these parameters.

@grubernaut grubernaut added the enhancement Requests to existing resources that expand the functionality or scope. label Jul 25, 2017
@bflad bflad added the service/redshift Issues and PRs that pertain to the redshift service. label Jan 28, 2018
@github-actions
Copy link

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 Mar 30, 2020
@ghost
Copy link

ghost commented May 31, 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 May 31, 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. 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
Development

No branches or pull requests

3 participants