AWS braket documentation change
Summary
Updated default instance type from ml.m5.large to ml.t3.medium, restructured instance type tables, and modified instance specifications. Changed terminology from 'Compute Optimized' to 'High performance' and 'Accelerated Computing' to 'GPU accelerated'.
Security assessment
Changes involve instance type updates and documentation restructuring without any mention of security vulnerabilities, access controls, or security best practices. The modifications appear focused on accuracy of technical specifications and terminology.
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 d077c9d1d..38a41d47e 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.m5.large` 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.t3.medium` instance. However, you can customize this instance type when you create a hybrid job using the following import and configuration argument. @@ -20 +20 @@ Depending on your algorithm, you may have different requirements. By default, Am -If you are running an embedded simulation and have specified a local device in the device configuration, you will be able to additionally request more than one instance in the InstanceConfig by specifying the instanceCount and setting it to be greater than one. The upper limit is 5. For instance, you can choose 3 instances as follows. +If you are running an embedded simulation and have specified a local device in the device configuration, you will be able to additionally request more than one instance in the `InstanceConfig` by specifying the `instanceCount` and setting it to be greater than one. The upper limit is 5. For instance, you can choose 3 instances as follows. @@ -32 +32 @@ When you use multiple instances, consider distributing your hybrid job using the -The following three tables list the available instance types and specs for standard, compute optimized, and accelerated computing instances. +The following three tables list the available instance types and specs for standard, high performance, and GPU accelerated instances. @@ -38 +38 @@ To view the default classical compute instance quotas for Hybrid Jobs, see the [ -Standard Instances | vCPU | Memory +Standard Instances | vCPU | Memory (GiB) @@ -40,12 +40,11 @@ Standard Instances | vCPU | Memory -ml.m5.large (default) | 2 | 8 GiB -ml.m5.xlarge | 4 | 16 GiB -ml.m5.2xlarge | 8 | 32 GiB -ml.m5.4xlarge | 16 | 64 GiB -ml.m5.12xlarge | 48 | 192 GiB -ml.m5.24xlarge | 96 | 384 GiB -ml.m4.xlarge | 4 | 16 GiB -ml.m4.2xlarge | 8 | 32 GiB -ml.m4.4xlarge | 16 | 64 GiB -ml.m4.10xlarge | 40 | 256 GiB - -Compute Optimized Instances | vCPU | Memory +ml.t3.medium (default) | 2 | 4 +ml.t3.large | 2 | 8 +ml.t3.xlarge | 4 | 16 +ml.t3.2xlarge | 8 | 32 +ml.m5.xlarge | 4 | 16 +ml.m5.2xlarge | 8 | 32 +ml.m5.4xlarge | 16 | 64 +ml.m5.12xlarge | 48 | 192 +ml.m5.24xlarge | 96 | 384 + +High performance Instances | vCPU | Memory (GiB) @@ -53,29 +52,11 @@ Compute Optimized Instances | vCPU | Memory -ml.c4.xlarge | 4 | 7.5 GiB -ml.c4.2xlarge | 8 | 15 GiB -ml.c4.4xlarge | 16 | 30 GiB -ml.c4.8xlarge | 36 | 192 GiB -ml.c5.xlarge | 4 | 8 GiB -ml.c5.2xlarge | 8 | 16 GiB -ml.c5.4xlarge | 16 | 32 GiB -ml.c5.9xlarge | 36 | 72 GiB -ml.c5.18xlarge | 72 | 144 GiB -ml.c5n.xlarge | 4 | 10.5 GiB -ml.c5n.2xlarge | 8 | 21 GiB -ml.c5n.4xlarge | 16 | 42 GiB -ml.c5n.9xlarge | 36 | 96 GiB -ml.c5n.18xlarge | 72 | 192 GiB - -Accelerated Compting Instances | vCPU | Memory ----|---|--- -ml.p2.xlarge | 4 | 61 GiB -ml.p2.8xlarge | 32 | 488 GiB -ml.p2.16xlarge | 64 | 732 GiB -ml.p3.2xlarge | 8 | 61 GiB -ml.p3.8xlarge | 32 | 244 GiB -ml.p3.16xlarge | 64 | 488 GiB -ml.g4dn.xlarge | 4 | 16 GiB -ml.g4dn.2xlarge | 8 | 32 GiB -ml.g4dn.4xlarge | 16 | 64 GiB -ml.g4dn.8xlarge | 32 | 128 GiB -ml.g4dn.12xlarge | 48 | 192 GiB -ml.g4dn.16xlarge | 64 | 256 GiB +ml.c5.xlarge | 4 | 8 +ml.c5.2xlarge | 8 | 16 +ml.c5.4xlarge | 16 | 32 +ml.c5.9xlarge | 36 | 72 +ml.c5.18xlarge | 72 | 144 + +GPU accelerated Instances | GPUs | vCPU | Memory (GiB) | GPU Memory (GiB) +---|---|---|---|--- +ml.p3.2xlarge | 1 | 8 | 61 | 16 +ml.p3.8xlarge | 4 | 32 | 244 | 64 +ml.p3.16xlarge | 8 | 64 | 488 | 128