AWS DataSync adds support for on-premises object storage

AWS DataSync now supports transfers to and from self-managed object storage!

This new feature makes it easy for customers to automate copying large amounts of data between on-premises object storage and AWS Cloud Storage.

What is AWS DataSync?

If you’re new to AWS DataSync, you may be wondering how this service works.

AWS DataSync makes it simple and fast to move large amounts of data between on-premises storage and AWS Cloud Storage. AWS DataSync makes it easy for you to move data by automating both the management of data transfer processes and the infrastructure required for a high-performance and secure data transfer. The below image illustrates how you can use AWS DataSync to quickly and efficiently move data between on-premises storage systems and Amazon S3, Amazon EFS, and Amazon FSx for Windows File Server.

Let’s see a demo…

Who’s ready for a demo? I know I am!

Let’s head over to the AWS Console and search for AWS DataSync.

Let’s click “Get Started.”

For the purpose of this blog post, we will pretend we’ve already Created an Agent. After you have created an agent and configured your source and destination, the next step is to Create a Task.

We want to set up a task that will transfer files from our on-premises object storage system to AWS. To do this, we select “Create Task.”

We select “Create a new location” and specify an Object storage location type for our source.

Now it’s time to select your agent. We add the IP address of our on-premises object storage server, as well as our path to the files we want to move.

Your object storage will likely require credentials to access it, so you may want to require Authentication.

We configure an Access key and Secret key to access our S3 bucket.

Now it’s time to configure our destination location. We do so by selecting “Choose an existing location” and by choosing an existing S3 bucket.

Next I pick a “Task Name.”

We also have the option to schedule what frequency we wish to execute this Task. (You may want to schedule it in order to regularly pick up incremental changes until the migration cut-over.)