ApsaraDB RDS supports two types of endpoints: internal endpoints and public endpoints. By default, you are provided with an internal endpoint that is used to connect to your ApsaraDB RDS for MySQL instance. If you want to connect to your RDS instance over the Internet, you must apply for a public endpoint.

For more information about how to apply for or release public endpoints for RDS instances that run other database engines, see the following topics:

Internal and public endpoints

Endpoint type Description
Internal endpoint
  • An internal endpoint is provided by default. You do not need to apply for this endpoint. In addition, you cannot release this endpoint. However, you can change the network type of your RDS instance.
  • If an Elastic Compute Service (ECS) instance resides in the same region and has the same network type as your RDS instance, these instances can communicate over an internal network. If your application is deployed on such an ECS instance, you do not need to apply for a public endpoint. For more information, see Change the network type of an ApsaraDB RDS for MySQL instance.
  • For security and performance purposes, we recommend that you connect to your RDS instance by using the internal endpoint.
Public endpoint
  • You must manually apply for a public endpoint. You can release this endpoint if it is no longer required.
  • If you cannot connect to your RDS instance by using the internal endpoint, you must apply for a public endpoint. This includes the following scenarios:
    • Connect to your RDS instance from an ECS instance that resides in a different region or has a different network type from your RDS instance. For more information, see Change the network type of an ApsaraDB RDS for MySQL instance.
    • Connect to your RDS instance from a device that resides outside Alibaba Cloud.
Note
  • You are not charged for the public endpoint or the traffic that is consumed.
  • If you connect to your RDS instance by using the public endpoint, security is compromised. Proceed with caution.
  • We recommend that you migrate your application to an ECS instance that resides in the same region and has the same network type as your RDS instance. This allows you to connect to your RDS instance by using the internal endpoint. The connection expedites transmission and improves security.

Procedure

  1. Access RDS Instances, select a region at the top, and then click the ID of the target RDS instance.
  2. In the left-side navigation pane, click Database Connection.
  3. Apply for or release a public endpoint for your RDS instance:
    • If you have not applied for a public endpoint, you can click Apply for Public Endpoint.
    • If you have applied for a public endpoint, you can click Release Public Endpoint.
  4. In the message that appears, click OK.

FAQ

  • Can I change the endpoints and ports of my RDS instance?

    No, you cannot change the endpoints of your RDS instance. You can change the prefixes of the endpoints. In addition, you can change the ports of your RDS instance. For more information, see View and change the internal and public endpoints and port numbers of an ApsaraDB RDS for MySQL instance.

  • Can I configure the endpoints of my RDS instances to static IP addresses?

    No, you cannot configure the endpoints of your RDS instance to static IP addresses. Both primary/secondary switchovers and specification changes may cause changes to the IP addresses. Therefore, we recommend that you connect to your RDS instance by using an endpoint. This allows you to minimize the impact on your workloads and relieves the need to modify the configuration data on your application.

  • How do I connect to my RDS instance by using the public endpoint?

    For more information, see Use a database client or the CLI to connect to an ApsaraDB RDS for MySQL instance.

Related operations

Operation Description
Apply for public endpoint Applies for a public endpoint for an ApsaraDB RDS instance.
Release a public endpoint Releases the public endpoint of an ApsaraDB RDS instance.