Skip to main content
Connect CloudAMQP with a Customer API key to sync team members with their two-factor status, instances and VPCs, and run access and MFA reviews. Read-only. Data feeds into your Access accounts and Inventory pages.
Read-only access. DSALTA only reads data from this integration. It never creates, modifies, or deletes anything in your environment, and every remediation step is performed by your team directly in the third-party product.
What you’ll see. The Access page lists the members of the CloudAMQP team the key belongs to. CloudAMQP’s team roster carries no name field, so each row shows the member’s email address in place of a name, together with their CloudAMQP roles (for example Admin, or Member when none is reported). CloudAMQP reports no account status and cannot tell a pending invitation from a member, so every row — including an invited address that has not yet accepted — is shown as Active and stamped with the date of the sync. CloudAMQP does report per-member two-factor authentication, so the MFA column shows Yes or No, and is blank (a dash) for a member whose record carries no value.
DSALTA collects this integration’s data when you connect it — you can refresh it at any time with Sync from integrations on the Integrations page. The compliance checks below re-run once a day at 02:00 America/New_York.

​
What DSALTA reads

DSALTA reads the CloudAMQP team roster — email addresses, roles and two-factor status — which appears on your Access page; and your CloudAMQP instances and VPCs, which appear on your Inventory page, each instance with its region, plan, provider and tags, and each VPC with its region, subnet and tags. An instance’s detail record, which contains the instance’s own Console API key, is never read, and neither are the broker’s own RabbitMQ or LavinMQ users.It calls these CloudAMQP endpoints on customer.cloudamqp.com/api:
  • /team
  • /instances
  • /vpcs
Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your CloudAMQP environment.

​
Troubleshooting

The key is not the account-level Customer API key. CloudAMQP has two screens labelled API Access: the one on an instance’s detail page shows that instance’s Console API key, which cannot list your team and is rejected. Create the key on Account settings → API Access instead. Accounts created through the Heroku add-on cannot use the Customer API at all.
Instances and VPCs are read best-effort after the team roster: a failure on either call leaves that part of the Inventory page empty without failing the sync, and an account that has not created an instance yet has nothing to list. Click Sync from integrations on the Integrations page to retry.
CloudAMQP’s roster has no status field and no separate list of invitations, so an invited address is indistinguishable from a member until it is removed from Account settings → Team.
Open Integrations in the DSALTA sidebar, stay on the Connected tab, and click Manage on the integration’s card. Open the Status tab: it shows either Connected and working properly or Connection issues detected.Use the Status tab, not Overview — Overview always reports Connected regardless of the real state.
On an integration-powered check, Failed normally means DSALTA was blocked rather than that you are non-compliant. Open the test, go to Source Data, and read the result code: 403 is a missing permission, 428 is a setting DSALTA still needs, 500 is a failure on DSALTA’s side.A real compliance gap shows 207 and leaves the test looking Completed. See Understanding Test Results.
Compliance checks re-run once a day at 02:00 America/New_York. To refresh sooner, open Integrations → Connected and click Sync from integrations at the top right — it refreshes every connected integration at once.
There is no Reconnect, Repair or Refresh Token button. The only repair available is to disconnect and connect again.
Disconnecting is destructive and cannot be undone. DSALTA removes the access records, inventory, vulnerabilities, code changes, incidents and device records collected from this integration, and deletes the test results tied to the connection. Export anything you still need as audit evidence first — see Integration errors.
That is expected. Configure scope is read-only — it shows what DSALTA is permitted to read, and has no Save action. To change what DSALTA can see, change the permissions on the credential in the third-party product, then disconnect and connect again.