Install and operate
Troubleshooting
The messages you are most likely to meet, and what to do about each. If none of these
helps, build a support bundle (how) and send it to us.
Starting Lagoria Control#
| You see | What to do |
|---|
| "Open the link printed in your terminal" | The token in the address is from an earlier run. Use the link Lagoria Control printed this time. |
| No profiles in the list | Your ~/.aws folder is not mounted, or on Linux the container cannot read it. Check the -v "$HOME/.aws:/home/lagoria/.aws" part of the command, and add --user "$(id -u):$(id -g)" on Linux. Or paste access keys instead. |
| Credentials rejected (SSO profile) | The sign-in expired. Run aws sso login --profile <name> on your machine, then choose Check access again. |
Checks#
| You see | What to do |
|---|
| Claude Sonnet 4.6: agreement NOT_AVAILABLE | Accept it once in the Bedrock console (how). It can take a few minutes to show as accepted; run the checks again. |
| Cohere models: not accepted yet | A warning only. The deploy accepts these agreements. Continue. |
| Permissions could not be checked | A warning only: the identity may not run the permission self-check. The deploy names any missing permission. |
| Region mismatch | Use the same region in AWS access and the environment settings. |
During a deploy#
| You see | What to do |
|---|
| "Your account is currently being verified" | The AWS account is new. AWS verifies it within about two hours. Wait, then deploy again. After two hours, write to aws-verification@amazon.com. |
| The deploy stopped after the laptop slept or the network dropped | Start Lagoria Control again and deploy again. AWS keeps building while you are away, and a repeat reuses what is done. |
| "stack is in UPDATE_IN_PROGRESS" or similar | An earlier deploy is still finishing in AWS. Wait for it (CloudFormation console), then deploy again. |
| "Starting parked graph" | Not an error. The knowledge graph is stopped out of hours and is being started; this can take 10 to 15 minutes. |
| Access denied for an action | The identity is missing that permission. Use an administrator, or add the named permission. |
After a deploy#
| You see | What to do |
|---|
| Custom domain not live yet | Normal for up to about 30 minutes while the certificate is issued. If your DNS is not in Route 53 in this account, add the records listed in the deploy log. Meanwhile use the AWS address shown on the Overview. |
Sign-in shows redirect_mismatch | Register the redirect URI from Configuration in your identity provider's application. |
| Nobody can claim admin | Add owner emails in Configuration and reinstall. |
| Search results stay empty | Check the AI part on the Overview. If AWS refused a Cohere agreement, the support bundle shows why. |
| Slow under load, throttling errors | The account may still have the default Lambda limit of 10. Request 1,000 in Service Quotas. |
