Troubleshooting
This page collects the issues you're most likely to hit and how to resolve them. It's organized by the stage where the problem appears.
ESP CloudHub in your own AWS account
The ESP CloudHub stack failed
The esp-cloud-hub stack shows ROLLBACK_COMPLETE.
- Open the stack's Events tab. The first CREATE_FAILED event's Status reason says why. Most often it's an AdminTemporaryPassword missing an uppercase letter, lowercase letter, number or symbol.
- Delete the
esp-cloud-hubstack. If a stack namedesp-rainmaker-installer-stackexists, delete it too. - Start again from Step 2.
An administrator lost the temporary password, or it expired
The temporary password is valid for 7 days, and Forgot password? only works after the first sign-in. Someone with access to the AWS account can set a new temporary password with the AWS CLI:
aws cognito-idp admin-set-user-password --region us-east-1 \
--user-pool-id <CognitoUserPoolId> \
--username <administrator email> \
--password '<new temporary password>' --no-permanent
<CognitoUserPoolId> is in the esp-cloud-hub stack's Outputs tab. The administrator signs in with the new temporary password and is asked to set their own.
I can't find my ESP CloudHub address
Open the esp-cloud-hub stack in CloudFormation (region us-east-1) → Outputs → DashboardUrl.
Sign-in & organization
I don't have an account. On the login screen, click Need an account? Sign up to register. Your organization is created automatically the first time you log in.
"Select an active organization…" You belong to more than one organization and none is active. Use the organization switcher in the top navigation to choose one, then retry the action.
I can see the console but most actions are disabled. A new member has minimal access until an admin assigns a role. Ask your organization's admin to grant you the appropriate role (see Roles & access).
Connecting your AWS account
"You do not have permission to connect this account…"
Your role lacks the connect permission (tenant:connect) in the current organization. Ask an admin to grant it, or switch to an org where you have it.
AssumeRole: the connection fails right after Confirm & Continue.
Usually the CloudFormation stack isn't finished, or the role was created in the wrong account. Confirm the ESPDeploymentTrustRole stack shows CREATE_COMPLETE in the same 12-digit tenant account you registered, then click Confirm & Continue — try again. Make sure you weren't signed in to a different AWS account when you ran the setup link.
AssumeRole: the setup link opened the wrong account. The link must be opened while signed in to the tenant account. Switch accounts (or log out and back in) in the AWS console, then re-open the copied setup link.
SSO: "SSO accessToken has expired. Please re-login." SSO connections are valid for about 8 hours. When one expires, ESP CloudHub can't deploy until you reconnect. Open the tenant, choose AWS SSO, and repeat the authorize flow (Start URL → Authorize → Allow → select role). If you'd rather not deal with expiry, switch the tenant to AWS Trust Role, which does not expire.
SSO: the authorize page didn't grant access. On the AWS "Allow access to your data?" screen you must click Allow (not Cancel). If you cancelled, restart the SSO flow and click Allow.
General connect failure / want to start over. Click Try Again to return to the method picker, or Change connection method to switch between AWS Trust Role and AWS SSO, then retry.

