Skip to content

Commit 427cdfd

Browse files
authored
feat(ec2): add c6a instances (#19113)
<img width="1239" alt="image" src="https://user-images.githubusercontent.com/31543/155358925-63394802-28db-4d49-bcd6-ad5182ad49c7.png"> https://aws.amazon.com/about-aws/whats-new/2022/02/amazon-ec2-c6a-instances/ > Amazon EC2 C6a instances are powered by 3rd generation AMD EPYC processors, deliver up to 15% better price performance compared to C5a instances, and offer 10% lower cost than comparable x86-based EC2 instances. C6a instances feature a 2:1 ratio of memory to vCPU, just like C5a instances and support increased sizes up to 192 vCPUs per instance, which is double that of C5a instances. These instances feature more than twice the network bandwidth of C5a instances, and are designed for compute-intensive workloads such as batch processing, distributed analytics, high performance computing (HPC), ad serving, highly-scalable multiplayer gaming, and video encoding. Submitted CFN user guide PR: awsdocs/aws-cloudformation-user-guide#1169 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
1 parent 464e561 commit 427cdfd

File tree

2 files changed

+30
-20
lines changed

2 files changed

+30
-20
lines changed

packages/@aws-cdk/aws-ec2/README.md

+7-7
Original file line numberDiff line numberDiff line change
@@ -663,7 +663,7 @@ vpc.addVpnConnection('Dynamic', {
663663
```
664664

665665
By default, routes will be propagated on the route tables associated with the private subnets. If no
666-
private subnets exists, isolated subnets are used. If no isolated subnets exists, public subnets are
666+
private subnets exist, isolated subnets are used. If no isolated subnets exist, public subnets are
667667
used. Use the `Vpc` property `vpnRoutePropagation` to customize this behavior.
668668

669669
VPN connections expose [metrics (cloudwatch.Metric)](https://github.com/aws/aws-cdk/blob/master/packages/%40aws-cdk/aws-cloudwatch/README.md) across all tunnels in the account/region and per connection:
@@ -810,7 +810,7 @@ The endpoint must use at least one [authentication method](https://docs.aws.amaz
810810
If user-based authentication is used, the [self-service portal URL](https://docs.aws.amazon.com/vpn/latest/clientvpn-user/self-service-portal.html)
811811
is made available via a CloudFormation output.
812812

813-
By default, a new security group is created and logging is enabled. Moreover, a rule to
813+
By default, a new security group is created, and logging is enabled. Moreover, a rule to
814814
authorize all users to the VPC CIDR is created.
815815

816816
To customize authorization rules, set the `authorizeAllUsersToVpcCidr` prop to `false`
@@ -898,7 +898,7 @@ new ec2.Instance(this, 'Instance4', {
898898

899899
CloudFormation Init allows you to configure your instances by writing files to them, installing software
900900
packages, starting services and running arbitrary commands. By default, if any of the instance setup
901-
commands throw an error, the deployment will fail and roll back to the previously known good state.
901+
commands throw an error; the deployment will fail and roll back to the previously known good state.
902902
The following documentation also applies to `AutoScalingGroup`s.
903903

904904
For the full set of capabilities of this system, see the documentation for
@@ -1201,7 +1201,7 @@ Aspects.of(this).add(aspect);
12011201

12021202
VPC Flow Logs is a feature that enables you to capture information about the IP traffic going to and from network interfaces in your VPC. Flow log data can be published to Amazon CloudWatch Logs and Amazon S3. After you've created a flow log, you can retrieve and view its data in the chosen destination. (<https://docs.aws.amazon.com/vpc/latest/userguide/flow-logs.html>).
12031203

1204-
By default a flow log will be created with CloudWatch Logs as the destination.
1204+
By default, a flow log will be created with CloudWatch Logs as the destination.
12051205

12061206
You can create a flow log like this:
12071207

@@ -1235,7 +1235,7 @@ vpc.addFlowLog('FlowLogCloudWatch', {
12351235
});
12361236
```
12371237

1238-
By default the CDK will create the necessary resources for the destination. For the CloudWatch Logs destination
1238+
By default, the CDK will create the necessary resources for the destination. For the CloudWatch Logs destination
12391239
it will create a CloudWatch Logs Log Group as well as the IAM role with the necessary permissions to publish to
12401240
the log group. In the case of an S3 destination, it will create the S3 bucket.
12411241

@@ -1311,9 +1311,9 @@ from separate parts forming archive. The most common parts are scripts executed
13111311
kinds, too.
13121312

13131313
The advantage of multipart archive is in flexibility when it's needed to add additional parts or to use specialized parts to
1314-
fine tune instance startup. Some services (like AWS Batch) supports only `MultipartUserData`.
1314+
fine tune instance startup. Some services (like AWS Batch) support only `MultipartUserData`.
13151315

1316-
The parts can be executed at different moment of instance start-up and can serve a different purposes. This is controlled by `contentType` property.
1316+
The parts can be executed at different moment of instance start-up and can serve a different purpose. This is controlled by `contentType` property.
13171317
For common scripts, `text/x-shellscript; charset="utf-8"` can be used as content type.
13181318

13191319
In order to create archive the `MultipartUserData` has to be instantiated. Than, user can add parts to multipart archive using `addPart`. The `MultipartBody` contains methods supporting creation of body parts.

packages/@aws-cdk/aws-ec2/lib/instance-types.ts

+23-13
Original file line numberDiff line numberDiff line change
@@ -298,16 +298,6 @@ export enum InstanceClass {
298298
*/
299299
C5 = 'c5',
300300

301-
/**
302-
* Compute optimized instances, 6th generation
303-
*/
304-
COMPUTE6_INTEL = 'c6i',
305-
306-
/**
307-
* Compute optimized instances, 6th generation
308-
*/
309-
C6I = 'c6i',
310-
311301
/**
312302
* Compute optimized instances with local NVME drive, 5th generation
313303
*/
@@ -319,7 +309,7 @@ export enum InstanceClass {
319309
C5D = 'c5d',
320310

321311
/**
322-
* Compute optimized instances based on AMD EPYC, 5th generation.
312+
* Compute optimized instances based on AMD EPYC, 5th generation
323313
*/
324314
COMPUTE5_AMD = 'c5a',
325315

@@ -329,12 +319,12 @@ export enum InstanceClass {
329319
C5A = 'c5a',
330320

331321
/**
332-
* Compute optimized instances with local NVME drive based on AMD EPYC, 5th generation.
322+
* Compute optimized instances with local NVME drive based on AMD EPYC, 5th generation
333323
*/
334324
COMPUTE5_AMD_NVME_DRIVE = 'c5ad',
335325

336326
/**
337-
* Compute optimized instances with local NVME drive based on AMD EPYC, 5th generation.
327+
* Compute optimized instances with local NVME drive based on AMD EPYC, 5th generation
338328
*/
339329
C5AD = 'c5ad',
340330

@@ -348,6 +338,26 @@ export enum InstanceClass {
348338
*/
349339
C5N = 'c5n',
350340

341+
/**
342+
* Compute optimized instances, 6th generation
343+
*/
344+
COMPUTE6_INTEL = 'c6i',
345+
346+
/**
347+
* Compute optimized instances, 6th generation
348+
*/
349+
C6I = 'c6i',
350+
351+
/**
352+
* Compute optimized instances based on AMD EPYC (codename Milan), 6th generation
353+
*/
354+
COMPUTE6_AMD = 'c6a',
355+
356+
/**
357+
* Compute optimized instances based on AMD EPYC (codename Milan), 6th generation
358+
*/
359+
C6A = 'c6a',
360+
351361
/**
352362
* Compute optimized instances for high performance computing, 6th generation with Graviton2 processors
353363
*/

0 commit comments

Comments
 (0)