docs: add self-hosting documentation#8605
Conversation
… Amplify Hosting - Rewrite deploy-and-host/index.mdx with two-path layout (managed vs self-managed) - Add self-hosting card to how-amplify-works overview - Update homepage and platform landing Deploy sections with self-hosting item - Add self-hosting alternative section to hosting stub page - Add self-hosting mention to gen2 migration feature-matrix - Update FeatureLists test to match updated link text
…hing into amplify-hosting - Rename hosting/ to amplify-hosting/ (rewrite stub as full overview page) - Move all fullstack-branching child pages under amplify-hosting/ - Remove fullstack-branching/ section entirely - Update deploy-and-host/index.mdx (remove "Shared development tools", add sandbox note) - Fix all internal links referencing old paths - Keep self-hosting/ and sandbox-environments/ as sibling sections
|
@adrianjoshua-strutt, since a file was deleted from the
|
…ss all deploy pages - Landing pages: Change "Deploy your app" button from external Amplify console link to internal /deploy-and-host/ overview with both hosting options - NextPrevious component: Fix stale /deploy-and-host/fullstack-branching/ path to /deploy-and-host/amplify-hosting/ - Concepts page: Update "Fullstack Git-based environments" section to mention self-managed hosting; fix em-dashes and banned words (leverage, simply) - Quickstarts (React, Vue, Angular, Next.js pages/app router, Android): Add callout noting self-hosting alternative; update "Publishing changes to cloud" sections to reference both deployment paths - Manual installation: Link to /deploy-and-host/ overview instead of only amplify-hosting - MCP workflows: Add self-managed hosting to CI/CD and deployment sections - deploy-and-host fragment: Rewrite to present both Amplify Hosting and self-managed hosting as equal options - README: Update outdated directory tree to reflect current structure
Split the Deploy section on both the platform-specific and root landing pages into a two-column layout: Left column (Amplify Hosting): - Description of managed Git CI/CD hosting - deploy-cycle.png diagram - Sub-features: sandboxes, fullstack branches, GUI - Link to /deploy-and-host/amplify-hosting/ Right column (Self-managed hosting): - Description of CDK-based self-hosting - Code example showing defineHosting usage - Sub-features: CDK escape hatches, custom CI/CD, domains + WAF - Link to /deploy-and-host/self-hosting/ The Customize section remains unchanged below the Deploy section.
…x CI - Add 301 redirects for hosting/ → amplify-hosting/ path moves - Add 301 redirects for fullstack-branching/ → amplify-hosting/ path moves - Update existing gen1/gen2 redirects to target amplify-hosting/ - Fix generate-sitemap test to reference new amplify-hosting paths - Add codeconnections and xlarge to cspell dictionary
…sting - Create deploy-cycle.svg showing Amplify Hosting flow - Create deploy-cycle-self-hosted.svg showing self-managed flow - Replace PNG image reference with SVG in both index pages - Replace code examples in right column with self-hosting SVG - Remove unused ExportedImage imports
- Fix incorrect flow showing sandbox→git→deploy (wrong) - Correct diagram shows two parallel concepts: 1. Developer sandboxes ↔ cloud (bidirectional, for local dev) 2. Git branches → Amplify Console (for production deploy) - Match original PNG color scheme (#193549 background, #9469d6 purple) - Use two separate cloud icons above each sandbox with bidirectional arrows - Add visual separator between development and deployment sections - Update self-hosted variant with same corrected layout
Redesigned both deploy-cycle diagrams to clearly communicate the three-phase deployment story: 1. DEVELOP - Per-developer cloud sandboxes with localhost, showing ampx sandbox bidirectional sync 2. GIT REPOSITORY - Branches (dev, main, feature) as pills 3. DEPLOY - Per-branch environments with unique URLs Key improvements: - Added localhost:3000 to show sandboxes are for local development - Added per-branch URLs (dev.example.com, app.example.com, etc.) - Removed ugly unfilled cloud emoji paths - Replaced with clean rectangular section containers - Added proper arrow labels (git push, auto-deploy) - Increased viewBox to 600x500 for better spacing and readability - Used proper gradient fills and consistent color palette - Self-hosted variant shows CloudFormation stacks with CloudFront URLs
- Increase SVG font sizes (20px section headers, 16-18px body text) - Reduce viewBox from 600×520 to 520×480 so content fills the space - Fix arrows to connect directly to section box edges (no floating gaps) - Center branch pills and section labels horizontally - Lengthen self-managed hosting feature descriptions to match left column
- Use "beta" and "main" as branch names in both SVGs - Self-hosted: show URLs (beta.example.com, app.example.com) instead of CloudFormation stack names - Self-hosted: remove CloudFormation branding - Self-hosted: simplify arrow label to just "deploy"
…, shorten landing page text
|
Redirects are already configured in
All pages moved from |
| import { defineHosting } from '@aws-amplify/hosting'; | ||
|
|
||
| export const hosting = defineHosting({ | ||
| framework: 'nextjs' |
There was a problem hiding this comment.
Since we are auto detecting the framework, can omit this framework param and also it is already mentioned in configuration page.
There was a problem hiding this comment.
Will do. Thanks!
| import { defineHosting } from '@aws-amplify/hosting'; | ||
|
|
||
| export const hosting = defineHosting({ | ||
| framework: 'nextjs' |
There was a problem hiding this comment.
same here, Since we are auto detecting the framework, can omit this framework param and also it is already mentioned in configuration page.
- Fix AWS service name references to use full official names on first mention: - CloudFront → Amazon CloudFront (first mention), CloudFront (subsequent) - S3 → Amazon S3 - Lambda → AWS Lambda - Route 53 → Amazon Route 53 - CodePipeline → AWS CodePipeline - CodeBuild → AWS CodeBuild - CloudFormation → AWS CloudFormation - WAF → AWS WAF - CDK → AWS CDK - DynamoDB → Amazon DynamoDB - SQS → Amazon SQS - In tables, headings, and meta descriptions: always use full name - In code blocks: leave as-is - Lambda@Edge stays as-is (official name) - AWS CDK escape hatches: use full name on first mention Files updated: - define-hosting/index.mdx - define-pipeline/index.mdx - self-hosting/index.mdx - external-pipelines/index.mdx - frameworks/index.mdx - getting-started/index.mdx - deploy-and-host/index.mdx - [platform]/index.tsx - index.tsx
- Rename 'SPA' column to 'Static / SPA' in feature matrix - Rename 'Nuxt' to 'Nuxt / Nitro' in framework list and feature matrix - Update Nuxt detection to mention 'nuxt' or 'nitropack' in dependencies - Update SPA description to include 'Static' prefix and use full product names (Amazon S3, Amazon CloudFront) - Maintain table alignment
…d pipeline Add build output directory override, storage configuration, and content security policy sections to define-hosting page. Add self-mutation toggle, cross-account deployments, disable auto-trigger, and custom synth install commands sections to define-pipeline page.
Preview: https://d2a8cehsb9j05d.cloudfront.net
Adds documentation for the self-managed hosting feature (
defineHosting,definePipeline,ampx deploy).Pages added
/deploy-and-host/self-hosting/— Overview/deploy-and-host/self-hosting/getting-started/— Install and first deploy/deploy-and-host/self-hosting/define-hosting/— Configure hosting (domains, WAF, compute, CDK escape hatches)/deploy-and-host/self-hosting/define-pipeline/— Set up CI/CD pipeline/deploy-and-host/self-hosting/external-pipelines/— GitHub Actions, GitLab CINavigation
Updated
src/directory/directory.mjsto add the self-hosting section under deploy-and-host.Related: aws-amplify/amplify-backend#3211