Introduction
In this blog, we will learn about AWS DMS endpoints. An endpoint is a source of connection, holder of type of data store, and storage space for local information. AWS DMS is a service that utilizes this information to form a connection with the data store and facilitates data migration between source and target endpoints. Extra connection attributes control log, file size, and some other parameters. So now, let us start with first understanding how we can create source and target endpoints.
Creating Source and Target Endpoints
To create a source endpoint, we must create a replication instance first. With assumption, AWS DMS console wizard has been chosen; follow the below procedure to create source and target endpoints.
If you use console wizard, you can create endpoints on the same page, while endpoints are created differently on separate pages if we do not use Console Wizard.
Step 1
Mention the connect information for the databases, source, and target on the ‘Connect source and target database endpoints’ page. The following table specifies the compulsory settings.
OPTION |
CHOICE |
| Endpoint Type | Either choose source or target as per which is required. |
| RDB DB Instance | Choose this option only if an endpoint is an Amazon RDB DB Instance. |
| Endpoint Identifier | Mention the name you want to use to identify the endpoint. Names should be unique for every replication instance. |
| Database Engine | Choose the type of database engine as per the requirement of endpoint, that is, source or target. |
| Access to endpoint database |
Select the option that specifies endpoint database credentials.
|
| AWS Secrets Manager | To set the secret credentials. |
| Secret ID | You can type here full ARN, that is, Amazon Resource Name or Partial ARN or any friendly name you might have given for endpoint database access in Secrets Manager. |
| Secret ID for Oracle ASM | You can type here full ARN, that is, Amazon Resource Name or Partial ARN or any friendly name you might have given for Oracle ASM access in Secrets Manager. |
| IAM Role | Fill here the ARN of the secret access role created to provide AWS DMS access in IAM. |
| IAM Role for Oracle ASM | Fill here the ARN of the secret access role created to provide AWS DMS access in IAM for Oracle ASM. |
| Access Information | Set the credentials to provide access to information manually. |
| Server Name | Fill in the server name, which can be the IP address or the public hostname. |
| Port | Here, the details of the port used by the database will be entered. |
| SSL Mode | SSL stands for Secure Socket Layer. For connection encryption to be enabled for the endpoint, we select SSL Mode. You might also have to provide a server certificate or its information here. |
| User Name | Fill in the username with the required permissions. |
| Password | Fill in the password with the required information. |
| Database Name | In certain database engines, you are also required to fill in name of the database you want to use endpoint database. |
We cannot use some characters in the endpoint passwords of certain database engines. These characters are mentioned below-
- Microsoft Azure- ‘;’
- Microsoft SQL Server- ‘, and;’
- MySQL, MariaDB, Amazon Aurora MySQL- ‘;’
- Oracle- ‘,’
- Postgre SQL, Amazon Aurora, Amazon Aurora Serverless- ‘; and + and %’
- Amazon Redshift-, and ;
Step 2
For Extra connection attributes and AWS KMS key, if required, go for the Advanced Tab.
OPTION |
CHOICE |
| Extra Connection Attributes | Here additional parameters would be filled. |
| AWS KMS key | Choose the suitable credentials with the required information. |
| Test Endpoint Connection (optional) | For this, you have to add VPS and replication instance name, then select Run Test. |
To check if the endpoint connection works properly or not, choose the ‘Run Test’ option.
569+ registered 
