RDS instance uses a default master username

What this check finds

Default master usernames such as "admin", "root", "master", or "postgres" are the first credentials tried in brute-force and credential-stuffing attacks against exposed RDS endpoints. A non-obvious username provides a small additional layer of defense.

Passing looks like: RDS uses a non-default master username.

How to fix it

The master username cannot be changed on an existing RDS instance. For new instances, specify a custom username during creation. To rotate on an existing instance, create a new instance with a custom master username and migrate data using DMS or a snapshot restore.

Compliance controls it is evidence for

A failing result counts against these controls in KloudLytics; a passing one is evidence towards them. How compliance mapping works

Checked on every scan

KloudLytics runs this check each time it scans a connected AWS account, through a read-only role, and lists every affected resource with its region. On Pro and Business a fix is written for the specific resource rather than the general case above. The exact access it needs

More RDS checks

• HighAurora/RDS cluster storage is not encrypted at rest
• HighRDS automated backups are disabled
• HighRDS instance does not have automatic minor version upgrades enabled
• HighRDS instance has zero database connections for 7 days
• HighRDS instance storage is not encrypted at rest
• HighRDS security group allows broad CIDR ingress (broader than /16)
• HighRDS snapshot is public
• MediumAurora/RDS cluster has automated backups disabled

All RDS checks