RDS Database Snapshots Should Not Be Public
Your AWS Relational Database Service (RDS) database snapshots should not be publicly accessible. This is to avoid exposing your private data.
Your AWS Relational Database Service (RDS) database snapshots should not be publicly accessible. This is to avoid exposing your private data.
Amazon Aurora databases should be protected from accidental deletion. This is done by having Deletion Protection feature enabled at the database cluster level.
Amazon RDS sends general, slow query, audit and error logs from your MySQL, Aurora and MariaDB databases to AWS CloudWatch Logs. Broadcasting these logs to CloudWatch allows you to maintain continuous visibility into database activity, query performance and errors within your RDS database instances.
Aurora Serverless databases should have Log Exports feature enabled in order to publish general logs, slow query logs, audit logs and error logs to AWS CloudWatch.
Amazon RDS provides a Deletion Protection Flag which should be enabled to prevent accidental prevention of the database.
Automated backups of your RDS database instances should be enabled to ensure point-in-time recovery.
Port obfuscation is as an additional layer of defense against non-targeted attacks. In order to leverage this, your Amazon RDS databases instances should not use their default ports (MySQL/Aurora port 3306, SQL Server port 1433, PostgreSQL port 5432)
It is recommended that RDS database instances use instance types from a limited set based on the database workload deployed.
RDS database instances should be encrypted to fulfill compliance requirements for data-at-rest encryption.
If your RDS databases are running low on disk space, they introduce a high risk of hurting your performance and availability.
AWS account has Limit Quotas on every service including RDS. The number of RDS database instances provisioned in your AWS account should not have reached the limit quota.
It is not a good practice to use awsuser or admin as master username for your database connection. Instead, use unique alphanumeric username.
RDS database instances provisioned in your AWS account should not be publicly accessible and should instead restrict unauthorized access in order to minimise security risks.
As an organization you should have a backup policy with atleast minimum 7 days.
If your RDS instance and it's security group allows access to everyone by setting 0.0.0.0/0, then it invites malicious users to target your database and make your security posture more vulnerable.
All the database instances within your Amazon Aurora clusters should have the same accessibility (either public or private) in order to follow AWS best practices.
Backtrack feature should be enabled for your Amazon Aurora with MySQL compatibility database clusters in order to backtrack your clusters to a specific time, without using backups
All RDS databases instances provisioned within your AWS account should be using the latest generation of instance classes in order to get the best performance with lower costs.
Microsoft SQL Server and PostgreSQL instances provisioned with Amazon RDS should have Transport Encryption feature enabled in order to meet security and compliance requirements
Your Amazon Relational Database Service (RDS) snapshots should be encrypted in order to achieve compliance for data-at-rest encryption within your organization
IAM Database Authentication feature should be enabled in order to use AWS Identity and Access Management (IAM) service to manage database access to your Amazon RDS MySQL and PostgreSQL instances
Identify any Amazon RDS database instances that appear to be idle and delete them to help lower the cost of your monthly AWS bill
Amazon RDS event notification subscriptions should be enabled for database instance level events.
Identify any Amazon RDS database instances that appear to be overutilized and upgrade (upsize) them to help handle better the database workload and improve the response time
Your AWS RDS MySQL and PostgreSQL database instances should have Performance Insights feature enabled in order to allow you to obtain a better overview of your databases performance
Your RDS database instances should have the Auto Minor Version Upgrade flag enabled in order to receive automatically minor engine upgrades during the specified maintenance window
RDS instances should make use of Copy Tags to Snapshots feature in order to allow tags set on database instances to be automatically copied to any automated or manual RDS snapshots that are created from these instances
Your RDS database instances should be using KMS CMK customer-managed keys rather than AWS managed-keys in order to have more granular control over your data-at-rest encryption/decryption process.
Your AWS RDS resources should have event notifications enabled in order to be notified when an event occurs for a given database instance, database snapshot, database security group or database parameter group
Your RDS instances should be using General Purpose SSDs instead of Provisioned IOPS SSDs for cost-effective storage that fits a broad range of database workloads
No AWS RDS database instances should be provisioned inside VPC public subnets in order to protect them from direct exposure to the Internet
Your RDS clusters should be using Multi-AZ deployment configurations for high availability and automatic failover support fully managed by AWS.
Your AWS RDS Reserved Instances (RIs) should be renewed before expiration in order to get the appropriate discount on the hourly charge for these instances
Your AWS RDS Reserved Instances (RIs) should be renewed before expiration in order to get the appropriate discount on the hourly charge for these instances
Identify any failed RDS Reserved Instances (RIs) available within your AWS account. A failed RDS RI is an unsuccessful reservation that received the "payment-failed" status during the purchase process.
Identify any pending RDS Reserved Instance (RI) purchases available within your AWS account. A payment-pending RDS RI purchase is a reservation purchase that cannot be fully processed due to issues with the payment method
All Amazon RDS Reserved Instance (RI) purchases are reviewed every 7 days in order to confirm that no unwanted reservation purchase has been placed recently.
Amazon RDS event notification subscriptions should be enabled for database security groups events. AWS RDS groups these events into categories that you can subscribe to.
Identify any Amazon RDS database instances that appear to be underutilized and downsize (resize) them to help lower the cost of your monthly AWS bill
All your AWS RDS Reserved Instances (RI) should have corresponding database instances running within the same account or within any AWS accounts members of an AWS Organization
Amazon Backup should be integrated with Amazon Relational Database Service (RDS) in order to manage RDS database instance snapshots and improve the reliability of your backup strategy.
If you are not yet convinced to sign up with Cloudanix, that's not a problem. We recommend you use a comprehensive checklist which your team can use to perform a manual assessment of your workload.