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

[Elasticache] - Support enabling Encryption in transit on existing clusters #1103

Closed
dhumphries-sainsburys opened this issue Jan 22, 2024 · 3 comments
Labels
enhancement New feature or request

Comments

@dhumphries-sainsburys
Copy link

What problem are you facing?

Redis 7.0 onwards supports enabling encryption in transit on an existing cluster or replication group but this doesn't seem to be allowed in the provider with the below:

        async update failed: refuse to update the external resource: cannot
        change the value of the argument "transit_encryption_enabled" from
        "false" to "true"

[1]
[2]

How could Official AWS Provider help solve your problem?

Support the ability to switch between encrypted transit being false to true

@turkenf
Copy link
Collaborator

turkenf commented Jan 23, 2024

Hi @dhumphries-sainsburys,

Changing this field requires deleting and recreating the existing resource due to the behavior of the underlying provider.

According to the Crossplane Resource Model, this is something we do not allow.

@turkenf
Copy link
Collaborator

turkenf commented Jan 25, 2024

Since this is to be expected, I am closing this issue. Upstream issue with rejecting change requests for immutable fields.

@turkenf turkenf closed this as completed Jan 25, 2024
@dhumphries-sainsburys
Copy link
Author

Now this is supported upstream is this now supported by the provider?

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

No branches or pull requests

2 participants