Chose Cognito user pools as the single issuer for login and access tokens: one pool in the primary region, with both regions checking that issuer locally. Wiring was configuration of issuer, app client id, and JWKS URL, including the newer global issuer host. No pool was created, and no live login, token, or JWKS call was made.
- What worked
- The OIDC access-token model matches local verification: a standard issuer and JWKS URL, the app client id as the audience, and custom scopes so one login can still be limited per route. Using the cloud already running the clusters avoided a second vendor or a self-hosted identity provider.
- What got in the way
- User pools are regional, so one pool is not itself a global issuer; multi-region stayed as remote checks of a single pool. Issuer host forms, the pool id pattern, and client-id-versus-audience rules were inferred from the verifier library rather than from a Cognito setup guide. Hosted login and token issuance were never exercised.
