Function Overview
-
RDS for MySQL
-
MySQL is one of the world's most popular open-source relational databases. It works with the Linux, Apache, and Perl/PHP/Python (LAMP) model to provide efficient web solutions. RDS for MySQL is reliable, secure, scalable, inexpensive, easy to manage, and immediately ready for use.
- It uses a stable architecture and supports various web applications. In addition, it is cost-effective and is preferred by small- and medium-sized enterprises.
- A web-based console is available for you to monitor comprehensive information, making operations easy and visual.
- Resources can be flexibly scaled and you pay for only what you use.
-
-
RDS for PostgreSQL
-
PostgreSQL is an open source object-relational database management system focused on extensibility and standards compliance. It is known as the most advanced open source database. RDS for PostgreSQL is designed for enterprise-oriented OLTP scenarios and supports NoSQL (JSON, XML, or hstore) and GIS data types. It has earned a reputation for reliability and data integrity, and is suitable for websites, location-based applications, and complex data object processing.
- RDS for PostgreSQL supports the postgis plugin and provides excellent spatial performance.
- RDS for PostgreSQL is a cost-effective solution for a range of different scenarios. You can flexibly scale resources as needed and you only pay for what you use.
-
-
Connecting to an RDS DB Instance
-
You can access RDS through Data Admin Service (DAS), a private network, or a public network.
-
Connecting to a DB Instance Through a Private Network
-
A private (floating) IP address is provided by default. If your applications are deployed on an ECS that is in the same region and VPC as your RDS DB instance, you are advised to use a private IP address to connect the ECS and RDS DB instance.
-
-
Connecting to a DB Instance Through a Public Network
-
If you cannot access a DB instance through a private IP address, bind an EIP to the DB instance first and connect the ECS to the DB instance through the EIP.
-
-
-
Data Migration
-
RDS offers various migration methods:
For MySQL instances:
- Migrate data using mysqldump
For PostgreSQL instances:
- Migrate data using psql
-
-
Resetting the Administrator Password
-
You can reset the password of your database account when using RDS. If an exception occurs on the root account, for example, the root account is lost or deleted, you can reset the root password to restore the account rights.
-
-
Enabling Public Accessibility
-
You can bind an EIP to the DB instance for public accessibility and can also unbind the EIP from the DB instance as needed.
- You can bind an EIP to a primary DB instance or a read replica only.
- If a DB instance has already been bound with an EIP, you must unbind the EIP from the DB instance first before binding a new EIP to it.
-
-
Read Replicas
-
In read-intensive scenarios, a single DB instance may be unable to handle the read pressure and service performance may be affected. To offload read pressure on the database, you can create read replicas in a region. These read replicas can process a large number of read requests and increase application throughput.
-
-
Scaling Up Storage Space
-
You can scale up storage space if it is no longer sufficient for your requirements. If the DB instance status is Storage full and data cannot be written to databases, you need to scale up storage space. The DB instance needs to preserve at least 15% of its capacity to work properly. The new minimum storage space required to make this instance available has been automatically calculated for you.
Services are not interrupted during storage scaling up. You can scale up storage space of DB instances but cannot change the storage type.
-
-
Change DB Instance Classes (CPU and memory)
-
You can change the DB instance class of a DB instance as required. If the status of a DB instance changes from Changing instance class to Available, the change is successful.
-
-
Backup and Restoration
-
Instance-level restoration: Automated or manual backups can be used to restore the entire DB instance.
-
-
Parameter Templates
-
You can use database parameter templates to manage DB engine configurations. A database parameter template acts as a container for engine configuration values that can be applied to one or more DB instances.
When creating a DB instance, you can use a default parameter template or create a custom template. After the DB instance is created, you can change the applied parameter template.
- Default parameter template
DB engine defaults and database system defaults are included in default parameter templates.
- Custom parameter template
If you want to use your custom parameter settings, you can create a parameter template and apply it with your DB instance.
- Default parameter template
-
-
SQL Auditing
-
- SQL audit is disabled by default on RDS for MySQL. Enabling this function may affect performance. After you enable SQL audit, all SQL operations will be recorded in log files for your further query and download.
- SQL audit is disabled by default on RDS for MySQL. Enabling this function may affect performance. After you enable SQL audit, all SQL operations will be recorded in log files for your further query and download.
-
-
APIs
-
RDS supports v3 APIs. You can invoke RDS APIs to perform a range of operations, such as DB instance creation and deletion, backup and restoration, and parameter query and modifications.
-
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.