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), or it was deployed in the wrong region — the template runs in us-east-1 only.
• The CloudSmart External ID doesn't match the one CloudSmart expects.
• The Timestamp parameter was edited at launch — it must be left exactly as pre-filled, since the created resource names are derived from it.

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

Where do I find the Feenix External ID?

In Feenix + CloudSmart mode, the stack's ExternalID parameter is Feenix's own trust ID, so CloudSmart cannot pre-fill it. In your Feenix portal, open step 2 Configure Cloud Formation, copy the External ID shown there, and paste it into the parameter before launching the stack.

My account shows a maintenance badge

The accounts list flags accounts that need attention; the matching button opens a tailored checklist:

• Update available / Update recommended → update your existing stack to the latest template (no new stack, no new resources), then re-verify.
• Consolidate access → you connect through older per-feature roles; deploy the unified stack once, then re-verify.
• Migration needed → you still use the old Customer Onboarding (push-model) stack; follow the five migration steps in order and delete the old stack last — see Getting started.

Everything keeps working while you follow the checklist.

What happens when I remove an account?

Removing an account (after the in-app confirmation) only deletes its registration in CloudSmart. The CloudFormation stack in your AWS account is not touched — nothing in AWS is deleted or changed, and you can re-add the account later.

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.