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

Avoid having application servers provision the RDS root user's password #69

Open
tinnightcap opened this issue Apr 27, 2017 · 4 comments
Labels

Comments

@tinnightcap
Copy link
Contributor

From @gene1wood on November 3, 2015 23:55

Thanks so much for sharing how the RDS root password provisioning works in issue #98. Based on how the RDS root user password provisioning works, the application servers which set the root user's password, as a result, have root MySQL user access to the RDS database when they only need the access that the application user that they use is granted (e.g. no rights to create and delete other MySQL users).

Please provision the RDS root user's password through a different means to avoid this unnecessary privilege being granted to RDS clients.

Copied from original issue: tinnightcap/nubis-stacks#219

@tinnightcap
Copy link
Contributor Author

From @gdestuynder on November 3, 2015 23:59

@tinnightcap @RichardWeiss can you confirm that for all 4 apps in Nubis plan B there is only 1 or no database user per app (which means not having separate RDS users is a lower risk)?
These 4 apps being:

  • EDNS/akamai
  • Bugzilla
  • LDAP Okta Agent
  • LDAP master

The risk would be higher for future app is these use multiple users.

@tinnightcap
Copy link
Contributor Author

From @gozer on November 4, 2015 0:1

Only bugzilla uses a database, and it's going to be MySQL-on-ec2, so no more RDS at all, technically

@tinnightcap
Copy link
Contributor Author

From @RichardWeiss on November 4, 2015 0:12

Confirming that it is only the Bugzilla database and that will be the only application running in that account.

@tinnightcap
Copy link
Contributor Author

From @gdestuynder on November 4, 2015 0:19

thanks! lowered risk accordingly, we'll probably revisit that for future apps (thus i'd recommend leaving this one issue open)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant