Introduce a read-only user for data-replication#4551
Closed
TheOneFromNorway wants to merge 7 commits intonextfrom
Closed
Introduce a read-only user for data-replication#4551TheOneFromNorway wants to merge 7 commits intonextfrom
TheOneFromNorway wants to merge 7 commits intonextfrom
Conversation
TheOneFromNorway
had a problem deploying
to
qa
GitHub Actions
Failure
TheOneFromNorway
force-pushed
the
ro_user_for_data_replication
branch
from
287fe11 to
b07f54f
Compare
thomasleese
reviewed
Sep 9, 2025
TheOneFromNorway
force-pushed
the
ro_user_for_data_replication
branch
2 times, most recently
from
5610a96 to
e50a8b4
Compare
bogsi17
reviewed
Sep 9, 2025
TheOneFromNorway
force-pushed
the
ro_user_for_data_replication
branch
from
38b1af1 to
97eba3d
Compare
TheOneFromNorway
had a problem deploying
to
qa
GitHub Actions
Failure
TheOneFromNorway
had a problem deploying
to
qa
GitHub Actions
Failure
TheOneFromNorway
force-pushed
the
ro_user_for_data_replication
branch
2 times, most recently
from
b1abf55 to
579ae58
Compare
thomasleese
reviewed
Sep 25, 2025
- User must be created within aws account due to database living in private subnet - For simplicity just create user on startup of application if does not already exist - Password is managed via terraform and injected into container
- Security group to handle incoming/outgoing connections to grafana - Grafana now has connection to VPC allowing DB access - To reliably reference data-replication resources new tags have been included
- Permissions are generic enough to go into general deploy permission set
- Also ensure ECS service can access s3 endpoint - Due to NAT gateway an s3 gateway is no longer needed
- Leave password/url as manual steps to fill for now
- Expand out names for clarity in code - Keep `_ro` suffix as standard indicator for read only permissions on db user
TheOneFromNorway
force-pushed
the
ro_user_for_data_replication
branch
from
579ae58 to
ef49ad3
Compare
|
thomasleese
approved these changes
Sep 25, 2025
Contributor
Author
|
Closed as this will be implemented after infrastructure code is refactored out into its own repository |
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
3 participants
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.
JIRA Ticket: MAV-1941