AWS Amplify Hosting cost: build minutes, hosting, and SSR compute

Quick answer

Amplify Hosting charges for build minutes (around $0.01/minute), stored build artifacts (~$0.023/GB-month), data served (~$0.15/GB), and, for server-rendered apps, SSR compute per request and duration. A static site is cheap; SSR and high traffic drive the bill. Cache aggressively and keep builds fast.

Amplify Hosting deploys and serves web apps from your Git repository. Its bill has four parts, and which ones matter depends on whether your app is static or server-rendered.

The four lines

Dimension	Rate (approximate)
Build and deploy	~$0.01 / build minute
Hosting storage	~$0.023 / GB-month
Data served	~$0.15 / GB
SSR compute	Per request + duration (server-rendered apps)

Static sites are cheap

For a static or client-rendered app, you pay a little for builds, a little for storage, and for the data served to visitors. Amplify serves through a CDN, so cached content is efficient, and a modest site costs a few dollars a month. Data served is usually the largest line, and it behaves like CloudFront egress.

SSR is where cost grows

Server-side rendering adds compute billed per request and duration, similar to Lambda. A high-traffic SSR app runs that compute on every uncached request, so the bill scales with traffic and with how much rendering each request does. Caching rendered pages and using static generation where possible deflects that compute, the caching lever again.

Keeping Amplify cost down

Keep builds fast and infrequent (they bill per minute), cache aggressively at the CDN so data-served and SSR compute both fall, prefer static generation over per-request rendering where the content allows, and prune old build artifacts you no longer need. For a purely static site, Amplify is one of the cheaper ways to host; the cost conversation is really about SSR and traffic.

FAQ

How is Amplify Hosting priced?

By build minutes (around $0.01 per minute), stored build artifacts (about $0.023 per GB-month), data served to visitors (about $0.15 per GB), and, for server-rendered apps, SSR compute billed per request and duration.

Is Amplify Hosting expensive for a static site?

No. A static or client-rendered app pays a little for builds and storage plus data served through the CDN, typically a few dollars a month for a modest site. SSR and high traffic are what drive cost up.

Why is my Amplify SSR cost high?

Server-side rendering bills compute per request and duration, so a high-traffic app runs rendering on every uncached request. Cache rendered pages, use static generation where possible, and reduce per-request work to lower it.

How do I reduce Amplify Hosting cost?

Keep builds fast and infrequent, cache aggressively at the CDN so data-served and SSR compute fall, prefer static generation over per-request rendering, and prune old build artifacts. Caching is the biggest lever for SSR and traffic-driven cost.

Is data served the main Amplify cost?

For static sites, usually yes, and it behaves like CloudFront egress at about $0.15 per GB. For SSR apps, the rendering compute can exceed data served on high-traffic sites. Which dominates depends on your app type and traffic.

Does C3X estimate Amplify cost?

Amplify cost is driven by build minutes, data served, and SSR requests, which are usage inputs. C3X prices the surrounding infrastructure, and you model build frequency and traffic to estimate the Amplify charges.

What to do next

Estimate the infrastructure around your app before you ship it. C3X reads your Terraform and prices your resources against a live catalog. Start with the quickstart.