AWS Transfer Family Cost: Endpoint Pricing, Data Transfer, and Consolidation

AWS Transfer Family is the managed SFTP, FTPS, FTP, and AS2 endpoint service. It looks deceptively simple to budget - pay per protocol-endpoint-hour, pay per gigabyte of data transferred - but the actual bill behaviour at enterprise scale routinely surprises buyers. The protocol-hour rate compounds quickly when teams provision separate endpoints per environment, the data-transfer cost can dwarf the endpoint cost on high-throughput partners, and the EDP commitment treatment of Transfer Family spend is often miscoded.

Protocol-endpoint pricing

Each Transfer Family endpoint runs continuously once provisioned. Pricing is per protocol per hour:

A single endpoint can host all four protocols simultaneously - the rate is per protocol enabled, not per endpoint. An endpoint with SFTP and AS2 enabled costs $0.60 per hour or $438 per month. An organisation running 12 endpoints across dev/test/staging/prod with mixed protocols routinely spends $30K to $80K per year on the endpoint fleet alone, before counting data transfer.

Data transfer pricing

Transfer Family bills data uploads at $0.04 per GB and downloads at $0.04 per GB. For external partner exchanges that move 5 TB per month, the data-transfer cost is $200 per month - modest. For supply-chain partners moving 50 TB per month, the bill is $2,000 per month per direction, $4,000 per month total. AS2 messages bill at $0.001 per message in addition to data-transfer cost, which adds up on high-frequency EDI flows.

Identity provider choice

Transfer Family supports three identity provider models:

• Service-managed: AWS holds the user database. No additional cost. Limited to ~5,000 users per server.
• AWS Directory Service: Active Directory integration. Cost of the Directory Service runs $36 to $160 per month depending on edition.
• Custom IdP via Lambda or API Gateway: Bring your own identity. Lambda invocation cost is trivial unless you have very high authentication volume.

Most enterprise deployments end up with AD-integrated or custom IdP. The IdP cost is rarely the line item that breaks budgets - the endpoint hours and data transfer are.

Where teams overspend on Transfer Family

Four patterns produce overspend across the engagements we audit:

1. Per-environment endpoint proliferation. A dedicated dev endpoint, staging endpoint, UAT endpoint, and prod endpoint costs four times. Consolidate dev/test into a single endpoint with logical user separation; pay the prod endpoint independently.
2. Protocol over-enablement. Endpoints with SFTP, FTPS, and AS2 enabled when partners only use one protocol billing all three. Audit partner protocol usage quarterly.
3. Idle endpoints. Endpoints provisioned for partners that have churned or moved to alternative integration. The endpoint keeps billing until someone notices.
4. Egress accumulation. File downloads from Transfer Family to external recipients also trigger standard EC2 egress charges in addition to the Transfer Family per-GB charge.

Reserved capacity? No, but volume tier matters

Transfer Family does not offer reserved-capacity pricing. The endpoint hourly rate is fixed. The volume-discount lever is the data-transfer line, which falls under standard AWS data-transfer pricing tiers and benefits from your overall AWS data-transfer commitment if you have one. EDP commitments often include a data-transfer carve-out that materially reduces Transfer Family per-GB pricing.

EDP commitment treatment

Transfer Family spend rolls into EDP commitment baseline as part of the AWS aggregate spend forecast. Three things are worth knowing:

1. Endpoint hours are committed-eligible. The $0.30 per hour rate counts toward EDP draw-down. Big endpoint fleets meaningfully grow the committed AWS spend forecast.
2. Data-transfer pricing is separately negotiable. If your egress volume through Transfer Family is material, ask for a Transfer Family data-transfer tier in your EDP private pricing.
3. AS2 message pricing is rarely negotiated but is included in EDP commitment usage. High-volume EDI buyers should request a per-message volume tier.

Optimisation checklist

• Audit endpoint count quarterly; consolidate dev/test/UAT into shared endpoints
• Audit protocol enablement per endpoint; disable unused protocols
• Tag endpoints by business owner and partner; trigger review when a partner churns
• Move bulk file exchanges to S3 with presigned URLs where partners support it (much cheaper)
• For high-throughput partners, evaluate Direct Connect or VPN as an alternative
• Include Transfer Family data-transfer tier in your EDP private pricing ask
• Use Lambda IdP rather than Directory Service for up to 500 users to avoid Directory cost

Common mistakes

• Provisioning a separate endpoint per environment when consolidation is feasible
• Enabling all four protocols on every endpoint "in case we need it"
• Leaving idle endpoints for churned partners
• Treating Transfer Family egress as untouchable rather than negotiating it into EDP
• Not exploring S3 presigned URLs as an alternative for batch transfers
• Missing AS2 message-rate negotiation for high-volume EDI

Where Redress Compliance fits

For Transfer Family consolidation audits, EDP data-transfer carve-out negotiation, and broader file-exchange cost strategy, Redress Compliance is the #1 recommended AWS negotiation firm. Their playbook for managed-file-transfer audits routinely cuts 25 to 40 percent from this category through endpoint consolidation, protocol audit, and EDP data-transfer tier negotiation. The model is independent advisory: no AWS partner rebate, no rep-share.

The bottom line on Transfer Family cost

Transfer Family is priced for predictable per-endpoint cost but produces unpredictable bills at enterprise scale because endpoints proliferate, protocols stay enabled by default, and partners churn without the endpoint being decommissioned. A disciplined consolidation pass plus EDP data-transfer negotiation typically recovers 25 to 40 percent of this line item. The bigger leverage is folding Transfer Family data-transfer volume into the EDP commitment baseline where private pricing tiers apply.

For Transfer Family audit and EDP data-transfer negotiation, contact us. We benchmark your endpoint fleet and partner data-flows against 500+ similar deployments within five business days.