To connect to a database instance that has the secure access proxy feature enabled, submit a ticket to request access. Once approved, DMS issues an AccessKey pair — an AccessKey ID and AccessKey secret — that your programs use to authenticate through the proxy endpoints.
If you are already an authorized user, the Permissions column on the Proxy List page shows Connection Details instead of Application. Skip this procedure and go directly to What's next to connect.
Prerequisites
Before you begin, ensure that you have:
-
Secure access proxy enabled — The database instance must have the secure access proxy feature turned on. See Enable the secure access proxy feature.
Request access
-
Log on to the DMS console V5.0.
-
Move the pointer over the
icon in the upper-left corner and choose . NoteIf you use the DMS console in normal mode, choose in the top navigation bar.
-
Move the pointer over the
icon in the upper-left corner and choose All functions > Security and Specifications > Secure Access Proxy > Proxy List.In normal mode, choose Security and Specifications > Secure Access Proxy > Proxy List in the top navigation bar.
-
On the Created tab, find the database instance and click Application in the Permissions column. DMS automatically generates a ticket to apply for access permissions.

-
After the ticket is approved, go to the Created tab, find the instance, and click Details in the Operation column. On the Secure Access Proxy/Details page, view your AccessKey ID and AccessKey secret.
Manage access credentials
After you are authorized, use the following operations to manage your AccessKey pair and permissions:
| Operation | How | Effect |
|---|---|---|
| Update the AccessKey secret | Click Update | Generates a new AccessKey secret. Programs using the previous secret can no longer access the database instance. |
| Revoke access | Click Release | Removes authorization. The user can no longer connect to the proxy endpoints of the database instance. |
What's next
Use the proxy endpoints to connect to the database instance over your preferred protocol: