AWS braket documentation change
Summary
Clarified IonQ reservation benefits: specified increased gate limit (5000 vs 2000) and reduced error mitigation shots (500 vs 2500) compared to on-demand usage
Security assessment
Change describes resource allocation differences between service tiers. No security mechanisms, vulnerabilities, or security features are referenced. Purely operational documentation update.
Diff
diff --git a/braket/latest/developerguide/braket-reservations.md b/braket/latest/developerguide/braket-reservations.md index 2c880585a..673ec90ab 100644 --- a//braket/latest/developerguide/braket-reservations.md +++ b//braket/latest/developerguide/braket-reservations.md @@ -15 +15 @@ The cost of dedicated device access is based on the duration of your reservation -In a reservation, there are no [gateshot](./braket-terms.html#gateshot-limit-term) limits. Additionally, for IonQ devices, the minimum shot count for [Error mitigation](https://docs.aws.amazon.com/braket/latest/developerguide/braket-error-mitigation.html) tasks is reduced to 500 (vs. 2500 for on-demand). +For IonQ devices, reservations allow a higher per-circuit gate limit of 5,000 gates (vs. 2,000 for on-demand). Additionally, for IonQ devices, the minimum shot count for [error mitigation](https://docs.aws.amazon.com/braket/latest/developerguide/braket-error-mitigation.html) tasks is reduced to 500 (vs. 2,500 for on-demand).