Manage cloud accounts
The Cloud accounts page lists every connected AWS account. Open an account to review its status, adjust settings, and manage the connection.
Accounts list
Each account shows its name and AWS account ID, the provider (AWS), whether remote command (SSM) is enabled, the connection Status, the owner, and when it was last synced.
Account status can be:
- Active — connected and syncing.
- Pending / Verifying — connection is being set up or validated.
- Failed — either verification failed, or three discovery scans in a row failed. Alpacon stops scanning an account in this state, so fix what the connect panel reported and bring the account back as described in Recover a failed account. See also Connect an AWS account.
- Disabled — connection is turned off.
Account settings
Open an account to view its Configuration:
- Auto-provision agent — automatically install the agent on newly discovered instances.
- Remote command — allow agent installation via AWS SSM.
- Sync interval — how often Alpacon refreshes the inventory (default every 5 minutes).
- Registration token — the server registration token used when onboarding instances.
Click Edit to change any of these settings, or to pause background discovery (Sync enabled).
The account detail page also shows an inventory summary (total instances, how many have the agent installed, and how many are pending) and the granted IAM role—AlpaconCrossAccountRole- followed by the stack’s ID, unique per connection. An account connected with an earlier template version has a role named AlpaconCrossAccountRole, with no suffix.
Sync and verify
- Sync now — queue an immediate inventory refresh instead of waiting for the next scheduled sync.
- Verify credentials — re-test that Alpacon can assume the account’s IAM role. On a failed account, the failure banner offers the same check instead; see below. Not available on a Pending account that hasn’t received its CloudFormation callback yet—wait for the callback, or continue in the connection wizard instead.
Find this account’s stack
Each account has its own CloudFormation stack in AWS, named AlpaconConnect- followed by the first 8 characters of the ID at the end of the account detail page’s address. Other accounts connected from the same AWS account and region have stacks with other suffixes, so match the suffix before you delete anything. An account connected before per-account stack names were introduced uses AlpaconConnect with no suffix.
Recover a failed account
When an account fails, its page shows a banner with the last error, if there is one, and two actions. Pick the one that matches what is left in AWS:
- Retry verification — the IAM role still exists in AWS. Alpacon checks the same role again; once that succeeds, the account is active again and a new scan starts on its own.
- Reconnect — the CloudFormation stack or its IAM role is gone. First delete this account’s stack in AWS: the new stack gets the same stack name and IAM role name, so AWS refuses to create it while the old stack exists. After you confirm, the account goes back to pending, its current credentials are cleared, and the connect wizard opens at the Quick Create step. Create the new stack from the same AWS account; a different AWS account is refused.
Disconnect an account
Click Disconnect account and confirm. The account stops syncing, and its instances leave the instance inventory. The EC2 instances in AWS are untouched, and servers you already onboarded from them keep running in Alpacon. To fully revoke Alpacon’s access, delete this account’s CloudFormation stack in your AWS account.