AWS Security ChangesHomeSearch

AWS braket documentation change

Service: braket · 2025-06-22 · Documentation low

File: braket/latest/developerguide/braket-jobs-configure-job-instance-for-script.md

Summary

Updated default instance type from ml.t3.medium to ml.m5.large, modified instance type table entries, added new instance types (c5n/g4dn series), and adjusted S3 bucket naming example

Security assessment

Changes focus on instance type specifications and naming conventions without mentioning security vulnerabilities, access controls, or encryption. The S3 bucket name change appears to be a branding adjustment rather than a security measure.

Diff

diff --git a/braket/latest/developerguide/braket-jobs-configure-job-instance-for-script.md b/braket/latest/developerguide/braket-jobs-configure-job-instance-for-script.md
index 38a41d47e..577949b56 100644
--- a//braket/latest/developerguide/braket-jobs-configure-job-instance-for-script.md
+++ b//braket/latest/developerguide/braket-jobs-configure-job-instance-for-script.md
@@ -9 +9 @@ Configure the default bucket in AwsSession
-Depending on your algorithm, you may have different requirements. By default, Amazon Braket runs your algorithm script on an `ml.t3.medium` instance. However, you can customize this instance type when you create a hybrid job using the following import and configuration argument.
+Depending on your algorithm, you may have different requirements. By default, Amazon Braket runs your algorithm script on an `ml.m5.large` instance. However, you can customize this instance type when you create a hybrid job using the following import and configuration argument.
@@ -40,4 +40 @@ Standard Instances | vCPU | Memory (GiB)
-ml.t3.medium (default) |  2 |  4  
-ml.t3.large |  2 |  8  
-ml.t3.xlarge |  4 |  16  
-ml.t3.2xlarge |  8 |  32  
+ml.m5.large (default) |  4 |  16  
@@ -56,0 +54,5 @@ ml.c5.18xlarge |  72 |  144
+ml.c5n.xlarge |  4 |  10.5  
+ml.c5n.2xlarge |  8 |  21  
+ml.c5n.4xlarge |  16 |  32  
+ml.c5n.9xlarge |  36 |  72  
+ml.c5n.18xlarge |  72 |  192  
@@ -62,0 +65,7 @@ ml.p3.16xlarge |  8 |  64 |  488 |  128
+ml.p4d.24xlarge |  8 |  96 |  1152 |  320  
+ml.g4dn.xlarge |  1 |  4 |  16 |  16  
+ml.g4dn.2xlarge |  1 |  8 |  32 |  16  
+ml.g4dn.4xlarge |  1 |  16 |  64 |  16  
+ml.g4dn.8xlarge |  1 |  32 |  128 |  16  
+ml.g4dn.12xlarge |  4 |  48 |  192 |  64  
+ml.g4dn.16xlarge |  1 |  64 |  256 |  16  
@@ -84 +93 @@ Each instance uses a default configuration of data storage (SSD) of 30 GB. But y
-Utilizing your own `AwsSession` instance provides you with enhanced flexibility, such as the ability to specify a custom location for your default Amazon S3 bucket. By default, an `AwsSession` has a pre-configured Amazon S3 bucket location of `f"amazon-braket-{id}-{region}"`. However, you have the option to override the default Amazon S3 bucket location when creating an `AwsSession`. Users can optionally pass in an `AwsSession` object into the `AwsQuantumJob.create()` method, by providing the `aws_session` parameter as demonstrated in the following code example.
+Utilizing your own `AwsSession` instance provides you with enhanced flexibility, such as the ability to specify a custom location for your default Amazon S3 bucket. By default, an `AwsSession` has a pre-configured Amazon S3 bucket location of `"amazon-braket-{id}-{region}"`. However, you have the option to override the default Amazon S3 bucket location when creating an `AwsSession`. Users can optionally pass in an `AwsSession` object into the `AwsQuantumJob.create()` method, by providing the `aws_session` parameter as demonstrated in the following code example.
@@ -87 +96 @@ Utilizing your own `AwsSession` instance provides you with enhanced flexibility,
-    aws_session = AwsSession(default_bucket="amzn-s3-demo-bucket")
+    aws_session = AwsSession(default_bucket="amazon-braket-s3-demo-bucket")
@@ -89 +98 @@ Utilizing your own `AwsSession` instance provides you with enhanced flexibility,
-    # then you can use that AwsSession when creating a hybrid job
+    # Then you can use that AwsSession when creating a hybrid job