Agent Ready HTML

AWS Amplify Hosting: vendor profile

In short

The pages read describe no prerendering for client-rendered apps on Amplify Hosting. Later Next.js majors are not on its support page. Standard builds are free up to 1,000 minutes a month, then $0.01 a minute. New customers from 2025-07-15 get up to $200 in Free Tier credits.

At a glance

standards.txt aws-amplify-hosting

llms-txt               = no statement
markdown-negotiation   = no statement
markdown-twin          = no statement
initial-html           = partial
real-404               = partial
vary-accept            = no statement

0 supports, 2 partial or announced, 4 no statement.

AWS Amplify Hosting Host, CDN or edge product

Git-connected hosting on AWS for static sites, single-page apps and server-rendered Next.js apps; its redirect rules decide whether a missing path answers 404 or hands every URL to a client-side router.

Type
Host, CDN or edge product
Operator, as the facts below state it
Amazon Web Services
Home page
aws.amazon.com/amplify/hosting, answered HTTP 200 on 2026-11-05
Last read
5 November 2026

What it does for this layer

  • Amplify Hosting deploys server-side rendered apps built with Next.js versions up through Next.js 15, including image optimization and middleware. [primary source] source, read 5 November 2026.
  • AWS's Amplify documentation says SSG pages are prerendered at build time and SSR pages at request time, so the HTML content of each page arrives ready in the browser. [primary source] source, read 5 November 2026.
  • Amplify's Rewrite (200) rule type serves content from a destination address while the browser keeps the original URL, and AWS lists sending all single-page-app traffic to index.html as a common use. [primary source] source, read 5 November 2026.
  • Amplify's Not Found (404) rule type displays a destination page for addresses that do not exist, including pointing nonexistent paths of a web app to index.html for a client-side router. [primary source] source, read 5 November 2026.
  • AWS says an unexpected 302 from an Amplify app usually comes from redirect and custom header changes, and the fix is to re-enable the app's default 404 rewrite rule. [primary source] source, read 5 November 2026.
  • Amplify applies redirect rules from the top of the list down, so rule order decides which answer a path gets. [primary source] source, read 5 November 2026.
  • Amplify pricing lists the Standard build instance free up to 1,000 build minutes a month and then $0.01 per minute, data transfer out free up to 15 GB a month and then $0.15 per GB served. [primary source, 2026-11-05] source, read 5 November 2026.
  • Amplify pricing lists SSR requests free up to 500,000 a month and then $0.30 per million requests. [primary source] source, read 5 November 2026.
  • AWS says new customers from 2025-07-15 receive up to $200 in Free Tier credits that apply to Amplify, with a free plan available for 6 months after account creation. [primary source, 2025-07-15] source, read 5 November 2026.

Products and plans

Plans and prices as the vendor's own pages showed them on the date read.
ProductWhat it isPriceAs ofSource
AWS Amplify HostingHosting with CI/CD from Git for static, single-page and Next.js SSR apps, with redirect and rewrite rules and custom headers.Usage-based, with a free allowance
Free tier allowances, then 0.01 USD per build minute and 0.15 USD per GB served		2026-11-05source

Standards

The six standards this site tracks; no statement means the pages read said nothing.
StandardStatusWhat the vendor's pages saySource
llms-txtno statementNo llms.txt feature in the Amplify Hosting pages read.none
markdown-negotiationno statementNo Accept-header markdown feature in the Amplify Hosting pages read.none
markdown-twinno statementNo markdown copy feature in the Amplify Hosting pages read.none
initial-htmlpartialSSR and SSG Next.js apps arrive prerendered; plain single-page apps stay client-rendered.source
real-404partialRule types include Not Found (404); SPA setups rewrite unknown paths to index.html.source
vary-acceptno statementNot covered in the pages read.none

Checks on its own site

Plain-fetch checks ran on https://aws.amazon.com/amplify/hosting/; the Ora and Cloudflare scores cover the whole host aws.amazon.com.

Readings of aws.amazon.com, the vendor's own website, which describe that site and not the product.
ReadingResultDate
Home page requestHTTP 200; H1 in the initial HTML: yes; 326 words; 2 JSON-LD blocks2026-11-05
Request with Accept: text/markdownHTTP 200, text/html, Vary: accept-encoding2026-11-05
/llms.txt at the host rootHTTP 404, text/html, 295 KB2026-11-05
A made-up pathHTTP 301, redirect to /agent-ready-check-17sehjff/, then HTTP 4042026-11-05
Ora score, cached60, grade C2026-10-30
Cloudflare keyless scan20, L1 Basic Web Presence2026-11-05
Shared crawl rowoutside the ranked slice; home page HTTP 200; H1 in the HTML: yes; 1,524 words; JSON-LD types: ItemList; answers markdown: no; made-up path HTTP 404; llms.txt valid: no2026-11-04

What it does not do

  • Amplify Hosting does not prerender a plain React or Vue single-page app for agents; the HTML is whatever the build emits.
  • The Amplify Next.js support page stops at Next.js 15, so later majors are not listed as supported on that page.

Related pages on this site

Sources

  1. AWS Amplify Hosting: home page https://aws.amazon.com/amplify/hosting/, read 5 November 2026
  2. Amplify support for Next.js - AWS Amplify Hosting https://docs.aws.amazon.com/amplify/latest/userguide/ssr-amplify-support.html, read 5 November 2026
  3. Setting up redirects and rewrites for an Amplify application - AWS Amplify Hosting https://docs.aws.amazon.com/amplify/latest/userguide/redirects.html, read 5 November 2026
  4. AWS Amplify Pricing | Front-End Web & Mobile | Amazon Web Services https://aws.amazon.com/amplify/pricing/, read 5 November 2026

Last reviewed 5 November 2026