### Answer --- I don't have specific documentation or examples for deploying the Login V2 UI to AWS Amplify. The available deployment guidance covers Vercel and Docker Compose setups. [(1) ]() [(2) ]() However, since the Login V2 is a Next.js application, here are the key requirements that would apply to any deployment platform including Amplify: **Required Environment Variables:** - `ZITADEL_API_URL` – Your ZITADEL instance URL (no trailing slash) [(1) ]() - `ZITADEL_SERVICE_USER_TOKEN` – PAT from a service user with `IAM_LOGIN_CLIENT` permissions [(1) ]() [(2) ]() **Key Setup Steps:** 1. Create a service user with a PAT in your instance [(1) ]() 2. Assign `IAM_LOGIN_CLIENT` permissions to the user via `YOUR_ZITADEL_HOST/ui/console/instance?id=organizations` 3. Add your login domain to [trusted domains]() in ZITADEL [(1) ]() [(2) ]() **OIDC Proxy Requirements:** - Must run on HTTPS [(2) ]() - Must set `x-zitadel-public-host` header (your login app host) - Must set `x-zitadel-instance-host` header (your ZITADEL instance host) If you want to try a general approach, you could fork the [ZITADEL repo]() and adapt the Next.js login app for Amplify's build/deploy process. [(1) ](

Login UI amplify

Similar Threads