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

Establish how RDS database credentials should be managed #64

Open
3 tasks
Tracked by #75
robinglov opened this issue Mar 23, 2024 · 3 comments
Open
3 tasks
Tracked by #75

Establish how RDS database credentials should be managed #64

robinglov opened this issue Mar 23, 2024 · 3 comments

Comments

@robinglov
Copy link
Member

robinglov commented Mar 23, 2024

Overview

As an Ops team, we need consistency between project environments to increase security and reduce errors in production code.

Action Items

  • Determine who should have access to the database
  • Research pricing
  • How should database credentials be managed?

Resources/Instructions

@ExperimentsInHonesty
Copy link
Member

Hi Leads. Is this issue ready for prioritization? Does it have enough info. I will also need help with the labels.

@ale210
Copy link

ale210 commented Oct 31, 2024

Come up with a strategy - examples could be using secrets/tags/iam to allow users to access db credentials etc

@lsousadev
Copy link
Member

An idea is to use IAM users to login to the DB (the DB proper, not only access to RDS service) instead of classic db user/pw:

https://medium.com/@tizattogabriel/how-to-authenticate-to-an-aws-rds-postgresql-db-instance-using-iam-credentials-4e69b095c01c

Need to investigate whether this would work for IAM roles (for apps/resources)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: New Issue Review
Development

No branches or pull requests

4 participants