CloudSmart Docs

Appearance

Getting started ​

CloudSmart works against the AWS accounts you connect. Connecting an account is a short, guided flow with four steps — Details → Deploy → Connect → Data feeds: you name the account, deploy a small CloudFormation access template into it, let CloudSmart verify the connection, and register your marketplace data feeds. Once an account is verified, its dashboards and features light up.

The wizard keeps your progress — if you close it mid-way, the accounts list offers Resume setup to pick up where you left off.

1. Details — add an AWS account ​

From Accounts & Setup, start Add AWS account and provide:

  • Account name — how the account appears in the account switcher.
  • AWS account ID — the 12-digit seller account you use for AWS Marketplace.

2. Deploy — launch the access template ​

CloudSmart never asks for AWS keys. Instead it uses a CloudFormation stack that creates a role (CloudSmartAccess) CloudSmart can assume into your account, scoped to the capabilities the app needs, plus the S3 bucket and SNS topic that receive your AWS Marketplace data feeds.

First choose a deployment mode:

  • Feenix + CloudSmart (recommended) — one stack onboards both Feenix and CloudSmart.
  • CloudSmart only (standalone) — CloudSmart data feeds and access only.

Then use Open AWS Console — a one-click quick-create link that opens the AWS CloudFormation console with everything pre-filled. The stack deploys in us-east-1. Two parameters need care:

  • Timestamp — pre-filled by CloudSmart; the created resource names are derived from it. Leave it exactly as it is.
  • ExternalID (Feenix mode only) — this 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.

Create the stack, then choose I've launched it — continue.

3. Connect — verify ​

CloudSmart polls for your stack automatically and connects as soon as it comes online; you can also click Verify now once the stack shows CREATE_COMPLETE. The result shows:

  • Role reachable — including which role answered (normally CloudSmartAccess; a legacy per-feature role still works but the app will suggest consolidating — see below).
  • Each feature (offers, CRM, dashboards, and so on) lights up as its permissions are found.
  • Any missing actions are listed — partial results are fine; features light up per account as permissions land. If something is missing, update the stack to the latest template.

The first account you add becomes the default in the account switcher.

4. Data feeds — register your storage with AWS ​

The last step tells AWS Marketplace where to deliver your data feeds. The wizard hands you the values with copy buttons:

  • Amazon S3 bucket ARN and SNS topic ARN — created by your stack.
  • KMS key ARN — copy the DFKMSKeyArn value from your stack's Outputs tab and save it; CloudSmart keeps it with the account and pre-fills it next time.

Use Open customer data storage to open the AWS Marketplace Management Portal's Set up customer data storage page, paste the three values into the matching fields, and choose Submit. AWS starts delivering feeds to your bucket.

If the wizard doesn't have the ARNs, read all three from the stack's Outputs tab in us-east-1: DFS3BucketArn, DFSnsTopicArn, DFKMSKeyArn.

Keeping accounts current ​

The accounts list shows a maintenance badge on any account that needs attention, with a matching action that opens a tailored Stack maintenance & migration checklist. Everything keeps working while you follow it.

  • Update available → Update stack. In the CloudFormation console, select your stack (cloudsmart-feenix, or cloudsmart-datafeeds in CloudSmart-only mode), choose Update → Replace current template → Amazon S3 URL, paste the template URL from the dialog, keep every existing parameter — especially Timestamp — wait for UPDATE_COMPLETE, then Re-verify.
  • Consolidate access → your account connects through older per-feature roles. Deploy the unified stack once (pick your mode, launch the pre-filled quick-create link), then Re-verify after CREATE_COMPLETE.
  • Migration needed → you still use the old Customer Onboarding (push-model) stack. Follow the five steps in order: deploy the new stack → wait for Verified → re-register data storage in the AWS Marketplace portal with the new ARNs → confirm your dashboard still receives data after the next delivery → only then delete the old stack (the one whose Resources tab lists CrossSyncLambda). Deleting it earlier stops your data feeds.

Once an account uses the unified CloudSmartAccess role, the superseded per-feature stacks (from POTemplate.yaml, CRMTemplate.yaml, WATemplate.yaml — roles TenantPrivateOffers, TenantCRMConnect, TenantCustomLens) can optionally be deleted. Keep the stack that created the CustomerSaas role if you use the Storefront — it is still required for Storefront offer creation.

Removing an account from CloudSmart only removes the registration (after an in-app confirmation) — the CloudFormation stack in your AWS account is not touched.

What's next ​

Stuck on setup? See the FAQ for the most common connection errors.