Update Redis config to support encryption in transit with AWS ElastiCache #4258
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Any background context you want to provide?
This is a bug fix with port not being provided for AWS Elasitache Redis.
What's this PR do?
Fixes bug to use AWS Elasticache Redis.
How should this be manually tested?
Delay to AWS Environment with Elasticache Cluster and provide REDIS_HOST
What are the relevant tickets?
Screenshots (if appropriate)