Skip to main content

Fix: api.hashpass.tech DNS Configuration

Manual recovery reference only. Normal releases should use the target-account web pipeline and should fail if /api/config/versions is stale.

Current Problem​

api.hashpass.tech should point to the target-account API Gateway custom domain. If you're getting 404 errors or redirects, the DNS record or API mapping is still stale.

Solution Options​

Prerequisites:

  • API Gateway must be configured with custom domain api.hashpass.tech
  • Lambda function must be deployed

Steps:

  1. Get API Gateway Domain Name:

    • Go to API Gateway Console → Custom Domain Names
    • Find api.hashpass.tech domain
    • Copy the "API Gateway domain name" (e.g., d-xxxxx.execute-api.us-east-1.amazonaws.com)

  2. Update DNS in Route 53:

    • Go to Route 53 → Hosted Zones → hashpass.tech
    • Find CNAME record for api
    • Update the value to the API Gateway domain name
    • Save

  3. Wait for DNS propagation (usually 5-15 minutes)

  4. Test:

    curl https://api.hashpass.tech/api/config/versions

Option 2: Use a Different Subdomain for the API​

If you need a separate hostname for testing or staging:

  1. Create new subdomain (e.g., api-gateway.hashpass.tech or api-proxy.hashpass.tech)

  2. Configure in API Gateway:

    • Create custom domain with new subdomain name
    • Map to your API

  3. Update DNS:

    • Create CNAME record for new subdomain
    • Point to API Gateway domain

  4. Update frontend code:

    • Change EXPO_PUBLIC_API_BASE_URL to new subdomain

Option 3: Use a Different Edge Platform (Alternative)​

If API Gateway is not the right fit, choose a different edge platform that supports your runtime and update DNS accordingly:

<your-deploy-command>

Verification​

After making DNS changes:

# Check DNS resolution
dig api.hashpass.tech

# Should show API Gateway domain, not CloudFront
# Example: d-xxxxx.execute-api.us-east-1.amazonaws.com

# Test API endpoint
curl https://api.hashpass.tech/api/config/versions

Current DNS Status​

Based on verification:

  • api.hashpass.tech → stale DNS target or missing API mapping ❌
  • Should be → the API Gateway custom domain ✅

Next Steps​

  1. If API Gateway is configured:

    • Update DNS CNAME to point to API Gateway domain
    • Wait for propagation
    • Test endpoint

  2. If API Gateway is NOT configured:

    • Follow API-GATEWAY-TROUBLESHOOTING.md to set up API Gateway first
    • Then update DNS

  3. Alternative:

    • Use Cloudflare Pages for API routes (simpler, free)
    • Or use Netlify Functions