AWS braket documentation change
Summary
Updated IonQ device quotas to clarify gateshot limits and error mitigation shot requirements for on-demand vs direct reservations
Security assessment
Change specifies service usage limits and operational requirements rather than addressing security vulnerabilities or introducing security features
Diff
diff --git a/braket/latest/developerguide/braket-quotas.md b/braket/latest/developerguide/braket-quotas.md index 959a94bc2..a5c262479 100644 --- a//braket/latest/developerguide/braket-quotas.md +++ b//braket/latest/developerguide/braket-quotas.md @@ -116 +116 @@ If your hybrid job is unable to provision requested ML compute capacity, use ano - * For all IonQ's devices, you can submit any combination of total gate count per shot (the sum of all gate types) and shot count per task, providing that `(total gate count per shot)*(shot count per task) <= 1 Million`. These limits do not apply for hourly reservations through [Braket Direct](https://docs.aws.amazon.com/braket/latest/developerguide/braket-create-a-reservation.html). + * For all IonQ's devices: When using an on-demand model, there is a 1 Million [gateshot](https://docs.aws.amazon.com/braket/latest/developerguide/braket-terms.html) limit, and a minimum of 2500 shots for [Error mitigation](https://docs.aws.amazon.com/braket/latest/developerguide/braket-error-mitigation.html) tasks. For a direct reservation, there is no gateshot limit, and a minimum of 500 shots for Error mitigation tasks.