Deploy Your AWS Amplify Frontend
Use Amplify's backend services without the AWS Console for deploys.
Last updated: February 20, 2026How it works
AWS Amplify backend + ZeroDeploy frontend.
AWS Amplify's backend services (Cognito for auth, AppSync/API Gateway for API, S3 for storage) run in AWS independently of Amplify Hosting. Your frontend — hosted on ZeroDeploy — uses the Amplify JS libraries to connect to these services at runtime. You get AWS's backend without AWS's hosting complexity.
Deploy in 3 steps
From zero to live in under a minute.
Create your frontend project
Scaffold a new project with Vite. Add the AWS Amplify SDK and connect it to your backend.
npm create vite@latest my-app -- --template react-ts Build for production
Run the build command to generate static output in dist/.
cd my-app && npm run build Deploy to ZeroDeploy
One command to push your frontend to the edge. It's live in seconds.
zerodeploy deploy --dir dist Configuration tips
Connecting your frontend to AWS Amplify.
- Export your Amplify config using
amplify pullto generateamplifyconfiguration.json. Import it in your app:Amplify.configure(config). - Store any custom API endpoints as environment variables:
VITE_API_ENDPOINT. The Amplify config file handles most service URLs automatically. - Build locally with
npm run build. Amplify's backend provisioning (amplify push) is separate from your frontend deploy — do it before building your frontend.
Things to know
AWS Amplify-specific tips to avoid common pitfalls.
- Amplify backend and frontend deploy separately. Run
amplify pushto provision/update backend resources, then build your frontend and deploy withzerodeploy deploy. - Cognito auth callback URLs need your ZeroDeploy domain. Update them in the Amplify config or directly in the AWS Console (Cognito > App client settings).
- For SPAs with client-side routing, create a
public/_redirectsfile with/* /index.html 200. Learn more about redirects → - The
amplifyconfiguration.jsonfile contains your API endpoints and auth config. It's safe to include in your bundle — these are client-side identifiers, not secrets. Never includeaws-exports.jswith secret keys.
Everything you need
Host your AWS Amplify frontend with the features you'd expect from a modern hosting platform.
Instant Deploys
Push to deploy in under 5 seconds. No queues, no build minutes to worry about.
Preview URLs
Every deployment gets a unique URL. Share any version instantly with your team.
Custom Domains
Connect your own domain with automatic SSL. Just add a CNAME and you're live. Learn more →
GitHub Actions CI/CD
Deploy on every push with GitHub Actions. Get PR comments with preview URLs. Set up CI/CD →
Built-in Analytics
See traffic, top pages, referrers, and countries right in your dashboard. No third-party scripts. Learn more →
Forms That Just Work
Add action="/_forms/contact" to any form. Submissions appear in your dashboard. Learn more →
Frequently asked questions
Can I use AWS Amplify backend without Amplify Hosting?
Yes. Amplify's backend services (Auth, API, Storage, DataStore) are separate from Amplify Hosting. Your frontend can be hosted anywhere — including ZeroDeploy — and still connect to all Amplify backend services using the Amplify JS libraries.
Why use ZeroDeploy instead of Amplify Hosting?
ZeroDeploy deploys in under 5 seconds (vs 1-5 minutes with Amplify). You get built-in forms and privacy analytics. Pricing is a flat $29/month instead of pay-per-use. And you don't need an AWS account or IAM permissions just to deploy a frontend.
Do I still need the Amplify CLI?
Yes — for managing your backend resources (amplify push, amplify pull). You don't need it for frontend deployment. Use the ZeroDeploy CLI for that: zerodeploy deploy --dir dist.
How do I handle Cognito auth redirects?
Add your ZeroDeploy URL to the callback URLs in your Cognito app client settings. You can update this via the Amplify CLI (amplify update auth) or directly in the AWS Console under Cognito > User Pools > App client settings.
Also works with
ZeroDeploy hosts frontends for any backend-as-a-service.
Framework deploy guides
Simpler deploys for your Amplify frontend
Use Amplify's backend. Skip Amplify's hosting complexity. Deploy with one command.