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

r/aws_elasticache_cluster: fix transit_encryption_enabled for redis #33451

Merged
merged 2 commits into from
Sep 14, 2023
Merged

r/aws_elasticache_cluster: fix transit_encryption_enabled for redis #33451

merged 2 commits into from
Sep 14, 2023

Commits on Sep 13, 2023

  1. r/aws_elasticache_cluster: fix transit_encryption_enabled for redis 

    - Removes the default `false` value and makes the argument optional and computed. For `redis` engine types the value will effectively always be computed.
- Removes the `CustomizeDiff` function focused on the `transit_encryption_enabled` attribute, instead relying on the native AWS errors to provide the same feedback.

1. AWS error for minimum supported memcached version check:
```
Error: creating ElastiCache Cache Cluster (jb-test-memcached): InvalidParameterCombination: Encryption features are not supported for engine version 1.6.6. Please use engine version 1.6.12
```
2. AWS error when attempting to create a `redis` cluster with `transit_encryption_enabled` set (must be set on replication group instead):
```
Error: creating ElastiCache Cache Cluster (jb-test-redis): InvalidParameterCombination: Encryption feature is not supported for engine REDIS.
```
    @jar-b
    jar-b committed Sep 13, 2023
    Configuration menu
    Copy the full SHA
    11d7933 View commit details
    Browse the repository at this point in the history

  2. chore: changelog

    @jar-b
    jar-b committed Sep 13, 2023
    Configuration menu
    Copy the full SHA
    17138db View commit details
    Browse the repository at this point in the history