AWS braket documentation change
Summary
Restructured device documentation to include detailed provider table, removed redundant sections, updated regions/endpoints information, and improved content organization
Security assessment
The changes focus on reorganizing device listings into tables, updating regional availability details, and removing redundant content. No security vulnerabilities, mitigations, or security features are mentioned. The modifications are purely informational improvements without security implications.
Diff
diff --git a/braket/latest/developerguide/braket-devices.md b/braket/latest/developerguide/braket-devices.md index ac68709dd..26e21fe1e 100644 --- a//braket/latest/developerguide/braket-devices.md +++ b//braket/latest/developerguide/braket-devices.md @@ -13 +13,26 @@ Regions and endpoints -In Amazon Braket, a device represents a QPU or simulator that you can call to run quantum tasks. Amazon Braket provides access to QPU devices from IonQ, IQM, QuEra, and Rigetti, three on-demand simulators, three local simulators, and one embedded simulator. For all devices, you can find further device properties, such as device topology, calibration data, and native gate sets, on the **Devices** tab of the Amazon Braket console or by means of the `GetDevice` API. When constructing a circuit with the simulators, Amazon Braket currently requires that you use contiguous qubits or indices. If you are working with the Amazon Braket SDK, you have access to device properties as shown in the following code example. +In Amazon Braket, a device represents a QPU or simulator that you can call to run quantum tasks. Amazon Braket provides access to QPU devices from IonQ, IQM, QuEra, and Rigetti, three on-demand simulators, three local simulators, and one embedded simulator. + +For information on supported quantum hardware providers, see [Submitting quantum tasks to QPUs](./braket-submit-tasks.html). For information on available simulators, see [Submitting quantum tasks to simulators](./braket-submit-tasks-simulators.html). The following table displays the list of available devices and simulators. + +Provider | Device Name | Paradigm | Type | Device ARN | Region +---|---|---|---|---|--- +[IonQ](./braket-submit-tasks.html#braket-qpu-partner-ionq) | Aria-1 | gate-based | QPU | arn:aws:braket:us-east-1::device/qpu/ionq/Aria-1 | us-east-1 +[IonQ](./braket-submit-tasks.html#braket-qpu-partner-ionq) | Aria-2 | gate-based | QPU | arn:aws:braket:us-east-1::device/qpu/ionq/Aria-2 | us-east-1 +[IonQ](./braket-submit-tasks.html#braket-qpu-partner-ionq) | Forte-1 | gate-based | QPU | arn:aws:braket:us-east-1::device/qpu/ionq/Forte-1 | us-east-1 +[IonQ](./braket-submit-tasks.html#braket-qpu-partner-ionq) | Forte-Enterprise-1 | gate-based | QPU | arn:aws:braket:us-east-1::device/qpu/ionq/Forte-Enterprise-1 | us-east-1 +[IQM](./braket-submit-tasks.html#braket-qpu-partner-iqm) | Garnet | gate-based | QPU | arn:aws:braket:eu-north-1::device/qpu/iqm/Garnet | eu-north-1 +[IQM](./braket-submit-tasks.html#braket-qpu-partner-iqm) | Emerald | gate-based | QPU | arn:aws:braket:eu-north-1::device/qpu/iqm/Emerald | eu-north-1 +[QuEra](./braket-submit-tasks.html#braket-qpu-partner-quera) | Aquila | Analog Hamiltonian Simulation | QPU | arn:aws:braket:us-east-1::device/qpu/quera/Aquila | us-east-1 +[Rigetti](./braket-submit-tasks.html#braket-qpu-partner-rigetti) | Ankaa-3 | gate-based | QPU | arn:aws:braket:us-west-1::device/qpu/rigetti/Ankaa-3 | us-west-1 +AWS | [braket_sv](./braket-submit-tasks-simulators.html#braket-simulator-sv) | gate-based | Local simulator | N/A (local simulator in Braket SDK) | N/A +AWS | [braket_dm](./braket-submit-tasks-simulators.html#braket-simulator-dm) | gate-based | Local simulator | N/A (local simulator in Braket SDK) | N/A +AWS | [braket_ahs](./braket-submit-tasks-simulators.html#braket-simulator-ahs-local) | Analog Hamiltonian Simulation | Local simulator | N/A (local simulator in Braket SDK) | N/A +AWS | [SV1](./braket-submit-tasks-simulators.html#braket-simulator-sv1) | gate-based | On-demand simulator | arn:aws:braket:::device/quantum-simulator/amazon/sv1 | us-east-1, us-west-1, us-west-2, eu-west-2 +AWS | [DM1](./braket-submit-tasks-simulators.html#braket-simulator-dm1) | gate-based | On-demand simulator | arn:aws:braket:::device/quantum-simulator/amazon/dm1 | us-east-1, us-west-1, us-west-2, eu-west-2 +AWS | [TN1](./braket-submit-tasks-simulators.html#braket-simulator-tn1) | gate-based | On-demand simulator | arn:aws:braket:::device/quantum-simulator/amazon/tn1 | us-east-1, us-west-2, and eu-west-2 + +To view additional details about the QPUs you can use with Amazon Braket, see [Amazon Braket Quantum Computers](https://aws.amazon.com/braket/quantum-computers/). + +**Device properties** + +For all devices, you can find further device properties, such as device topology, calibration data, and native gate sets, on the **Devices** tab of the Amazon Braket console or by the `GetDevice` API. When constructing a circuit with the simulators, Amazon Braket requires that you use contiguous qubits or indices. When working with the SDK, the following code example shows how to get access to the device properties for each available device and simulator. @@ -40,18 +65 @@ In Amazon Braket, a device represents a QPU or simulator that you can call to ru -**Supported quantum hardware providers** - - * [IonQ](./braket-submit-tasks.html#braket-qpu-partner-ionq) - - * [IQM](./braket-submit-tasks.html#braket-qpu-partner-iqm) - - * [QuEra Computing](./braket-submit-tasks.html#braket-qpu-partner-quera) - - * [Rigetti](./braket-submit-tasks.html#braket-qpu-partner-rigetti) - - - - -**Supported simulators** - - * [Local state vector simulator (braket_sv) ('Default Simulator')](./braket-submit-tasks-simulators.html#braket-simulator-sv) - - * [Local density matrix simulator (braket_dm)](./braket-submit-tasks-simulators.html#braket-simulator-dm) +## Regions and endpoints for Amazon Braket @@ -59 +67 @@ In Amazon Braket, a device represents a QPU or simulator that you can call to ru - * [Local AHS simulator](./braket-submit-tasks-simulators.html#braket-simulator-ahs-local) +For a full list of regions and endpoints, see the [AWS General Reference.](https://docs.aws.amazon.com/general/latest/gr/braket.html) @@ -61,37 +69 @@ In Amazon Braket, a device represents a QPU or simulator that you can call to ru - * [State vector simulator (SV1)](./braket-submit-tasks-simulators.html#braket-simulator-sv1) - - * [Density matrix simulator (DM1)](./braket-submit-tasks-simulators.html#braket-simulator-dm1) - - * [Tensor network simulator (TN1)](./braket-submit-tasks-simulators.html#braket-simulator-tn1) - - * [PennyLane's Lightning Simulators](./embedded-simulator.html#lightning-simulator) - - - - -**Choose the best simulator for your quantum task** - - * [Compare simulators](./choose-a-simulator.html) - - - - -Amazon Braket devices Provider | Device Name | Paradigm | Type | Device ARN | Region ----|---|---|---|---|--- -IonQ | Aria-1 | gate-based | QPU | arn:aws:braket:us-east-1::device/qpu/ionq/Aria-1 | us-east-1 -IonQ | Aria-2 | gate-based | QPU | arn:aws:braket:us-east-1::device/qpu/ionq/Aria-2 | us-east-1 -IonQ | Forte-1 | gate-based | QPU | arn:aws:braket:us-east-1::device/qpu/ionq/Forte-1 | us-east-1 -IonQ | Forte-Enterprise-1 | gate-based | QPU | arn:aws:braket:us-east-1::device/qpu/ionq/Forte-Enterprise-1 | us-east-1 -IQM | Garnet | gate-based | QPU | arn:aws:braket:eu-north-1::device/qpu/iqm/Garnet | eu-north-1 -IQM | Emerald | gate-based | QPU | arn:aws:braket:eu-north-1::device/qpu/iqm/Emerald | eu-north-1 -QuEra | Aquila | Analog Hamiltonian Simulation | QPU | arn:aws:braket:us-east-1::device/qpu/quera/Aquila | us-east-1 -Rigetti | Ankaa-3 | gate-based | QPU | arn:aws:braket:us-west-1::device/qpu/rigetti/Ankaa-3 | us-west-1 -AWS | braket_sv | gate-based | Local simulator | N/A (local simulator in Braket SDK) | N/A -AWS | braket_dm | gate-based | Local simulator | N/A (local simulator in Braket SDK) | N/A -AWS | SV1 | gate-based | On-demand simulator | arn:aws:braket:::device/quantum-simulator/amazon/sv1 | us-east-1, us-west-1, us-west-2, eu-west-2 -AWS | DM1 | gate-based | On-demand simulator | arn:aws:braket:::device/quantum-simulator/amazon/dm1 | us-east-1, us-west-1, us-west-2, eu-west-2 -AWS | TN1 | gate-based | On-demand simulator | arn:aws:braket:::device/quantum-simulator/amazon/tn1 | us-east-1, us-west-2, and eu-west-2 - -To view additional details about the QPUs you can use with Amazon Braket, see [Amazon Braket Hardware Providers](https://aws.amazon.com/braket/quantum-computers/). - -## Amazon Braket regions and endpoints +Quantum tasks that run on a QPU device can be viewed in the Amazon Braket console in the Region of that device. When using the Amazon Braket SDK, you can submit quantum tasks to any QPU device, regardless of the Region in which you are working. The SDK automatically creates a session to the Region for the QPU specified. @@ -101,9 +73,7 @@ Amazon Braket is available in the following AWS Regions: -Region availability of Amazon Braket Region name | Region | Braket endpoints | QPUs & Simulators ----|---|---|--- -US East (N. Virginia) | us-east-1 | braket.us-east-1.amazonaws.com (IPv4 only) braket.us-east-1.api.aws (Dual stack) | IonQ, QuEra, SV1, DM1, TN1 -US West (N. California) | us-west-1 | braket.us-west-1.amazonaws.com (IPv4 only) braket.us-west-1.api.aws (Dual stack) | Rigetti, SV1, DM1 -US West 2 (Oregon) | us-west-2 | braket.us-west-2.amazonaws.com (IPv4 only) braket.us-west-2.api.aws (Dual stack) | SV1, DM1, TN1 -EU North 1 (Stockholm) | eu-north-1 | braket.eu-north-1.amazonaws.com (IPv4 only) braket.eu-north-1.api.aws (Dual stack) | IQM -EU West 2 (London) | eu-west-2 | braket.eu-west-2.amazonaws.com (IPv4 only) braket.eu-west-2.api.aws (Dual stack) | SV1, DM1, TN1 - -Quantum tasks that run on a QPU device can be viewed in the Amazon Braket console in the Region of that device. If you are using the Amazon Braket SDK, you can submit quantum tasks to any QPU device, regardless of the Region in which you are working. The SDK automatically creates a session to the Region for the QPU specified. +Region name | Region | Braket endpoints +---|---|--- +US East (N. Virginia) | us-east-1 | braket.us-east-1.amazonaws.com (IPv4 only) braket.us-east-1.api.aws (Dual stack) +US West (N. California) | us-west-1 | braket.us-west-1.amazonaws.com (IPv4 only) braket.us-west-1.api.aws (Dual stack) +US West 2 (Oregon) | us-west-2 | braket.us-west-2.amazonaws.com (IPv4 only) braket.us-west-2.api.aws (Dual stack) +EU North 1 (Stockholm) | eu-north-1 | braket.eu-north-1.amazonaws.com (IPv4 only) braket.eu-north-1.api.aws (Dual stack) +EU West 2 (London) | eu-west-2 | braket.eu-west-2.amazonaws.com (IPv4 only) braket.eu-west-2.api.aws (Dual stack) @@ -115,2 +84,0 @@ The Amazon Braket SDK does not support IPv6-only networks. -For general information about how AWS works with Regions and endpoints, see [AWS service endpoints](https://docs.aws.amazon.com/general/latest/gr/rande.html) in the _AWS General Reference_. -