9. Verification Checklist

Verify these infrastructure components and the configuration to ensure Roost is fully configured.

1. oAuth Provider has redirect URI setup

2. ACM certificate is issued and attached to the ALB

3. Route 53 entry is present for DNS to ALB

4. ALB is associated with Target Group

5. Target Group has healthy EC2 target

6. Database is accessible

7. EC2 instance - “control plane” is showing 3 docker processes running (nestjs, react_app, console_proxy)

Verify Roost Controlplane by accessing the Enterprise DNS associated with the Hosted zone

Troubleshooting Roost

1. Check docker logs for nestjs container (verify that it is connected to the database

   docker logs -f --since 1m roost_roostai_nest_server_1

2. Check docker logs for react container to verify it is listening on port 4200

   docker logs -f --since 1m roost_roostai_react_app_1