All Services

Developer Tools

AWS Amplify

AWS Amplify Hosting builds and deploys web applications from Git or uploaded artifacts to managed CloudFront-backed hosting with branches, previews, custom domains, redirects, headers, observability, and supported server-side rendering frameworks.

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

AWS Amplify pricing and cost programs

Pricing model: Hosting, build, and backend usage

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

Billing dimensions: Build minutes · Hosting storage and transfer · Requests · Backend AWS services

Programs and modes: Amplify Hosting · Web compute · Backend resources

Amplify Hosting is metered separately from backend AWS services provisioned by an Amplify app.

Free Tier: Available — 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 Amplify?

  • Combines managed builds, global content delivery, TLS, branch deployments, pull-request previews, custom domains, redirects, and response headers.
  • Supports static sites and selected server-side rendering frameworks without operating web servers or a custom CDN deployment pipeline.
  • Integrates with source providers, monorepos, WAF, CloudWatch, IAM, and Amplify backend or other AWS APIs.

How to implement AWS Amplify

  1. Confirm the framework, feature and Region support, SSR runtime constraints, build resource needs, cache behavior, environment ownership, and whether a general-purpose CloudFront architecture is required instead.
  2. Connect a least-privilege repository, pin the runtime and dependency lockfile, define build settings, keep secrets out of client bundles and logs, configure branch access, redirects, headers, custom domain and WAF as needed.
  3. Test previews, canonical URLs, caching, authentication, SSR failures and rollback; monitor builds, availability, logs, bandwidth and compute, and remove stale branches and preview environments.

AWS Amplify best practices

  • Treat every client-side environment variable as public, keep server secrets in an approved store, and never expose credentials through build output or generated JavaScript.
  • Use least-privilege repository access, deterministic builds, pinned runtimes and dependencies, preview checks, security headers, WAF where warranted, and explicit redirect order.
  • The `amplifyapp.com` domain is on the Public Suffix List; use secure cookie practices such as the `__Host-` prefix and validate authentication on the real custom domain.

AWS Amplify use cases and server impact

  • Static and single-page applications
  • Supported SSR web applications
  • Branch previews and frontend continuous deployment

Replaces frontend build runners, static web servers, CDN provisioning, certificates, and much branch-environment automation, while application security, framework compatibility, secrets, APIs, data, and user experience remain yours.

Official implementation resources

Commonly paired AWS services