Study guide

6.5 AWS DataSync and Transfer Family

AWS Solutions Architect Associate SAA-C03

Track your progress as you read

Finished sections get a check mark.

1 Introduction

About the AWS Solutions Architect Associate (SAA-C03) Exam Study Strategies and Exam Tips for SAA-C03 The AWS Well-Architected Framework

2 Domain 1: Design Secure Architectures (30%)

1.1 IAM Fundamentals — Users, Groups, Roles, and Policies 1.2 AWS Organizations, SCPs, and Multi-Account Strategy 1.3 VPC Security — Security Groups, NACLs, and VPC Endpoints 1.4 Encryption, KMS, and Secrets Management 1.5 AWS WAF, Shield, and Network Firewall 1.6 GuardDuty, Inspector, Macie, and Security Hub 1.7 The Shared Responsibility Model for Solutions Architects 1.8 Data Protection, Compliance, and Audit Services

3 Domain 2: Design Resilient Architectures (26%)

2.1 Elastic Load Balancing (ELB) — ALB, NLB, and GWLB 2.2 EC2 Auto Scaling — Dynamic, Predictive, and Scheduled 2.3 Multi-AZ and Multi-Region Architectures 2.4 Disaster Recovery Strategies — RTO and RPO 2.5 Decoupling with SQS, SNS, and EventBridge 2.6 AWS Step Functions and Workflow Orchestration

4 Domain 3: Design High-Performing Architectures (24%)

3.1 EC2 Instance Types, Purchasing Options, and Placement Groups 3.2 Lambda, Serverless Compute, and Container Services 3.3 Amazon S3 - Storage Classes, Lifecycle, and Performance 3.4 Block and File Storage - EBS, EFS, and FSx 3.5 Database Services - RDS, Aurora, DynamoDB, and More 3.6 CloudFront, Route 53, and Global Accelerator 3.7 Data Ingestion and Transformation - Kinesis, Glue, and EMR

5 Domain 4: Design Cost-Optimized Architectures (20%)

4.1 Compute Cost Optimization — Right-Sizing, RIs, Savings Plans, and Spot 4.2 Storage Cost Optimization — S3 Tiers, EBS, and Data Transfer 4.3 Database Cost Optimization 4.4 AWS Cost Management and Monitoring Tools

6 VPC and Networking Deep Dive

5.1 VPC Architecture — Subnets, Route Tables, and Gateways 5.2 VPC Connectivity — Peering, Transit Gateway, and Direct Connect 5.3 Amazon API Gateway 5.4 CloudFormation and Infrastructure as Code 5.5 AWS PrivateLink and Endpoint Services

7 Migration, Transfer, and Hybrid Services

6.1 The 7 Rs of Cloud Migration 6.2 AWS Snow Family — Snowball Edge Devices 6.3 CloudWatch, CloudTrail, and AWS Config 6.4 Amazon Cognito and Identity Federation 6.5 AWS DataSync and Transfer Family

8 Serverless Architecture and Application Services

7.1 Serverless Architecture Patterns 7.2 Advanced SQS Patterns — DLQ, Backpressure, and FIFO 7.3 Analytics Services — Athena, OpenSearch, and QuickSight 7.4 Container Orchestration — ECS, EKS, and ECR

9 Advanced Topics and Exam Scenarios

8.1 Advanced IAM — Permission Boundaries, Federation, and Cross-Account 8.2 Caching Strategies and ElastiCache Patterns 8.3 Hybrid Architecture — DNS, Storage, and Compute 8.4 SAA-C03 Scenario Practice — Putting It All Together

6.5 AWS DataSync and Transfer Family

Key Takeaways Explain This Topic AI

AWS DataSync automates and accelerates online data transfer between on-premises storage and AWS (S3, EFS, FSx) with built-in encryption, scheduling, filtering, and post-transfer integrity validation.

DataSync uses a purpose-built protocol that can run up to about 10x faster than open-source tools like rsync, and uses an on-premises agent for on-prem sources (no agent for AWS-to-AWS).

AWS Transfer Family is a fully managed SFTP, FTPS, FTP, and AS2 service backed by S3 or EFS — it preserves existing partner file-exchange workflows without changing their clients.

Use DataSync for migration and recurring synchronization; use Transfer Family when the requirement is a specific file-transfer protocol (especially SFTP) for external partners.

DataSync pricing is per-gigabyte transferred, and it supports bandwidth throttling and include/exclude filters to control cost and scope.

Last updated: June 2026

AWS DataSync — Fast, Automated Online Transfer

Quick Answer: DataSync = fast, automated, online data transfer between on-premises and AWS storage (S3/EFS/FSx) with scheduling, filtering, and integrity checks. Transfer Family = managed SFTP/FTPS/FTP/AS2 backed by S3 or EFS so partners keep their existing clients. Exam shorthand: "bulk migrate or sync files over the network" → DataSync; "partners upload via SFTP" → Transfer Family.

DataSync moves data over the network (not by shipping disks) and is built for both one-time migrations and recurring synchronization . It deploys an agent as a VM (or EC2 instance) next to on-premises NFS/SMB/HDFS/object stores; AWS-to-AWS transfers need no agent.

  • Feature Detail
  • Throughput Up to ~10 Gbps; roughly 10x faster than rsync/open-source tools
  • Sources NFS, SMB, HDFS, self-managed object storage, S3, EFS, FSx
  • Destinations S3, EFS, FSx for Windows, FSx for Lustre, FSx for OpenZFS, FSx for NetApp ONTAP
  • Encryption TLS in transit; destination-side encryption at rest
  • Validation Automatic data-integrity verification after each task
  • Scheduling Hourly/daily/weekly tasks for ongoing sync
  • Bandwidth Configurable throttling to protect production links
  • Filtering Include/exclude patterns for selective transfer
  • Pricing Per-GB transferred (no separate license)
  • DataSync vs. scripted copies
  • Capability DataSync S3 CLI / rsync
  • Speed Purpose-built, ~10x faster Standard network speed
  • Scheduling Built-in task scheduler Needs cron/external tooling
  • Integrity check Automatic Manual
  • Encryption TLS by default Must configure
  • Operations AWS-managed Self-managed scripts

Worked example: Migrate 50 TB from on-prem NFS to Amazon EFS and then keep them in sync nightly. Deploy a DataSync agent on the NFS network, create a task NFS→EFS, run the initial full transfer, then schedule a nightly task with include filters so only changed datasets move. Validation confirms each task's integrity automatically.

AWS Transfer Family — Managed File-Transfer Protocols

Many organizations have partners and vendors hard-wired to SFTP/FTPS/FTP scripts or B2B AS2 flows. Transfer Family gives those workflows a managed AWS endpoint while the files land directly in S3 or EFS — no protocol change for the partner.

  • Feature Detail
  • Protocols SFTP, FTPS, FTP, AS2 (B2B EDI)
  • Backend storage Amazon S3 or Amazon EFS
  • Authentication Service-managed users, Active Directory, or a custom Lambda authorizer
  • Endpoint types Public, VPC, or VPC with internet-facing Elastic IPs
  • Scaling/HA Fully managed, auto-scaling, multi-AZ
  • Auditing Integrates with CloudWatch and CloudTrail
  • Choosing between the two
  • Requirement Service
  • Bulk migrate or nightly-sync file shares to AWS DataSync
  • Partners must keep using their SFTP client Transfer Family
  • Move data between two AWS file systems DataSync (no agent)
  • Inbound B2B EDI document exchange (AS2) Transfer Family

Worked example: A retailer's 200 suppliers drop nightly inventory files via SFTP to an aging on-prem server. Stand up a Transfer Family SFTP server with an S3 backend, give each supplier a service-managed user mapped to its own S3 prefix, and update DNS so existing SFTP scripts connect unchanged. Files now arrive in S3 and trigger downstream Lambda processing.

Common trap: Choosing Transfer Family for a one-time 50 TB migration. Transfer Family is about protocol compatibility for ongoing exchange, not high-throughput bulk migration — that is DataSync (online) or Snow Family (offline). Conversely, do not pick DataSync when the explicit requirement is "partners must use SFTP/FTPS," because DataSync exposes no such protocol endpoint.

On the Exam: "Migrate terabytes from on-prem NFS to EFS over the network, with scheduling and validation" → DataSync. "External partners need SFTP access landing in S3 without changing their tooling" → AWS Transfer Family.

Where each fits among the transfer services

The SAA-C03 exam clusters several transfer options, and the differentiator is almost always the requirement's keyword. DataSync wins on "fast online migration" and "scheduled sync with validation." Transfer Family wins on a named protocol ("SFTP," "FTPS," "AS2") for external parties. Snow Family wins on "limited bandwidth" plus large volume. Storage Gateway wins on "hybrid access" where on-premises apps need ongoing low-latency reads of data cached locally while it is durably stored in AWS. S3 Replication wins only for bucket-to-bucket copies inside AWS.

Reading the requirement keyword first, before the answer choices, prevents the classic mistake of choosing DataSync for an SFTP scenario or Transfer Family for a bulk migration.

Cost and operational considerations

DataSync charges per gigabyte transferred, so for very large one-time moves over a constrained link you should compare its cost and elapsed time against shipping a Snowball Edge device — past a certain volume-to-bandwidth ratio, offline shipping is both cheaper and faster. DataSync's bandwidth throttling lets you cap throughput during business hours so migration traffic does not starve production, and include/exclude filters restrict a task to specific paths.

Transfer Family is billed per enabled protocol-hour plus data transferred, and because it is fully managed and multi-AZ, it removes the need to patch and scale your own SFTP servers. For partner onboarding, map each Transfer Family user to a distinct S3 prefix and a least-privilege session policy so vendors can only see their own drop folder — the same per-identity isolation principle used with Cognito Identity Pools earlier in this chapter.