Closed
Conversation
gherceg
commented
Aug 20, 2025
gherceg
force-pushed
the
gh/elasticache/celery-broker
branch
7 times, most recently
from
dc5d060 to
f6eb31b
Compare
gherceg
force-pushed
the
gh/elasticache/celery-broker
branch
2 times, most recently
from
2a6356f to
0a5c541
Compare
gherceg
force-pushed
the
gh/elasticache/celery-broker
branch
2 times, most recently
from
9bf2345 to
e75bb17
Compare
Matches Rabbit config
For whatever reason, memory is only up to 13.07 GB on this machine type which means we might run into issues on staging, but figure we can cross that bridge if/when we get there.
Created the r53 record via AWS, not terraform
gherceg
force-pushed
the
gh/elasticache/celery-broker
branch
from
e75bb17 to
5785dc2
Compare
Contributor
Author
|
No longer relevant as this has been rolled out to staging in other PRs. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
https://dimagi.atlassian.net/browse/SAAS-18360
Prototyping using elasticache for celery broker on staging. As noted in the ticket, our version of aws terraform provider doesn't support specifying valkey despite it being supported by elasticache, so I'm just moving forward with redis for the sake of testing this.
Environments Affected
Staging