# Working with data providers, instance profiles, and migration projects in AWS DMS
<a name="migration-projects"></a>

When you use DMS Schema Conversion and homogeneous data migrations in AWS Database Migration Service, you work with migration projects. In turn, AWS DMS migration projects use subnet groups, instance profiles, and data providers.

A *subnet* is a range of IP addresses in your VPC. A replication *subnet group* includes subnets from different Availability Zones which your instance profile can use. Note that a replication *subnet group* is a DMS resource, and is distinct from subnet groups that Amazon VPC and Amazon RDS use.

An *instance profile* specifies network and security settings for the serverless environment where your migration project runs.

A *data provider* stores a data store type and the location information about your database. After you add a data provider to your migration project, you provide the database credentials from AWS Secrets Manager. AWS DMS uses this information to connect to your database.

After you create data providers, your instance profile, and other AWS resources, you can create a migration project. A *migration project* describes your instance profile, source and target data providers, and secrets from AWS Secrets Manager. You can create multiple migration projects for different source and target data providers.

You perform most of your work in the migration project. For DMS Schema Conversion, you use a migration project to assess the objects of your source data provider and convert them to a format compatible with the target database. Then, you can apply converted code to your target data provider or save it as a SQL script. For homogeneous data migrations, you use a migration project to migrate data from your source database to a target database of the same type in the AWS Cloud.

Migration projects in AWS DMS are serverless only. AWS DMS automatically provisions the cloud resources for your migration projects.

AWS DMS has the maximum number of instance profiles, data providers, and migration projects that you can create for your AWS account. See the following section for information about AWS DMS service quotas [Quotas for AWS Database Migration Service](CHAP_Limits.md).

**Topics**
+ [Creating a subnet group for an AWS DMS migration project](subnet-group.md)
+ [Creating instance profiles for AWS Database Migration Service](instance-profiles.md)
+ [Creating data providers in AWS Database Migration Service](data-providers-create.md)
+ [Creating migration projects in AWS Database Migration Service](migration-projects-create.md)
+ [Managing migration projects in AWS Database Migration Service](migration-projects-manage.md)

# Creating a subnet group for an AWS DMS migration project
<a name="subnet-group"></a>

Before you create an instance profile, configure a subnet group for your instance profile.

**To create a subnet group**

1. Sign in to the AWS Management Console and open the AWS DMS console at [https://console.aws.amazon.com/dms/v2/](https://console.aws.amazon.com/dms/v2/).

1. In the navigation pane, choose **Subnet groups**, and then choose **Create subnet group**.

1. For **Name**, enter a unique name of your subnet group.

1. For **Description**, enter a brief description of your subnet group.

1. For **VPC**, choose a VPC that has at least one subnet in at least two Availability Zones.

1. For **Add subnets**, choose subnets to include in the subnet group. You must choose subnets in at least two Availability Zones.

   To connect to Amazon RDS databases, add public subnets into your subnet group. To connect to on-premises databases, add private subnets into your subnet group. 

1. Choose **Create subnet group**.

# Creating instance profiles for AWS Database Migration Service
<a name="instance-profiles"></a>

You can create multiple instance profiles in the AWS DMS console. Make sure that you select an instance profile to use for each migration project that you create in AWS DMS.

**To create an instance profile**

1. Sign in to the AWS Management Console and open the AWS DMS console at [https://console.aws.amazon.com/dms/v2/](https://console.aws.amazon.com/dms/v2/).

1. In the navigation pane, choose **Instance profiles**.

1. Choose **Create instance profile**.

1. On the **Create instance profile** page, enter a descriptive value for **Name** for your instance profile.

1. For **Network type**, choose **Dual-stack mode** to create an instance profile that supports IPv4 and IPv6 addressing. Keep the default option to create an instance profile that supports only IPv4 addressing.

1. Next, choose **Virtual private cloud (VPC)** to run your instance of the selected network type. Then choose a **Subnet group** and **VPC security groups** for your instance profile.

   To connect to Amazon RDS databases, use the subnet configuration appropriate for your RDS setup, whether public or private. For connecting to on-premises databases, If use a private subnet group and ensure that your network is configured to allow AWS DMS access to the source on-premises database through the NAT gateway's public IP address. For more information, see [Create a VPC based on Amazon VPC](set-up.md#set-up-vpc).

1. (Optional) In you create a migration project for DMS Schema Conversion, then for **Schema conversion settings - optional**, choose an Amazon S3 bucket to store information from your migration project. Then choose the AWS Identity and Access Management (IAM) role that provides access to this Amazon S3 bucket. For more information, see [Create an Amazon S3 bucket](set-up.md#set-up-s3-bucket).

1. Choose **Create instance profile**.

After you create your instance profile, you can modify or delete it.

**To modify an instance profile**

1. Sign in to the AWS Management Console and open the AWS DMS console at [https://console.aws.amazon.com/dms/v2/](https://console.aws.amazon.com/dms/v2/).

1. Choose **Instance profiles**. The **Instance profiles** page opens.

1. Choose your instance profile, and then choose **Modify**.

1. Update the name of your instance profile, edit the VPC or Amazon S3 bucket settings.

1. Choose **Save changes**.

**To delete an instance profile**

1. Sign in to the AWS Management Console and open the AWS DMS console at [https://console.aws.amazon.com/dms/v2/](https://console.aws.amazon.com/dms/v2/).

1. Choose **Instance profiles**. The **Instance profiles** page opens.

1. Choose your instance profile, and then choose **Delete**.

1. Choose **Delete** to confirm your choice.

# Creating data providers in AWS Database Migration Service
<a name="data-providers-create"></a>

You can create data providers and use them in AWS DMS migration projects. Your data provider can be a self-managed engine running on-premises or on an Amazon EC2 instance. Also, your data provider can be a fully managed engine, such as Amazon Relational Database Service (Amazon RDS) or Amazon Aurora.

For each database, you can create a single data provider. You can use a single data provider in multiple migration projects.

Before creating a migration project, make sure that you have created at least two data providers. One of your data providers must be on an AWS service. You can't use AWS DMS to convert your schemas or migrate your data to an on-premises database.

The following procedure shows you how to create data providers in the AWS DMS console wizard.

**To create a data provider**

1. Sign in to the AWS Management Console, then open the AWS DMS console at [https://console.aws.amazon.com/dms/v2/](https://console.aws.amazon.com/dms/v2/).

1. Choose **Data providers**. The **Data providers** page opens.

1. Choose **Create data provider**. The following table describes the settings.  
****    
[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/dms/latest/userguide/data-providers-create.html)

1. Choose **Create data provider**.

After you create a data provider, make sure that you add database connection credentials in AWS Secrets Manager.

# Creating migration projects in AWS Database Migration Service
<a name="migration-projects-create"></a>

Before you create a migration project in AWS DMS, make sure that you create the following resources:
+ Data providers that describe your source and target databases
+ Secrets with database credentials stored in AWS Secrets Manager
+ The AWS Identity and Access Management (IAM) role that provides access to Secrets Manager
+ An instance profile that includes network and security settings

**To create a migration project**

1. Sign in to the AWS Management Console and open the AWS DMS console at [https://console.aws.amazon.com/dms/v2/](https://console.aws.amazon.com/dms/v2/).

1. Choose **Migration projects**. The **Migration projects** page opens.

1. Choose **Create migration project**. The following table describes the settings.  
****    
[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/dms/latest/userguide/migration-projects-create.html)

1. Choose **Create migration project**.

After AWS DMS creates your migration project, you can use this project in DMS Schema Conversion or homogeneous data migrations. To start working with your migration project, on the **Migration projects** page, choose your project from the list.

# Managing migration projects in AWS Database Migration Service
<a name="migration-projects-manage"></a>

After you create your migration project, you can modify or delete it. For example, to change the source or target data provider, modify your migration project.

You can modify or delete your migration project only after you close the schema conversion or data migration operations. To do so, choose your migration project from the list, and choose **Schema conversion** or **Data migrations**. Next, choose **Close schema conversion** for DMS Schema Conversion and confirm your choice. For homogeneous data migrations, choose your data migration, then choose **Stop** on the **Actions** menu. After you edit your migration project, you can launch schema conversion or start your data migration again.

**To modify a migration project**

1. Sign in to the AWS Management Console and open the AWS DMS console at [https://console.aws.amazon.com/dms/v2/](https://console.aws.amazon.com/dms/v2/).

1. Choose **Migration projects**. The **Migration projects** page opens.

1. Choose your migration project, and then choose **Modify**.

1. Update the name of your project, edit the instance profile, or change source and target data providers. Optionally, add or edit migration rules that change the object names during conversion.

1. Choose **Save changes**.

**To delete a migration project**

1. Sign in to the AWS Management Console and open the AWS DMS console at [https://console.aws.amazon.com/dms/v2/](https://console.aws.amazon.com/dms/v2/).

1. Choose **Migration projects**. The **Migration projects** page opens.

1. Choose your migration project, and then choose **Delete**.

1. Choose **Delete** to confirm your choice.