Service level agreements
Listed terms cover requests sent through this service adapter. They do not cover direct connections to the target service or replace the cloud provider’s own SLA. Each origin-to-target pair has its own terms or an explicit pending status. See the SLA tables, measurement rules, and scaling conditions.AWS Organizations to Organization account store
Deployment availability. These targets apply only to a deployed, authenticated Organizations account-plane endpoint with the account-lifecycle transaction available and the operations named in a signed agreement. A numerical target does not establish deployment availability.
What Tensor9 covers. These service levels cover the adapter between the origin API and target API. They do not replace the target provider’s SLA.
How latency is counted. Adapter work, including metadata and coordination, counts. Only separately measured permitted target waits are excluded.
Which terms apply. Your signed agreement names the covered operations, workload limits, remedies, and final service levels for your deployment.
What this adapter does
The Organizations service authenticates the management account, checks organization authority and operates on the durable account view. CreateAccount delegates to the host-owned account-lifecycle transaction; it is not a standalone local insert. External account readiness after commitment is a separately observed phase.How the latency targets were chosen
Bounded account listing: 8 ms monthly p99.ListAccounts. Includes a full bounded read of the durable account view.
Organization creation: 15 ms monthly p99. CreateOrganization. Includes identity validation, uniqueness checks and one durable mutation.
Account lifecycle transaction: 40 ms monthly p99. CloseAccount, CreateAccount. Includes the multi-record account lifecycle transaction, not just one database write.
Your signed agreement sets the terms for your deployment. A target does not add an operation or option that the compatibility tables mark unavailable.
What counts toward latency
For a request-response row, measure from the agreed ingress boundary to dispatch of the complete response. A row that explicitly names a first response chunk ends at that chunk; its number does not cover the rest of the stream. A long-poll row names the intentional wait and when adapter delay starts. Include parsing, authorization, admission, translation, serialization, adapter-owned storage and coordination, retries and response handling. Subtract only separately measured target-workload waits and external network segments allowed by the measurement rules. The adapter’s own response handling and dispatch remain covered. A database used for adapter metadata is still adapter work, even if a cloud provider hosts it. For concurrent calls, exclude the union of permitted wait intervals, not the sum of overlapping spans. Calculate each request’s adapter duration first, then the monthly p99. Do not subtract one service’s p99 from another’s. Known adapter timeouts are over-budget samples; failed or incomplete requests cannot disappear to improve the percentile. Missing measurements do not become zero latency. An SDK call span alone does not prove how much of its duration can be excluded.Availability and failures
The 99.9% request target measures correct adapter handling, not the percentage of application calls that return success. Correctly forwarding a target quota or permission error is different from producing that error because the adapter sent the wrong request. Adapter-caused failures count even when the target is healthy. With 1,000,000 eligible calls in a month, a 99.9% target permits at most 1,000 adapter-attributable failures. Endpoint probes have their own denominator. Correctness defects remain actionable even when the monthly availability percentage is met.Scaling and target-service capacity
ListAccounts currently scans the account store rather than paging, so this target applies only while the entire store has at most 100 accounts. Independent organizations can be read concurrently. Mutations serialize by organization or account identity so a replay cannot mint a duplicate member; qualify claim count, request size and concurrent lifecycle calls. Tell Tensor9 the expected steady rate, bursts, concurrency, payload sizes and operation mix. Tensor9 sizes and scales the adapter for the agreed load; you choose and monitor the target service’s capacity with Tensor9’s help. A latency budget is not a requests-per-second rating. Larger requests and higher rates need explicit terms, not silent inheritance of a small-request SLA.Data and behavior guarantees
CreateOrganization must bind the verified caller. CreateAccount may succeed only when bootstrap authority and the host transaction are available; retries preserve account identity. CloseAccount must not retire a foreign member. DescribeOrganization is deliberately unserved, not a hidden implication of the shared model.Example and diagnosis
An authenticated management account issues CreateAccount with one unique email. The host transaction records the new member and linked authority before replying; a retried request returns the same committed identity instead of a second account. The 40 ms target covers adapter transaction work, not downstream account provisioning. Usetensor9 explain and the documented explain headers to understand the selected adapter and its behavior. Correlate available request diagnostics with the target provider’s latency, throttling and capacity metrics. An explain report helps diagnose a request; it is not by itself a qualified SLA timing measurement. Share the operation, request shape, timestamps and request identifiers with support, with credentials and customer payloads removed.