From the course: AWS: Storage and Data Management

Move data to AWS

- Unless your organization is just getting started, you no doubt have lots of data on premises. And like many organizations, your data is everywhere. It's on servers, local file systems, on a range of file system types and operating systems. It's on network attached storage. It's in relational databases of many different types. Oracle, Microsoft SQL, Postgres, MySQL. Some of this might even be on staff laptops in the form of text files or CSVs. When we are ready to move to the cloud, how do we get all this data to AWS? We've seen a few ways already. You can always upload data to S3, or add records to Dynamo directly from the AWS gooey. But that's often the slowest way to do things, and certainly the least automated. And recall that if you're using AWS Direct Connect, you can transfer data quickly over the direct Connect pipe to an EFS file system via an NFS mount. But there are many more ways, of course. In this chapter, we'll explore some of those other options. For instance, command line interfaces for services like S3, have commands that can push, update, sync, and manage data in those services. We'll look at that in the next lesson. After that, it's AWS storage gateway, a service that can provide you local NFS mounts that ultimately convey your data over the internet to S3. Next, we'll examine AWS database migration service and schema conversion tool. These AWS features can help you both migrate, and if you choose, continuously replicate local databases to RDS, S3, and more. You're still subject to the latency of your AWS connection overall, but these tools make the move a lot simpler than a DIY approach. Finally, we'll take a peek at AWS's take on Sneakernet. AWS Snowball. This service lets you ship your data directly to AWS, bypassing the internet entirely. We'll start with command line tools in the next video.

Contents