# Database Migration Service (DMS) \$1 Create Replication Instance
Create a Database Migration Service (DMS) replication instance on an Amazon EC2 instance in an AMS VPC. Use the replication instance to perform your database migration. The replication instance provides high availability and failover support using a Multi-AZ deployment when you select the Multi-AZ option.
**Full classification:** Deployment \$1 Advanced stack components \$1 Database Migration Service (DMS) \$1 Create replication instance
## Change Type Details
****
| | |
| --- |--- |
| Change type ID | ct-27apldkhqr0ol |
| Current version | 1.0 |
| Expected execution duration | 60 minutes |
| AWS approval | Required |
| Customer approval | Not required |
| Execution mode | Automated |
## Additional Information
### Create AWS DMS replication instance
#### Creating a AWS DMS replication instance with the console
Screenshot of this change type in the AMS console:
![\[Database Migration Service (DMS) replication instance creation details with ID and version.\]](http://docs.aws.amazon.com/managedservices/latest/ctref/images/guiDmsCreateRepInstanceCT.png)
How it works:
1. Navigate to the **Create RFC** page: In the left navigation pane of the AMS console click **RFCs** to open the RFCs list page, and then click **Create RFC**.
1. Choose a popular change type (CT) in the default **Browse change types** view, or select a CT in the **Choose by category** view.
+ **Browse by change type**: You can click on a popular CT in the **Quick create** area to immediately open the **Run RFC** page. Note that you cannot choose an older CT version with quick create.
To sort CTs, use the **All change types** area in either the **Card** or **Table** view. In either view, select a CT and then click **Create RFC** to open the **Run RFC** page. If applicable, a **Create with older version** option appears next to the **Create RFC** button.
+ **Choose by category**: Select a category, subcategory, item, and operation and the CT details box opens with an option to **Create with older version** if applicable. Click **Create RFC** to open the **Run RFC** page.
1. On the **Run RFC** page, open the CT name area to see the CT details box. A **Subject** is required (this is filled in for you if you choose your CT in the **Browse change types** view). Open the **Additional configuration** area to add information about the RFC.
In the **Execution configuration** area, use available drop-down lists or enter values for the required parameters. To configure optional execution parameters, open the **Additional configuration** area.
1. When finished, click **Run**. If there are no errors, the **RFC successfully created** page displays with the submitted RFC details, and the initial **Run output**.
1. Open the **Run parameters** area to see the configurations you submitted. Refresh the page to update the RFC execution status. Optionally, cancel the RFC or create a copy of it with the options at the top of the page.
#### Creating a AWS DMS replication instance with the CLI
How it works:
1. Use either the Inline Create (you issue a `create-rfc` command with all RFC and execution parameters included), or Template Create (you create two JSON files, one for the RFC parameters and one for the execution parameters) and issue the `create-rfc` command with the two files as input. Both methods are described here.
1. Submit the RFC: `aws amscm submit-rfc --rfc-id ID` command with the returned RFC ID.
Monitor the RFC: `aws amscm get-rfc --rfc-id ID` command.
To check the change type version, use this command:
```
aws amscm list-change-type-version-summaries --filter Attribute=ChangeTypeId,Value=CT_ID
```
**Note**
You can use any `CreateRfc` parameters with any RFC whether or not they are part of the schema for the change type. For example, to get notifications when the RFC status changes, add this line, `--notification "{\"Email\": {\"EmailRecipients\" : [\"email@example.com\"]}}"` to the RFC parameters part of the request (not the execution parameters). For a list of all CreateRfc parameters, see the [AMS Change Management API Reference](https://docs.aws.amazon.com/managedservices/latest/ApiReference-cm/API_CreateRfc.html).
*INLINE CREATE*:
Issue the create RFC command with execution parameters provided inline (escape quotes when providing execution parameters inline), and then submit the returned RFC ID. For example, you can replace the contents with something like this:
```
aws --profile saml --region us-east-1 amscm create-rfc --change-type-id "ct-27apldkhqr0ol" --change-type-version "1.0" --title "TestDMSRepInstance" --execution-parameters "{\"Description\":\"DMSTestRepInstance\",\"VpcId\":\"VPC-ID\",\"Name\":\"REP-INSTANCE-NAME\",\"Parameters\":{\"InstanceClass\":\"dms.t2.micro\",\"ReplicationSubnetGroupIdentifier\":\"TEST-REP-SG\",\"SecurityGroupIds\":\"SG-ID, SG-ID\"},\"TimeoutInMinutes\":60,\"StackTemplateId\":\"stm-3n1j5hdrmiiiuqk6v\"}"
```
While your replication instance is being created, you can specify the source and target data stores. The source and target data stores can be on an Amazon Elastic Compute Cloud (Amazon EC2) instance, an AWS S3 Bucket, an Amazon Relational Database Service (Amazon RDS) DB instance, or an on-premises database.
*TEMPLATE CREATE*:
1. Output the execution parameters for this change type to a JSON file; this example names it CreateDmsRiParams.json:
```
aws amscm get-change-type-version --change-type-id "ct-27apldkhqr0ol" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > CreateDmsRiParams.json
```
1. Modify and save the execution parameters CreateDmsRiParams.json file. For example, you can replace the contents with something like this:
```
{
"Description": "DMSTestRepInstance",
"VpcId": "VPC_ID",
"Name": "Test RI",
"StackTemplateId": "stm-3n1j5hdrmiiiuqk6v",
"TimeoutInMinutes": 60,
"Parameters": {
"Description": "DESCRIPTION",
"InstanceClass": "dms.t2.micro",
"ReplicationSubnetGroupIdentifier": "TEST-REP-SG",
"SecurityGroupIds": ["SG-ID, SG-ID"}
}
}
```
1. Output the JSON template to a file in your current folder; this example names it CreateDmsRiRfc.json:
```
aws amscm create-rfc --generate-cli-skeleton > CreateDmsRiRfc.json
```
1. Modify and save the CreateDmsRiRfc.json file. For example, you can replace the contents with something like this:
```
{
"ChangeTypeVersion": "1.0",
"ChangeTypeId": "ct-27apldkhqr0ol",
"Title": "DMS-RI-Create-RFC"
}
```
1. Create the RFC, specifying the execution parameters file and the CreateDmsRiRfc file:
```
aws amscm create-rfc --cli-input-json file://CreateDmsRiRfc.json --execution-parameters file://CreateDmsRiParams.json
```
You receive the ID of the new RFC in the response and can use it to submit and monitor the RFC. Until you submit it, the RFC remains in the editing state and does not start.
#### Tips
+ You can add up to 50 tags, but to do so you must enable the **Additional configuration** view.
+ You must create a replication instance on an EC2 instance in your AMS VPC that has sufficient storage and processing power to perform the tasks you assign and migrate data from your source database to the target database. The required size of this instance varies depending on the amount of data you need to migrate and the tasks that you need the instance to perform. The replication instance provides high availability and failover support using a Multi-AZ deployment when you select the `MultiAZ` option. For more information about replication instances, see [ Working with an AWS DMS Replication Instance](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_ReplicationInstance.html).
## Execution Input Parameters
For detailed information about the execution input parameters, see [Schema for Change Type ct-27apldkhqr0ol](schemas.md#ct-27apldkhqr0ol-schema-section).
## Example: Required Parameters
```
Example not available.
```
## Example: All Parameters
```
{
"Description": "This is a test description",
"Name": "Test Stack",
"Parameters": {
"AllocatedStorage": 50,
"AutoMinorVersionUpgrade": "true",
"AvailabilityZone": "us-east-1",
"EngineVersion": "1.5.0",
"Identifier": "my-instance",
"InstanceClass": "dms.t2.micro",
"KmsKeyId": "12345678-1234-1234-1234-1234567890ab",
"MultiAZ": "false",
"PreferredMaintenanceWindow": "sun:06:00-sun:14:00",
"ReplicationSubnetGroupIdentifier": "my-subnet-group",
"SecurityGroupIds": ["sg-1234556eaba0a4799", "sg-1234556eaba0a5799"]
},
"StackTemplateId": "stm-3n1j5hdrmiiiuqk6v",
"TimeoutInMinutes": 60,
"VpcId": "vpc-01234567890abcdef"
}
```