IPlacementGroup

class aws_cdk.aws_ec2.IPlacementGroup(*args, **kwds)

Bases: IResource, Protocol

Determines where your instances are placed on the underlying hardware according to the specified PlacementGroupStrategy.

See:

https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/placement-groups.html

Methods

apply_removal_policy(policy)

Apply the given removal policy to this resource.

The Removal Policy controls what happens to this resource when it stops being managed by CloudFormation, either because you’ve removed it from the CDK application or because you’ve made a change that requires the resource to be replaced.

The resource can be deleted (RemovalPolicy.DESTROY), or left in your AWS account for data recovery and cleanup later (RemovalPolicy.RETAIN).

Parameters:

policy (RemovalPolicy) –

Return type:

None

Attributes

env

The environment this resource belongs to.

For resources that are created and managed by the CDK (generally, those created by creating new class instances like Role, Bucket, etc.), this is always the same as the environment of the stack they belong to; however, for imported resources (those obtained from static methods like fromRoleArn, fromBucketName, etc.), that might be different than the stack they were imported into.

node

The tree node.

partitions

The number of partitions.

Valid only when Strategy is set to PARTITION.

Default:

0

placement_group_name

The name of this placement group.

Attribute:

true

spread_level

Places instances on distinct hardware.

Spread placement groups are recommended for applications that have a small number of critical instances that should be kept separate from each other. Launching instances in a spread level placement group reduces the risk of simultaneous failures that might occur when instances share the same equipment. Spread level placement groups provide access to distinct hardware, and are therefore suitable for mixing instance types or launching instances over time. If you start or launch an instance in a spread placement group and there is insufficient unique hardware to fulfill the request, the request fails. Amazon EC2 makes more distinct hardware available over time, so you can try your request again later. Placement groups can spread instances across racks or hosts. You can use host level spread placement groups only with AWS Outposts.

Default:
  • no spread level

stack

The stack in which this resource is defined.

strategy

Which strategy to use when launching instances.

Default:
  • PlacementGroupStrategy.PARTITION if partitions is defined, CLUSTER otherwise