Skip to main content

AWS Manual Setup in Spotto

Most people should connect with Launch Stack. Set up manually when you need:

  • a custom role name or path;
  • a billing bucket in a separate account, or a legacy Cost and Usage Report;
  • policies reviewed and applied through your own change process.

You type the details that Launch Stack would discover. Where Do I Find This? beside each field, and find your AWS IDs, show where each one is.

Step 1: Open The Setup​

  1. Open Connectors > Cloud Accounts, select Create, then AWS.
  2. Under Manual Setup, select Organization or Single Account.

The page has four steps: Accounts, Billing, Deploy Access and Strategy. Next takes you through them, and Create appears on the last step.

To change a saved account or organization later, select the edit icon on its row in Cloud Accounts. The same steps appear as tabs.

Step 2: Enter The Accounts​

FieldNotes
Organization Name · Organization IDOrganizations only. Both required.
Account ID · Account NameOne row per account. Both required. Enter the management account first.
Management Account IDOrganizations with more than one account.
IAM Role ARNFilled in as arn:aws:iam::<account-id>:role/SpottoReadOnlyRole. Select Use a Custom Role ARN only for a different name or path.

For many accounts, select Paste Account IDs and paste them separated by new lines, commas or spaces.

Optionally:

  • select Organization Commitments Planning on the management account, for Reserved Instance and Savings Plans planning across the organization;
  • under Excluded Accounts, select Add Exclusion for accounts you're leaving out on purpose, so the gap is explained later.

Step 3: Add Billing​

Billing is required: Create stays unavailable until the account that holds the bill has a validated billing source. Member accounts don't need their own. Add it before you deploy the roles, so they get billing access the first time.

On Billing, select Add Billing Source and enter the export details. See add a billing source.

Step 4: Deploy The Role In Each Account​

On Deploy Access, choose a method:

MethodIn SpottoIn AWS
CloudFormationFor each account, select Get Template, then Download CloudFormation Template.Create a stack from the file.
Manual IAMFor each account, select Generate Role Instructions, then Copy Role Instructions.Create the role by hand.

Each account's role differs slightly, depending on what it does:

Every account gets the AWS managed ViewOnlyAccess and SecurityAudit policies and SpottoReadOnlyAccess, for resources, configuration and security evidence. Member account: nothing else. Management account: SpottoBillingExportRead to read the export definition if it is defined there, and SpottoCommitmentsPlanning if organization commitments planning is selected. Billing storage account: SpottoBillingExportRead to read the files in the export folder and nothing else in S3. Standalone account: the export definition and files in the same role, and commitments planning if selected. One account can have several duties.Every account gets the AWS managed ViewOnlyAccess and SecurityAudit policies and SpottoReadOnlyAccess, for resources, configuration and security evidence. Member account: nothing else. Management account: SpottoBillingExportRead to read the export definition if it is defined there, and SpottoCommitmentsPlanning if organization commitments planning is selected. Billing storage account: SpottoBillingExportRead to read the files in the export folder and nothing else in S3. Standalone account: the export definition and files in the same role, and commitments planning if selected. One account can have several duties.

All roles trust the same External ID. It's fixed for your company, so roles you've already deployed don't change when you add accounts.

For many member accounts, deploy the hosted member account StackSet from the management account instead of one stack per account.

Create A Stack From The Downloaded Template​

  1. Sign in to the account and open CloudFormation. Any Region works for a role-only template.
  2. Select Create stack, then With new resources (standard).
  3. Choose Upload a template file, select the file, then select Next.
  4. Enter a stack name, such as SpottoReadOnlyRole, then select Next twice.
  5. Tick the IAM acknowledgement and select Submit.
  6. Wait for CREATE_COMPLETE.

When an account's billing or purposes change, download its new template and update the stack with Replace existing template.

Deploy The Role Manually​

  1. In the account's IAM console, create a role named SpottoReadOnlyRole with Custom trust policy, and paste the trust policy from the role instructions.

  2. Attach the two AWS managed policies (Add permissions > Attach policies):

    PolicyARN
    ViewOnlyAccessarn:aws:iam::aws:policy/job-function/ViewOnlyAccess
    SecurityAuditarn:aws:iam::aws:policy/SecurityAudit

    From the CLI: aws iam attach-role-policy --role-name SpottoReadOnlyRole --policy-arn <ARN>, once for each.

  3. Add each inline policy with the exact name and JSON shown: SpottoReadOnlyAccess, plus SpottoBillingExportRead and SpottoCommitmentsPlanning where listed.

If your standards require it, you can create the inline policies as customer managed policies instead. Each fits within the managed-policy size limit.

When an account's billing changes, generate its instructions again and replace SpottoReadOnlyAccess. Don't add a second copy: its S3 deny changes with billing. See permissions.

Step 5: Create And Check The Status​

After deploying the roles, select Check Details to check the configuration without saving. New or changed billing sources are checked live in AWS: Spotto reads the authoritative export definition, checks its destination and bucket encryption, and tests storage access. See what the preflight checks, including the limits when no files have arrived.

Select Create, or Update for a saved configuration, to repeat those checks and save. A failed preflight saves nothing and starts no scan. After a successful save, Spotto returns you to Cloud Accounts and checks each account in the background:

1 Prove each role: assume SpottoReadOnlyRole with your External ID and confirm AWS returns the expected account. Outcome: ready to scan, or AWS Role Could Not Be Used. 2 Check each billing export: the export definition must match what you entered, then Spotto lists and reads a delivered file. Outcome: validated, waiting for AWS to deliver the first files, or Billing Source Needs Attention. 3 Scan and import: the first scan runs for every account whose role works, even while billing waits for its first delivery, and cost history is imported for validated exports once files arrive. Each account and billing source is checked on its own, so one failure never holds up the rest. After you fix something in AWS, select Retry Validation.1 Prove each role: assume SpottoReadOnlyRole with your External ID and confirm AWS returns the expected account. Outcome: ready to scan, or AWS Role Could Not Be Used. 2 Check each billing export: the export definition must match what you entered, then Spotto lists and reads a delivered file. Outcome: validated, waiting for AWS to deliver the first files, or Billing Source Needs Attention. 3 Scan and import: the first scan runs for every account whose role works, even while billing waits for its first delivery, and cost history is imported for validated exports once files arrive. Each account and billing source is checked on its own, so one failure never holds up the rest. After you fix something in AWS, select Retry Validation.

Open the account or organization again to see AWS Setup Status:

StatusMeaning
Not Started or ValidatingStill checking. The panel refreshes on its own.
ReadyEvery role and billing source passed.
Partially ReadySome accounts or billing sources need attention, each with its fix.
FailedNothing passed yet. The fix is listed for each account.

After you fix something in AWS, select Retry Validation. For each message, see troubleshooting. To change, sync or remove accounts later, see manage connected AWS accounts.