Skip to main content
Connect Elastic Cloud with an organization API key to sync organization members and hosted deployments, and run access reviews. Read-only.
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 your Elastic Cloud organization with their name, email, the organization-level roles assigned to them (for example organization-admin or billing-admin, or Member when they hold none) and the date they joined. Elastic Cloud reports no account status or MFA state on this endpoint, so every member is shown as Active with MFA Unknown. Deployment-level and project-level role assignments are not shown.
Only an Organization owner key can read the roster. Elastic Cloud lets you create API keys with narrower roles, but none of them can list organization members — a key without the Organization owner role connects but fails at the first sync.
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 Elastic Cloud organization member roster — names, emails, organization roles and join dates — which appears on your Access page; and your Elastic Cloud Hosted deployments, which appear on your Inventory page with their region, Elastic Stack version and health. Serverless projects are not part of the sync.It calls these Elastic Cloud endpoints:
  • /api/v1/organizations
  • /api/v1/organizations/{id}/members
  • /api/v1/deployments
Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Elastic Cloud environment.

​
Troubleshooting

The key is invalid, expired, or was created without the Organization owner role. Create a new key with that role, then disconnect and connect again — Elastic Cloud does not let you add a role to an existing key. Note that disconnecting permanently deletes the data already collected from Elastic Cloud.
Only Hosted deployments are listed. An organization that runs Serverless projects only, or whose deployments the key cannot see, shows no Inventory rows. Access data and the checks are unaffected.
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.