All Services

Developer Tools

AWS Device Farm

AWS Device Farm runs mobile application tests on AWS-hosted physical devices and returns logs, screenshots, video, performance data, and per-device results.

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

AWS Device Farm pricing and cost programs

Pricing model: Device testing usage

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

Billing dimensions: Device minutes · Concurrent sessions · Private devices

Programs and modes: Pay-as-you-go testing · Private device slots

Charges vary between public device minutes and private device capacity.

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 AWS Device Farm?

  • Expands test coverage across real device models, operating-system versions, orientations, locales, and network conditions without maintaining a device lab.
  • Runs tests in parallel and collects device-specific evidence that helps reproduce failures that emulators may miss.
  • Supports built-in and common automation frameworks and can be integrated into continuous-delivery pipelines.

How to implement AWS Device Farm

  1. Create a Device Farm project in us-west-2, upload the Android or iOS application and an optional supported test package.
  2. Choose devices or a device pool, configure the test specification and execution settings, then schedule a run.
  3. Review reports, logs, screenshots, video, and performance data; connect private test targets through the supported VPC configuration when required.

AWS Device Farm best practices

  • Use a deliberate representative device matrix and stable automated tests instead of testing every device on every commit.
  • Do not embed production secrets or sensitive customer data in application or test packages; grant the CI identity only the Device Farm actions it needs.
  • Use network isolation and VPC access for private targets, retain useful artifacts, and separate flaky-test handling from genuine device regressions.

AWS Device Farm use cases and server impact

  • Android and iOS regression suites
  • Cross-device compatibility testing
  • CI release gates with device evidence

Replaces much of a physical mobile-device lab and its scheduling infrastructure, while teams still create and maintain the application tests.

Official implementation resources

Commonly paired AWS services