FAQ

"This AWS account is already registered"

The AWS account ID you entered is already connected to CloudSmart.

• If it's registered to your tenant, it's already set up — find it in the account switcher and Accounts & Setup.
• If it's registered to another tenant, an account can only belong to one tenant at a time. Contact support to sort out ownership.

"Your plan includes one AWS account"

Your current plan is limited to a single AWS account, and you already have one connected. To connect additional accounts, upgrade to the CloudSmart Insights (Subscription) product, which includes unlimited AWS accounts. See Plans & tiers.

Verify fails with "could not assume role"

CloudSmart couldn't assume the CloudSmartAccess role in your account. Usually one of:

• The access stack isn't deployed (or was deleted).
• The CloudSmart External ID doesn't match the one CloudSmart expects.

Re-deploy the access template using the Launch / quick-create link from setup — it pre-fills the correct CloudSmart External ID — then click Verify again. See Getting started.

A feature is missing after I verify

Your account's access template is outdated and doesn't grant everything the newer features need. The verification result lists the missing actions — these are permissions in the current template that your deployed stack doesn't have yet. Update the stack with the latest template and re-verify; the missing features light up.

Dashboard shows "no data yet"

Dashboards are built per account after that account is first verified, so a not-ready state right after setup is expected while your dashboard is prepared. Use Check again to re-poll — the embed appears once it's ready. See Dashboard & Insights.

CRM connection or OAuth errors

If connecting your CRM fails, or a previously connected CRM stops syncing, the OAuth authorization likely expired or was revoked. Reconnect the provider from CRM Connect. See CRM Connect.