Sunday, October 25, 2026
HomeCloud ComputingNew for AWS DataSync – Transfer Information Between AWS and Google Cloud...

New for AWS DataSync – Transfer Information Between AWS and Google Cloud Storage or AWS and Microsoft Azure Information

[ad_1]

Transferring knowledge to and from AWS Storage providers will be automated and accelerated with AWS DataSync. For instance, you should utilize DataSync emigrate knowledge to AWS, replicate knowledge for enterprise continuity, and transfer knowledge for evaluation and processing within the cloud. You should utilize DataSync to switch knowledge to and from AWS Storage providers, together with Amazon Easy Storage Service (Amazon S3), Amazon Elastic File System (Amazon EFS), and Amazon FSx. DataSync additionally integrates with Amazon CloudWatch and AWS CloudTrail for logging, monitoring, and alerting.

At the moment, we added to DataSync the potential emigrate knowledge between AWS Storage providers and both Google Cloud Storage or Microsoft Azure Information. On this approach, you may simplify your knowledge processing or storage consolidation duties. This additionally helps if it’s good to import, share, and change knowledge with clients, distributors, or companions who use Google Cloud Storage or Microsoft Azure Information. DataSync offers end-to-end safety, together with encryption and integrity validation, to make sure your knowledge arrives securely, intact, and able to use.

Let’s see how this works in observe.

Making ready the DataSync Agent
First, I want a DataSync agent to learn from, or write to, storage situated in Google Cloud Storage or Azure Information. I deploy the agent on an Amazon Elastic Compute Cloud (Amazon EC2) occasion. The most recent DataSync Amazon Machine Picture (AMI) ID is saved within the Parameter Retailer, a functionality of AWS Programs Supervisor. I exploit the AWS Command Line Interface (CLI) to get the worth of the /aws/service/datasync/ami parameter:

aws ssm get-parameter --name /aws/service/datasync/ami --region us-east-1

{
    "Parameter": {
        "Title": "/aws/service/datasync/ami",
        "Sort": "String",
        "Worth": "ami-0e244fe801cf5a510",
        "Model": 54,
        "LastModifiedDate": "2022-05-11T14:08:09.319000+01:00",
        "ARN": "arn:aws:ssm:us-east-1::parameter/aws/service/datasync/ami",
        "DataType": "textual content"
    }
}

Utilizing the EC2 console, I begin an EC2 occasion utilizing the AMI ID specified within the Worth property of the parameter. For networking, I exploit a public subnet and the choice to auto-assign a public IP deal with. The EC2 occasion wants community entry to each the supply and the vacation spot of an information transferring job. One other requirement for the occasion is to have the ability to obtain HTTP site visitors from DataSync to activate the agent.

When utilizing AWS DataSync in a digital personal cloud (VPC) primarily based on the Amazon VPC service, it’s a finest observe to use VPC endpoints to attach the agent with the DataSync service. Within the VPC console, I select Endpoints on the navigation pane after which Create endpoint. I enter a reputation for the endpoint and choose the AWS providers class.

Console screenshot.

Within the Companies part, I search for DataSync.

Console screenshot.

Then, I choose the identical VPC the place I began the EC2 occasion.

Console screenshot.

To cut back cross-AZ site visitors, I select the identical subnet used for the EC2 occasion.

Console screenshot.

The DataSync agent operating on the EC2 occasion wants community entry to the VPC endpoint. For simplicity, I exploit the default safety group of the VPC for each. I create the VPC endpoint and, after a couple of minutes, it’s prepared for use.

Console screenshot.

Within the AWS DataSync console, I select Brokers from the navigation pane after which Create agent. I choose Amazon EC2 for the Hypervisor.

Console screenshot.

I select VPC endpoints utilizing AWS PrivateLink for the Endpoint kind. I choose the VPC endpoint I created earlier than and the identical Subnet and Safety group I used for the VPC endpoint.

I select the choice to Mechanically get the activation key and sort the general public IP of the EC2 occasion. Then, I select Get key.

Console screenshot.

After the DataSync agent has been activated, I don’t want HTTP entry anymore, and I take away that from the safety teams of the EC2 occasion. Now that the DataSync agent is lively, I can configure duties and places to maneuver my knowledge.

Transferring Information from Google Cloud Storage to Amazon S3
I’ve a number of photos in a Google Cloud Storage bucket, and I need to synchronize these information with an S3 bucket. Within the Google Cloud console, I open the settings of the bucket. There, I create a service account with Storage Object Viewer permissions and write down the credentials (entry key and secret) to entry the bucket programmatically.

Again within the AWS DataSync console, I select Duties after which Create job.

To configure the supply of the duty, I create a location. I choose Object storage for the Location kind and select the agent I simply created. For the Server, I exploit storage.googleapis.com. Then, I enter the identify of the Google Cloud bucket and the folder the place my photos are saved.

Console screenshot.

For authentication, I enter the entry key and the key I retrieved once I created the service account. I select Subsequent.

Console screenshot.

To configure the vacation spot of the duty, I create one other location. This time, I choose Amazon S3 for the Location Sort. I select the vacation spot S3 bucket and enter a folder that might be used as a prefix for the information transferred to the bucket. I exploit the Autogenerate button to create the IAM function that can give DataSync permissions to entry the S3 bucket.

Console screenshot.

Within the subsequent step, I configure the duty settings. I enter a reputation for the duty. Optionally, I can fine-tune how DataSync verifies the integrity of the transferred knowledge or allocate a bandwidth for the duty.

Console screenshot.

I may select what knowledge to scan and what to switch. By default, all supply knowledge is scanned, and solely knowledge that has modified is transferred. Within the Extra settings, I disable Copy object tags as a result of tags are at present not supported with Google Cloud Storage.

Console screenshot.

I can choose the schedule used to run this job. For now, I go away it Not scheduled, and I’ll begin it manually.

Console screenshot.

For logging, I exploit the Autogenerate button to create a log group for DataSync. I select Subsequent.

Console screenshot.

I evaluate the configurations and create the duty. Now, I begin the info transferring job from the console. After a couple of minutes, the information are synced with my S3 bucket and I can entry them from the S3 console.

Console screenshot.

Transferring Information from Azure Information to Amazon FSx for Home windows File Server
I take lots of footage, and I even have a number of photos in an Azure file share. I need to synchronize these information with an Amazon FSx for Home windows file system. Within the Azure console, I choose the file share and select the Join button to generate a PowerShell script that checks if this storage account is accessible over the community.

$connectTestResult = Take a look at-NetConnection -ComputerName <SMB_SERVER> -Port 445
if ($connectTestResult.TcpTestSucceeded) {
    # Save the password so the drive will persist on reboot
    cmd.exe /C "cmdkey /add:`"danilopsync.file.core.home windows.internet`" /person:`"localhost<USER>`" /move:`"<PASSWORD>`""
    # Mount the drive
    New-PSDrive -Title Z -PSProvider FileSystem -Root "danilopsync.file.core.home windows.internet<SHARE_NAME>" -Persist
} else {
    Write-Error -Message "Unable to achieve the Azure storage account by way of port 445. Test to ensure your group or ISP will not be blocking port 445, or use Azure P2S VPN, Azure S2S VPN, or Specific Path to tunnel SMB site visitors over a unique port."
}

From this script, I seize the data I must configure the DataSync location:

  • SMB Server
  • Share Title
  • Consumer
  • Password

Again within the AWS DataSync console, I select Duties after which Create job.

To configure the supply of the duty, I create a location. I choose Server Message Block (SMB) for the Location Sort and the agent I created earlier than. Then, I exploit the data I discovered within the script to enter the SMB Server deal with, the Share identify, and the Consumer/Password to make use of for authentication.

Console screenshot.

To configure the vacation spot of the duty, I once more create a location. This time, I select Amazon FSx for the Location kind. I choose an FSx for Home windows file system that I created earlier than and use the default share identify. I exploit the default safety group to hook up with the file system. As a result of I’m utilizing AWS Listing Service for Microsoft Energetic Listing with FSx for Home windows File Server, I exploit the credentials of a person member of the AWS Delegated FSx Directors and Area Admins teams. For extra info, see Making a location for FSx for Home windows File Server within the documentation.

Console screenshot.

Within the subsequent step, I enter a reputation for the duty and go away all different choices to their default values in the identical approach I did for the earlier job.

Console screenshot.

I evaluate the configurations and create the duty. Now, I begin the info transferring job from the console. After a couple of minutes, the information are synched with my FSx for Home windows file system share. I mount the file system share with a Home windows EC2 occasion and see that my photos are there.

EC2 screenshot.

When making a job, I can reuse current places. For instance, if I need to synchronize information from Azure Information to my S3 bucket, I can shortly choose the 2 corresponding places I created for this submit.

Availability and Pricing
You possibly can transfer your knowledge utilizing the AWS DataSync console, AWS Command Line Interface (CLI), or AWS SDKs to create duties that transfer knowledge between AWS storage and Google Cloud Storage buckets or Azure Information file methods. As your duties run, you may monitor progress from the DataSync console or by utilizing CloudWatch.

There aren’t any adjustments to DataSync pricing with these new capabilities. Transferring knowledge to and from Google Cloud or Microsoft Azure is charged on the similar fee as all different knowledge sources supported by DataSync at the moment.

Chances are you’ll be topic to knowledge switch out charges by Google Cloud or Microsoft Azure. As a result of DataSync compresses knowledge in flight when copying between the agent and AWS, you could possibly scale back egress charges by deploying the DataSync agent in a Google Cloud or Microsoft Azure setting.

When utilizing DataSync to maneuver knowledge from AWS to Google Cloud or Microsoft Azure, you might be charged for knowledge switch out from EC2 to the web. See Amazon EC2 pricing for extra info.

Automate and speed up the best way you progress knowledge with AWS DataSync.

— Danilo



[ad_2]

RELATED ARTICLES

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Most Popular

Recent Comments