How do you configure database permissions for an Atlas application user?
Grant the application the database access it needs and verify both allowed and denied operations.
How do you configure database permissions for an Atlas application user?
A database identity should match the application’s responsibilities. Broad administrative access makes an ordinary application bug more consequential.
Choose scoped privileges
Atlas database users have roles that determine their access. Select privileges for the intended database and operations, and use separate identities for separate environments or responsibilities where appropriate. Do not confuse permission to manage the Atlas project with permission to read and write application data.
Test the intended boundary
Run representative operations using the application’s identity, including one operation it should not be able to perform. Document which deployment uses the credential and how it will be rotated. Keep credentials outside logs and source control. If a permission error occurs, identify the missing operation instead of immediately granting administrator access. Review access when the application’s responsibilities change.
Further reading: Atlas database-user configuration.
They grant capabilities beyond the application’s ordinary needs and increase the impact of mistakes or compromise.
Identify the operation and resource involved, then adjust only the required privileges.
Prefer separate identities and scopes so testing does not inherit production access.
Related learning resources
Ready to master AI completely?
Want to upskill yourself, crack your next interview, and get your dream job? Join our comprehensive course to dive deeper with high-quality video tutorials, solve interview questions, and a premium community.
Master AI
Want to upskill yourself, crack your next interview, and get your dream job? Join our comprehensive course.