All Services

App Integration

Amazon AppFlow

Amazon AppFlow is a managed data-integration service for transferring and mapping data between supported SaaS applications and AWS services on demand, on a schedule, or from supported events.

Explore pricing models, common use cases, infrastructure support, and the AWS services that commonly work with Amazon AppFlow.

SaaS integration scope and flow-run cost

Amazon AppFlow Pricing, Connectors & Flow Design

AppFlow bills per successful flow run and per volume processed, which makes schedule frequency a cost decision as much as a freshness decision. A polling flow that finds no new records still bills as a run.

Official AWS sources reviewed 2026-08-29.

What is Amazon AppFlow?

AppFlow transfers data between supported SaaS applications and AWS services such as Amazon S3 and Amazon Redshift. A flow declares the source, destination, trigger, field mapping, filters, and transformations, so there is no connector code to write or host.

What is Amazon AppFlow?

What drives Amazon AppFlow pricing?

Pay per successful flow run plus the volume of data processed. Scheduled flows that find no new records still count as runs, connectors that accelerate a transfer with extra concurrent processes bill each process as an additional flow, and private connectivity is charged separately.

Official Amazon AppFlow pricing

Which applications does AppFlow connect?

AWS publishes a per-application list of supported sources and destinations with the operations each connector allows. Support is not symmetric, so confirm the direction, objects, and fields a flow needs before designing around a specific connector.

Supported AppFlow source and destination applications

Related AWS services for this plan

  • Amazon Simple Storage Service — Land AppFlow output in Amazon S3 when downstream analytics reads files rather than an API.
  • Amazon Redshift — Use Amazon Redshift as a destination when transferred records belong in a warehouse schema.
  • AWS Glue — Catalog transferred datasets with the AWS Glue Data Catalog so query engines can discover them.
  • AWS PrivateLink — Use AWS PrivateLink where a transfer must avoid the public internet, and price that path separately.

Amazon AppFlow pricing and cost programs

Pricing model: Data-flow execution and processing

On-Demand
Available
Reserved Instances or reserved capacity
Not applicable
Savings Plans
Not applicable
Spot
Not applicable

Billing dimensions: Flow runs · Data processed · Connector-specific charges

Programs and modes: Scheduled flows · Event-triggered flows · On-demand flows

Each flow execution and processed data volume can be billed separately.

Free Tier: Service-specific — verify current offers

Pricing reviewed 2026-07-25. Reviewed against the linked official AWS pricing page. Recheck regional rates and program terms before purchase.

Official AWS pricing

Official AWS sources reviewed 2026-07-21.

Why implement Amazon AppFlow?

  • Moves data through maintained SaaS connectors without building and hosting custom polling, OAuth refresh, batching, and retry workers.
  • Supports field mapping, filtering, validation, aggregation or masking options depending on connector, with encrypted transport and managed connection-secret storage.
  • Feeds S3, Redshift, and other supported AWS destinations for analytics or transfers AWS data back to supported SaaS applications.

How to implement Amazon AppFlow

  1. Verify the exact connector, Region, object, API edition, quota, private-connectivity, source and destination capabilities, then create required SaaS permissions and OAuth application settings.
  2. Create an encrypted connector profile, choose source and destination objects, map and validate fields, configure filters and error handling, and select on-demand, scheduled, or supported event-triggered execution.
  3. Run a limited historical sample, reconcile counts and transformations, confirm incremental-field behavior and deletion semantics, then enable CloudWatch and CloudTrail monitoring plus a failure replay procedure.

Amazon AppFlow best practices

  • Use a dedicated least-privilege SaaS integration identity, customer-managed keys when policy requires them, private flows where supported, and never place sensitive data in flow names or tags.
  • Understand connector-specific API quotas, incremental transfer fields, schema changes, null and deletion behavior, and schedule flows with enough room for retries and destination processing.
  • Keep immutable raw landing data when appropriate, validate record counts and rejected rows, alert on failed or delayed executions, and test credential rotation and connector reauthorization.

Amazon AppFlow use cases and server impact

  • Replicating CRM and support data into S3
  • Scheduled SaaS-to-warehouse ingestion
  • Sending governed AWS data to supported business applications

Replaces custom connector and transfer workers for supported applications, but data contracts, SaaS quotas, reconciliation, credential ownership, and downstream transformations remain customer responsibilities.

Official implementation resources

Commonly paired AWS services