AWS braket documentation change
Summary
Removed TN1 from the list of on-demand simulators available for hybrid jobs
Security assessment
The change only modifies the list of available simulators by removing TN1. There is no mention of security vulnerabilities, patching, or mitigation of threats. This appears to be routine documentation maintenance reflecting service changes.
Diff
diff --git a/braket/latest/developerguide/braket-jobs.md b/braket/latest/developerguide/braket-jobs.md index 117324acd..02e4dd621 100644 --- a//braket/latest/developerguide/braket-jobs.md +++ b//braket/latest/developerguide/braket-jobs.md @@ -68 +68 @@ To run a hybrid job with Amazon Braket Hybrid Jobs, you first need to define you -In either case, next you create a hybrid job using the Amazon Braket API, where you provide your algorithm script or container, select the target quantum device the hybrid job is to use, and then choose from a variety of optional settings. The default values provided for these optional settings work for the majority of use cases. For the target device to run your Hybrid Job, you have a choice between a QPU, an on-demand simulator (such as SV1, DM1 or TN1), or the classical hybrid job instance itself. With an on-demand simulator or QPU, your hybrid jobs container makes API calls to a remote device. With the embedded simulators, the simulator is embedded in the same container as your algorithm script. The [lightning simulators](https://github.com/PennyLaneAI/pennylane-lightning) from PennyLane are embedded with the default pre-built hybrid jobs container for you to use. If you run your code using an embedded PennyLane simulator or a custom simulator, you can specify an instance type as well as how many instances you wish to use. Refer to the [Amazon Braket Pricing page](https://aws.amazon.com/braket/pricing/) for the costs associated with each choice. +In either case, next you create a hybrid job using the Amazon Braket API, where you provide your algorithm script or container, select the target quantum device the hybrid job is to use, and then choose from a variety of optional settings. The default values provided for these optional settings work for the majority of use cases. For the target device to run your Hybrid Job, you have a choice between a QPU, an on-demand simulator (such as SV1 or DM1), or the classical hybrid job instance itself. With an on-demand simulator or QPU, your hybrid jobs container makes API calls to a remote device. With the embedded simulators, the simulator is embedded in the same container as your algorithm script. The [lightning simulators](https://github.com/PennyLaneAI/pennylane-lightning) from PennyLane are embedded with the default pre-built hybrid jobs container for you to use. If you run your code using an embedded PennyLane simulator or a custom simulator, you can specify an instance type as well as how many instances you wish to use. Refer to the [Amazon Braket Pricing page](https://aws.amazon.com/braket/pricing/) for the costs associated with each choice.