What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
You can build and run a first Amazon Braket quantum circuit without owning a quantum computer. Use the Braket SDK’s LocalSimulator to create a two-qubit Bell state, run 1,000 shots, and inspect the measurement counts. A local run needs no S3 output location; AWS-hosted simulators and QPUs do.
Choose where to run the circuit
The simplest starting point is the local simulator, which runs in the Python environment where you installed the Braket SDK. It does not submit an AWS-hosted quantum task. Amazon Braket notebooks come with the SDK and dependencies installed; for a local development environment, install the SDK and Boto3. You can prototype locally before configuring AWS access.
To submit a task to a hosted simulator or QPU, configure AWS credentials and permissions for the user or role initiating Braket actions. Third-party QPU access also requires accepting the relevant AWS account terms about data transfer. AWS says that agreement is not required for local or on-demand simulators.
Build a Bell-state circuit
A Bell-state circuit is a useful first example because its expected measurement pattern is easy to recognize. A Hadamard gate puts qubit 0 into superposition; a controlled-NOT (CNOT) from qubit 0 to qubit 1 entangles the pair.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →#1 Best Overall
from braket.circuits import Circuit
from braket.devices import LocalSimulator
bell = Circuit().h(0).cnot(0, 1)
print(bell)Ideally, measuring the two qubits produces 00 or 11, each with probability one-half. The circuit does not produce those two outcomes in a guaranteed fixed sequence: measurement samples the state.
Run it locally and read the counts
Pass a shot count to LocalSimulator.run(), then obtain the result and its measurement counts:
local_sim = LocalSimulator()
result = local_sim.run(bell, shots=1000).result()
counts = result.measurement_counts
print(counts)Amazon Web Services’ undated current Developer Guide illustrates output like Counter({'11': 503, '00': 497}). That is an example, not a promised result. With 1,000 shots, expect counts concentrated on 00 and 11, with ordinary finite-shot variation around an even split. The same guide says its local state-vector simulator can handle up to 25 qubits depending on the computer’s available hardware; this is a hardware-dependent estimate, not a guarantee for every machine. AWS first-circuit and getting-started guidance.
This local run does not need an S3 bucket or an S3 output-location argument. It is the low-friction path for learning the SDK and prototyping small circuits.
How local, hosted simulator, and QPU runs differ
| Option | Where it runs | Setup and results | What to check |
|---|---|---|---|
| LocalSimulator | Your Python or Braket notebook environment | Pass a shot count; no S3 output location is needed. | Available local memory and processing capacity constrain circuit size. |
| SV1 | AWS-hosted on-demand simulator | Use an AwsDevice and pass an S3 bucket and prefix to .run(); results are stored in S3. |
AWS’s current Developer Guide lists a limit of up to 34 qubits. Check current capabilities and costs. |
| QPU | AWS-hosted task on selected quantum hardware | Use an AwsDevice, an S3 output location, and AWS permissions. Third-party hardware requires accepting the applicable data-transfer terms. |
Check the device’s current status, availability, region, and supported operations before submitting. |
Submit the circuit to the hosted SV1 simulator
To move from a local run to a hosted task, select SV1 by its device ARN and supply an S3 bucket and prefix. AWS’s example uses 100 shots; choose a shot count appropriate to your experiment and review current service pricing first.
from braket.aws import AwsDevice
# Replace with your bucket name and an output prefix in a region
# supported by the selected device.
s3_location = ("amazon-braket-your-bucket", "braket-results")
sv1 = AwsDevice("arn:aws:braket:::device/quantum-simulator/amazon/sv1")
result = sv1.run(bell, s3_location, shots=100).result()
print(result.measurement_counts)The ARN and bucket details can vary with AWS configuration and device availability; use the current device listing and documentation rather than assuming an example ARN or region will always be suitable. If you omit a bucket, AWS documents a default bucket naming pattern, but a valid hosted task still needs S3 result handling. S3 storage is a separate AWS service and may incur charges. AWS Braket getting-started guide · AWS device documentation.
Rank #4
Run on a QPU only after checking the device
A QPU task follows the hosted workflow: select a QPU with its current device ARN, provide an S3 output location, and submit the circuit through the SDK. The Bell circuit itself is unchanged, but device capabilities and access conditions are not uniform. A particular QPU may be unavailable, in a different region, or unable to run an operation your circuit uses.
- Check the selected device’s status, availability window, region, and supported operations in the current AWS device listing.
- Confirm that your AWS identity has permission to submit Braket tasks and use the required S3 location.
- For third-party hardware, accept the applicable AWS terms concerning data transfer.
- Review the current task and shot pricing before launching; a QPU run is not the same as a free local simulation.
AWS’s guidance covers the hosted simulator and QPU workflow, while its device pages are the place to verify current device properties. AWS Braket getting-started guide · AWS device documentation.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsCosts, Free Tier, and saving results
A local simulator run does not submit a paid hosted Braket task, though your own computer or notebook environment may have its own costs. Hosted simulators, QPUs, and S3 storage can incur AWS charges. The current AWS pricing page describes one hour per month of on-demand simulator time for the first 12 months under the Free Tier; eligibility and offer terms can change, so confirm them before relying on the offer. Pricing and device access can also change over time. Amazon Braket pricing.
Save any measurement counts, circuit code, and records you need outside the Braket task history. AWS states that task IDs and associated metadata are removed after 90 days. AWS Braket Developer Guide.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
