AWS Transfer Family Pricing Explained: Why Your SFTP Bill Is $200+/Month Before a Single Upload

AWS Transfer Family pricing seems innocent enough when you skim the docs. An hourly rate here, a per-gigabyte fee there. Two simple numbers. What could go wrong?

Turns out, plenty. Most engineers spinning up an AWS SFTP endpoint for the first time face immediate sticker shock on their first invoice. The surprise rarely comes from data transfer volume. It comes from the meter running silently in the background whether you move a single byte or not.

Here is the exact line-by-line breakdown using AWS published rates (US East, N. Virginia) for 2026, alongside what a realistic bill actually looks like when you deploy it.

The Core Charge: $0.30/Hour, 24/7, Whether You Use It or Not

The second you spin up a Transfer Family server endpoint, AWS starts ticking a clock at $0.30 per hour for each enabled protocol (SFTP, FTPS, or FTP).

Run the numbers for a typical month:

• 30-day month: $0.30 × 720 hours = $216.00
• 31-day month: $0.30 × 744 hours = $223.20

Remember, that rate applies per protocol. What if a legacy partner demands FTPS while everyone else uses SFTP? Enabling both protocols on that single endpoint instantly doubles your hourly charges to roughly $432 to $446 each month, long before anyone connects.

The real catch? The meter keeps running until you destroy the server resource. Idle time gets billed. Weekends count. That forgotten staging endpoint sitting in us-west-2? It's actively draining your budget. AWS offers no free tier for Transfer Family and no button to pause the clock. You either keep paying or tear down the endpoint completely.

If a vendor uploads one invoice CSV every Monday morning, you are effectively paying around $219 a month in rent for four minutes of actual compute work.

The Data Charge: $0.04/GB, Both Directions

Alongside the hourly fee, AWS bills $0.04 per gigabyte on all uploads and downloads flowing through your endpoint.

To be fair, this usage fee feels reasonable. Transferring 100GB of files costs $4. Moving a full terabyte comes out to roughly $40. For small or medium workloads, data processing fees end up looking like a rounding error next to the static endpoint tax:

Take a close look at that right column. Unless your pipelines shift tens of terabytes every month, you are primarily paying for the bare existence of the infrastructure, not the work it performs.

The Rest of the Menu

AWS has attached billable meters to almost every extra Transfer Family feature:

• SFTP connectors (outbound connections to remote SFTP servers): $0.001 per connector call plus $0.40/GB transferred. That per-gigabyte egress rate is ten times higher than inbound transfers.
• AS2 messaging: $0.30 per hour for the endpoint plus $0.01 per message for the first 100,000 monthly messages ($0.005 after that, up to 1M). Messages over 50MB are charged an extra $0.01 per additional 50MB chunk.
• Transfer Family web apps (the browser-based portal): $0.50 per hour per unit, adding roughly $365 per month if non-technical users need browser uploads instead of standard SFTP software.
• Managed Workflows: PGP decryption steps run $0.10/GB processed.

The Hidden Line Items: Supporting AWS Infrastructure

AWS explicitly reminds you on their pricing page that standard charges apply for downstream services. Building a production-ready SFTP setup usually drags in several extra billable components:

• Amazon S3: Storage space, API request operations (PUT/GET), and cross-region or internet egress fees.
• AWS Lambda: Necessary if you plan to authenticate users via passwords in a custom database instead of manually managing SSH keys per user.
• Amazon CloudWatch: Log ingestion and persistent storage for audit compliance. Answering simple questions like "did vendor X push their file today?" requires paying for CloudWatch Insights queries.
• AWS Secrets Manager: Commonly used to store API keys and credentials for custom auth providers, billed per secret monthly plus API call fees.
• Route 53: Required if you want a clean custom domain like sftp.yourcompany.com instead of the raw AWS-generated hostname.

While none of these auxiliary services look huge on their own, together they regularly tack on an extra 10% to 20% to your true monthly spend. More importantly, each service adds another IAM policy, stack component, and security surface to maintain.

What a Realistic Small-Team Bill Looks Like

Let's look at a standard setup: a team needs external partners to drop files into S3 buckets. You run one SFTP endpoint, custom password authentication backed by Lambda, and handle roughly 50GB of incoming uploads a month.

• Endpoint (SFTP): ~$219
• Data processing: $2
• Lambda, CloudWatch, Secrets Manager: ~$5 to $15
• Total: roughly $225 to $235/month, or ~$2,800/year

And what does $2,800 a year buy you? A raw protocol endpoint. You still have to build and maintain user management, folder permission mapping, SSH key rotation policies, and file arrival notifications yourself.

When AWS Transfer Family Is Actually Worth It

To be fair, AWS Transfer Family makes complete sense in specific scenarios:

• You push massive volume through high-duty endpoints. When traffic runs constantly, that fixed hourly charge gets amortized down to pennies per gigabyte.
• Strict compliance forces everything inside your AWS isolation boundary. You need VPC-hosted endpoints, customer-managed KMS keys, and strict IAM governance across every hop.
• You already run dedicated DevOps teams, making Transfer Family just another Terraform module in an existing stack.

In those environments, Transfer Family acts as a capable, enterprise-grade service. Its pricing structure isn't broken; it was simply engineered for high-throughput, always-on corporate infrastructure.

The Alternative: Pay for Data Moved, Not Hours Elapsed

The core issue with hourly endpoint pricing is simple: most file transfer workloads arrive in bursts. Vendors upload batches overnight. Field teams dump files after site visits. Partners send spreadsheets once a week. The endpoint sits idle during the intervening hours, yet idle hours represent almost your entire bill.

Rilavek changes the math by billing for bandwidth actually transferred rather than server uptime.

• Free plan: 10GB/month, $0, no credit card required. Plenty of allowance to run production workloads for small teams.
• Starter: $10/month for 100GB.
• Pro: $30/month for 1TB.

There are no hourly clocks or per-protocol penalties. Hosting your endpoint costs nothing. Uploaded files stream straight into your own object storage (AWS S3, Cloudflare R2, Backblaze B2, Wasabi, MinIO, or other S3-compatible providers) using a secure zero-knowledge architecture. That 50GB monthly scenario costing $225+ on AWS fits easily inside Rilavek's $10/month Starter tier.

It isn't a temporary discount. It's a pragmatic pricing model that charges for actual data utility rather than digital rent.

Next Steps

• Compare the architectures: AWS Transfer Family vs. Rilavek: The Hidden Costs breaks down vendor lock-in, IAM friction, and onboarding overhead.
• Weigh your options: Read our overview of AWS Transfer Family alternatives for small teams.
• Test the math yourself: Connect an S3 bucket and test your pipeline on Rilavek's free tier. If you've been paying $219 a month for idle infrastructure, the difference will be clear right away.