Check ID:
Provider: AWS
Service:
Severity: HIGH
Categories:
Resource type:
rds_instance_deprecated_engine_versionProvider: AWS
Service:
rdsSeverity: HIGH
Categories:
vulnerabilitiesResource type:
AwsRdsDbInstanceWhat this check verifies
RDS DB instances use a supported, non-deprecated engine version for MariaDB, MySQL, or PostgreSQL. The instance’sengine and engine_version are evaluated against versions currently supported in the region.
Risk
Deprecated engine versions lack security fixes and support, enabling exploitation of known flaws impacting confidentiality and integrity. Availability can suffer from forced maintenance or failed upgrades.- Unpatched CVEs
- TLS/client incompatibilities
- Replication or backup/restore issues
Recommendation
Standardize on supported engine versions and keep them current.- Plan and test upgrades; back up and define rollback
- Enable
AutoMinorVersionUpgradewhere acceptable - Monitor deprecation notices and upgrade before EoS
- Enforce least privilege to limit blast radius during incidents
Remediation
- CLI
- Terraform
- Native IaC
- Dashboard steps
aws rds modify-db-instance —db-instance-identifier <DB_INSTANCE_ID> —engine-version <SUPPORTED_ENGINE_VERSION> —allow-major-version-upgrade —apply-immediately
References
Where this check fires
This check runs on every scheduled scan against your AWS account. Findings appear at Cloud Security → Findings filterable byCheck ID = rds_instance_deprecated_engine_version. To re-evaluate after a fix, hit Run now on the account’s schedule under Cloud Security → Schedules — the next scan re-checks this control and marks the finding fixed or keeps it persistent.
← Back to AWS checks