PyPI - aws-cdk.aws-ec2-alpha - Versions diffs - 2.175.1a0__tar.gz → 2.176.0a0__tar.gz - Mend

aws-cdk.aws-ec2-alpha 2.175.1a0tar.gz → 2.176.0a0tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Potentially problematic release.

This version of aws-cdk.aws-ec2-alpha might be problematic. Click here for more details.

Files changed (18) hide show

{aws_cdk_aws_ec2_alpha-2.175.1a0/src/aws_cdk.aws_ec2_alpha.egg-info → aws_cdk_aws_ec2_alpha-2.176.0a0}/PKG-INFO RENAMED Viewed

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: aws-cdk.aws-ec2-alpha
-Version: 2.175.1a0
+Version: 2.176.0a0
 Summary: The CDK construct library for VPC V2
 Home-page: https://github.com/aws/aws-cdk
 Author: Amazon Web Services
@@ -23,7 +23,7 @@ Requires-Python: ~=3.8
 Description-Content-Type: text/markdown
 License-File: LICENSE
 License-File: NOTICE
-Requires-Dist: aws-cdk-lib<3.0.0,>=2.175.1
+Requires-Dist: aws-cdk-lib<3.0.0,>=2.176.0
 Requires-Dist: constructs<11.0.0,>=10.0.0
 Requires-Dist: jsii<2.0.0,>=1.104.0
 Requires-Dist: publication>=0.0.3
@@ -327,7 +327,7 @@ acceptor_vpc = VpcV2(self, "VpcA",
 acceptor_role_arn = acceptor_vpc.create_acceptor_vpc_role("000000000000")
 ```
-After creating an IAM role in the acceptor account, we can initiate the peering connection request from the requestor VPC. Import accpeptorVpc to the stack using `fromVpcV2Attributes` method, it is recommended to specify owner account id of the acceptor VPC in case of cross account peering connection, if acceptor VPC is hosted in different region provide region value for import as well.
+After creating an IAM role in the acceptor account, we can initiate the peering connection request from the requestor VPC. Import acceptorVpc to the stack using `fromVpcV2Attributes` method, it is recommended to specify owner account id of the acceptor VPC in case of cross account peering connection, if acceptor VPC is hosted in different region provide region value for import as well.
 The following code snippet demonstrates how to set up VPC peering between two VPCs in different AWS accounts using CDK:
 ```python
@@ -483,11 +483,11 @@ For more information, see [What is AWS Site-to-Site VPN?](https://docs.aws.amazo
 VPN route propagation is a feature in Amazon Web Services (AWS) that automatically updates route tables in your Virtual Private Cloud (VPC) with routes learned from a VPN connection.
-To enable VPN route propogation, use the `vpnRoutePropagation` property to specify the subnets as an input to the function. VPN route propagation will then be enabled for each subnet with the corresponding route table IDs.
+To enable VPN route propagation, use the `vpnRoutePropagation` property to specify the subnets as an input to the function. VPN route propagation will then be enabled for each subnet with the corresponding route table IDs.
 Additionally, you can set up a route in any route table with the target set to the VPN Gateway. The function `enableVpnGatewayV2` returns a `VPNGatewayV2` object that you can reference later.
-The code example below provides the definition for setting up a VPN gateway with `vpnRoutePropogation` enabled:
+The code example below provides the definition for setting up a VPN gateway with `vpnRoutePropagation` enabled:
 ```python
 stack = Stack()
@@ -515,7 +515,7 @@ An internet gateway is a horizontally scaled, redundant, and highly available VP
 For more information, see [Enable VPC internet access using internet gateways](https://docs.aws.amazon.com/vpc/latest/userguide/vpc-igw-internet-access.html).
 You can add an internet gateway to a VPC using `addInternetGateway` method. By default, this method creates a route in all Public Subnets with outbound destination set to `0.0.0.0` for IPv4 and `::0` for IPv6 enabled VPC.
-Instead of using the default settings, you can configure a custom destinatation range by providing an optional input `destination` to the method.
+Instead of using the default settings, you can configure a custom destination range by providing an optional input `destination` to the method.
 The code example below shows how to add an internet gateway with a custom outbound destination IP range:
@@ -558,12 +558,12 @@ imported_vpc = VpcV2.from_vpc_v2_attributes(stack, "ImportedVpc",
 In case of cross account or cross region VPC, its recommended to provide region and ownerAccountId so that these values for the VPC can be used to populate correct arn value for the VPC. If a VPC region and account ID is not provided, then region and account configured in the stack will be used. Furthermore, these fields will be referenced later while setting up VPC peering connection, so its necessary to set these fields to a correct value.
-Below is an example of importing a cross region and cross acount VPC, VPC arn for this case would be 'arn:aws:ec2:us-west-2:123456789012:vpc/mockVpcID'
+Below is an example of importing a cross region and cross account VPC, VPC arn for this case would be 'arn:aws:ec2:us-west-2:123456789012:vpc/mockVpcID'
 ```python
 stack = Stack()
-# Importing a cross acount or cross region VPC
+# Importing a cross account or cross region VPC
 imported_vpc = VpcV2.from_vpc_v2_attributes(stack, "ImportedVpc",
     vpc_id="mockVpcID",
     vpc_cidr_block="10.0.0.0/16",

{aws_cdk_aws_ec2_alpha-2.175.1a0 → aws_cdk_aws_ec2_alpha-2.176.0a0}/README.md RENAMED Viewed

@@ -296,7 +296,7 @@ acceptor_vpc = VpcV2(self, "VpcA",
 acceptor_role_arn = acceptor_vpc.create_acceptor_vpc_role("000000000000")
 ```
-After creating an IAM role in the acceptor account, we can initiate the peering connection request from the requestor VPC. Import accpeptorVpc to the stack using `fromVpcV2Attributes` method, it is recommended to specify owner account id of the acceptor VPC in case of cross account peering connection, if acceptor VPC is hosted in different region provide region value for import as well.
+After creating an IAM role in the acceptor account, we can initiate the peering connection request from the requestor VPC. Import acceptorVpc to the stack using `fromVpcV2Attributes` method, it is recommended to specify owner account id of the acceptor VPC in case of cross account peering connection, if acceptor VPC is hosted in different region provide region value for import as well.
 The following code snippet demonstrates how to set up VPC peering between two VPCs in different AWS accounts using CDK:
 ```python
@@ -452,11 +452,11 @@ For more information, see [What is AWS Site-to-Site VPN?](https://docs.aws.amazo
 VPN route propagation is a feature in Amazon Web Services (AWS) that automatically updates route tables in your Virtual Private Cloud (VPC) with routes learned from a VPN connection.
-To enable VPN route propogation, use the `vpnRoutePropagation` property to specify the subnets as an input to the function. VPN route propagation will then be enabled for each subnet with the corresponding route table IDs.
+To enable VPN route propagation, use the `vpnRoutePropagation` property to specify the subnets as an input to the function. VPN route propagation will then be enabled for each subnet with the corresponding route table IDs.
 Additionally, you can set up a route in any route table with the target set to the VPN Gateway. The function `enableVpnGatewayV2` returns a `VPNGatewayV2` object that you can reference later.
-The code example below provides the definition for setting up a VPN gateway with `vpnRoutePropogation` enabled:
+The code example below provides the definition for setting up a VPN gateway with `vpnRoutePropagation` enabled:
 ```python
 stack = Stack()
@@ -484,7 +484,7 @@ An internet gateway is a horizontally scaled, redundant, and highly available VP
 For more information, see [Enable VPC internet access using internet gateways](https://docs.aws.amazon.com/vpc/latest/userguide/vpc-igw-internet-access.html).
 You can add an internet gateway to a VPC using `addInternetGateway` method. By default, this method creates a route in all Public Subnets with outbound destination set to `0.0.0.0` for IPv4 and `::0` for IPv6 enabled VPC.
-Instead of using the default settings, you can configure a custom destinatation range by providing an optional input `destination` to the method.
+Instead of using the default settings, you can configure a custom destination range by providing an optional input `destination` to the method.
 The code example below shows how to add an internet gateway with a custom outbound destination IP range:
@@ -527,12 +527,12 @@ imported_vpc = VpcV2.from_vpc_v2_attributes(stack, "ImportedVpc",
 In case of cross account or cross region VPC, its recommended to provide region and ownerAccountId so that these values for the VPC can be used to populate correct arn value for the VPC. If a VPC region and account ID is not provided, then region and account configured in the stack will be used. Furthermore, these fields will be referenced later while setting up VPC peering connection, so its necessary to set these fields to a correct value.
-Below is an example of importing a cross region and cross acount VPC, VPC arn for this case would be 'arn:aws:ec2:us-west-2:123456789012:vpc/mockVpcID'
+Below is an example of importing a cross region and cross account VPC, VPC arn for this case would be 'arn:aws:ec2:us-west-2:123456789012:vpc/mockVpcID'
 ```python
 stack = Stack()
-# Importing a cross acount or cross region VPC
+# Importing a cross account or cross region VPC
 imported_vpc = VpcV2.from_vpc_v2_attributes(stack, "ImportedVpc",
     vpc_id="mockVpcID",
     vpc_cidr_block="10.0.0.0/16",

{aws_cdk_aws_ec2_alpha-2.175.1a0 → aws_cdk_aws_ec2_alpha-2.176.0a0}/setup.py RENAMED Viewed

@@ -5,7 +5,7 @@ kwargs = json.loads(
     """
 {
     "name": "aws-cdk.aws-ec2-alpha",
-    "version": "2.175.1.a0",
+    "version": "2.176.0.a0",
     "description": "The CDK construct library for VPC V2",
     "license": "Apache-2.0",
     "url": "https://github.com/aws/aws-cdk",
@@ -26,7 +26,7 @@ kwargs = json.loads(
     ],
     "package_data": {
         "aws_cdk.aws_ec2_alpha._jsii": [
-            "aws-ec2-alpha@2.175.1-alpha.0.jsii.tgz"
+            "aws-ec2-alpha@2.176.0-alpha.0.jsii.tgz"
         ],
         "aws_cdk.aws_ec2_alpha": [
             "py.typed"
@@ -34,7 +34,7 @@ kwargs = json.loads(
     },
     "python_requires": "~=3.8",
     "install_requires": [
-        "aws-cdk-lib>=2.175.1, <3.0.0",
+        "aws-cdk-lib>=2.176.0, <3.0.0",
         "constructs>=10.0.0, <11.0.0",
         "jsii>=1.104.0, <2.0.0",
         "publication>=0.0.3",

{aws_cdk_aws_ec2_alpha-2.175.1a0 → aws_cdk_aws_ec2_alpha-2.176.0a0}/src/aws_cdk/aws_ec2_alpha/__init__.py RENAMED Viewed

@@ -297,7 +297,7 @@ acceptor_vpc = VpcV2(self, "VpcA",
 acceptor_role_arn = acceptor_vpc.create_acceptor_vpc_role("000000000000")
 ```
-After creating an IAM role in the acceptor account, we can initiate the peering connection request from the requestor VPC. Import accpeptorVpc to the stack using `fromVpcV2Attributes` method, it is recommended to specify owner account id of the acceptor VPC in case of cross account peering connection, if acceptor VPC is hosted in different region provide region value for import as well.
+After creating an IAM role in the acceptor account, we can initiate the peering connection request from the requestor VPC. Import acceptorVpc to the stack using `fromVpcV2Attributes` method, it is recommended to specify owner account id of the acceptor VPC in case of cross account peering connection, if acceptor VPC is hosted in different region provide region value for import as well.
 The following code snippet demonstrates how to set up VPC peering between two VPCs in different AWS accounts using CDK:
 ```python
@@ -453,11 +453,11 @@ For more information, see [What is AWS Site-to-Site VPN?](https://docs.aws.amazo
 VPN route propagation is a feature in Amazon Web Services (AWS) that automatically updates route tables in your Virtual Private Cloud (VPC) with routes learned from a VPN connection.
-To enable VPN route propogation, use the `vpnRoutePropagation` property to specify the subnets as an input to the function. VPN route propagation will then be enabled for each subnet with the corresponding route table IDs.
+To enable VPN route propagation, use the `vpnRoutePropagation` property to specify the subnets as an input to the function. VPN route propagation will then be enabled for each subnet with the corresponding route table IDs.
 Additionally, you can set up a route in any route table with the target set to the VPN Gateway. The function `enableVpnGatewayV2` returns a `VPNGatewayV2` object that you can reference later.
-The code example below provides the definition for setting up a VPN gateway with `vpnRoutePropogation` enabled:
+The code example below provides the definition for setting up a VPN gateway with `vpnRoutePropagation` enabled:
 ```python
 stack = Stack()
@@ -485,7 +485,7 @@ An internet gateway is a horizontally scaled, redundant, and highly available VP
 For more information, see [Enable VPC internet access using internet gateways](https://docs.aws.amazon.com/vpc/latest/userguide/vpc-igw-internet-access.html).
 You can add an internet gateway to a VPC using `addInternetGateway` method. By default, this method creates a route in all Public Subnets with outbound destination set to `0.0.0.0` for IPv4 and `::0` for IPv6 enabled VPC.
-Instead of using the default settings, you can configure a custom destinatation range by providing an optional input `destination` to the method.
+Instead of using the default settings, you can configure a custom destination range by providing an optional input `destination` to the method.
 The code example below shows how to add an internet gateway with a custom outbound destination IP range:
@@ -528,12 +528,12 @@ imported_vpc = VpcV2.from_vpc_v2_attributes(stack, "ImportedVpc",
 In case of cross account or cross region VPC, its recommended to provide region and ownerAccountId so that these values for the VPC can be used to populate correct arn value for the VPC. If a VPC region and account ID is not provided, then region and account configured in the stack will be used. Furthermore, these fields will be referenced later while setting up VPC peering connection, so its necessary to set these fields to a correct value.
-Below is an example of importing a cross region and cross acount VPC, VPC arn for this case would be 'arn:aws:ec2:us-west-2:123456789012:vpc/mockVpcID'
+Below is an example of importing a cross region and cross account VPC, VPC arn for this case would be 'arn:aws:ec2:us-west-2:123456789012:vpc/mockVpcID'
 ```python
 stack = Stack()
-# Importing a cross acount or cross region VPC
+# Importing a cross account or cross region VPC
 imported_vpc = VpcV2.from_vpc_v2_attributes(stack, "ImportedVpc",
     vpc_id="mockVpcID",
     vpc_cidr_block="10.0.0.0/16",
@@ -4050,7 +4050,7 @@ class Route(
     @builtins.property
     @jsii.member(jsii_name="targetRouterType")
     def target_router_type(self) -> _aws_cdk_aws_ec2_ceddda9d.RouterType:
-        '''(experimental) The type of router the route is targetting.
+        '''(experimental) The type of router the route is targeting.
         :stability: experimental
         '''

{aws_cdk_aws_ec2_alpha-2.175.1a0 → aws_cdk_aws_ec2_alpha-2.176.0a0}/src/aws_cdk/aws_ec2_alpha/_jsii/__init__.py RENAMED Viewed

@@ -33,9 +33,9 @@ import constructs._jsii
 __jsii_assembly__ = jsii.JSIIAssembly.load(
     "@aws-cdk/aws-ec2-alpha",
-    "2.175.1-alpha.0",
+    "2.176.0-alpha.0",
     __name__[0:-6],
-    "aws-ec2-alpha@2.175.1-alpha.0.jsii.tgz",
+    "aws-ec2-alpha@2.176.0-alpha.0.jsii.tgz",
 )
 __all__ = [

aws_cdk_aws_ec2_alpha-2.176.0a0/src/aws_cdk/aws_ec2_alpha/_jsii/aws-ec2-alpha@2.176.0-alpha.0.jsii.tgz ADDED Viewed

Binary file

{aws_cdk_aws_ec2_alpha-2.175.1a0 → aws_cdk_aws_ec2_alpha-2.176.0a0/src/aws_cdk.aws_ec2_alpha.egg-info}/PKG-INFO RENAMED Viewed

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: aws-cdk.aws-ec2-alpha
-Version: 2.175.1a0
+Version: 2.176.0a0
 Summary: The CDK construct library for VPC V2
 Home-page: https://github.com/aws/aws-cdk
 Author: Amazon Web Services
@@ -23,7 +23,7 @@ Requires-Python: ~=3.8
 Description-Content-Type: text/markdown
 License-File: LICENSE
 License-File: NOTICE
-Requires-Dist: aws-cdk-lib<3.0.0,>=2.175.1
+Requires-Dist: aws-cdk-lib<3.0.0,>=2.176.0
 Requires-Dist: constructs<11.0.0,>=10.0.0
 Requires-Dist: jsii<2.0.0,>=1.104.0
 Requires-Dist: publication>=0.0.3
@@ -327,7 +327,7 @@ acceptor_vpc = VpcV2(self, "VpcA",
 acceptor_role_arn = acceptor_vpc.create_acceptor_vpc_role("000000000000")
 ```
-After creating an IAM role in the acceptor account, we can initiate the peering connection request from the requestor VPC. Import accpeptorVpc to the stack using `fromVpcV2Attributes` method, it is recommended to specify owner account id of the acceptor VPC in case of cross account peering connection, if acceptor VPC is hosted in different region provide region value for import as well.
+After creating an IAM role in the acceptor account, we can initiate the peering connection request from the requestor VPC. Import acceptorVpc to the stack using `fromVpcV2Attributes` method, it is recommended to specify owner account id of the acceptor VPC in case of cross account peering connection, if acceptor VPC is hosted in different region provide region value for import as well.
 The following code snippet demonstrates how to set up VPC peering between two VPCs in different AWS accounts using CDK:
 ```python
@@ -483,11 +483,11 @@ For more information, see [What is AWS Site-to-Site VPN?](https://docs.aws.amazo
 VPN route propagation is a feature in Amazon Web Services (AWS) that automatically updates route tables in your Virtual Private Cloud (VPC) with routes learned from a VPN connection.
-To enable VPN route propogation, use the `vpnRoutePropagation` property to specify the subnets as an input to the function. VPN route propagation will then be enabled for each subnet with the corresponding route table IDs.
+To enable VPN route propagation, use the `vpnRoutePropagation` property to specify the subnets as an input to the function. VPN route propagation will then be enabled for each subnet with the corresponding route table IDs.
 Additionally, you can set up a route in any route table with the target set to the VPN Gateway. The function `enableVpnGatewayV2` returns a `VPNGatewayV2` object that you can reference later.
-The code example below provides the definition for setting up a VPN gateway with `vpnRoutePropogation` enabled:
+The code example below provides the definition for setting up a VPN gateway with `vpnRoutePropagation` enabled:
 ```python
 stack = Stack()
@@ -515,7 +515,7 @@ An internet gateway is a horizontally scaled, redundant, and highly available VP
 For more information, see [Enable VPC internet access using internet gateways](https://docs.aws.amazon.com/vpc/latest/userguide/vpc-igw-internet-access.html).
 You can add an internet gateway to a VPC using `addInternetGateway` method. By default, this method creates a route in all Public Subnets with outbound destination set to `0.0.0.0` for IPv4 and `::0` for IPv6 enabled VPC.
-Instead of using the default settings, you can configure a custom destinatation range by providing an optional input `destination` to the method.
+Instead of using the default settings, you can configure a custom destination range by providing an optional input `destination` to the method.
 The code example below shows how to add an internet gateway with a custom outbound destination IP range:
@@ -558,12 +558,12 @@ imported_vpc = VpcV2.from_vpc_v2_attributes(stack, "ImportedVpc",
 In case of cross account or cross region VPC, its recommended to provide region and ownerAccountId so that these values for the VPC can be used to populate correct arn value for the VPC. If a VPC region and account ID is not provided, then region and account configured in the stack will be used. Furthermore, these fields will be referenced later while setting up VPC peering connection, so its necessary to set these fields to a correct value.
-Below is an example of importing a cross region and cross acount VPC, VPC arn for this case would be 'arn:aws:ec2:us-west-2:123456789012:vpc/mockVpcID'
+Below is an example of importing a cross region and cross account VPC, VPC arn for this case would be 'arn:aws:ec2:us-west-2:123456789012:vpc/mockVpcID'
 ```python
 stack = Stack()
-# Importing a cross acount or cross region VPC
+# Importing a cross account or cross region VPC
 imported_vpc = VpcV2.from_vpc_v2_attributes(stack, "ImportedVpc",
     vpc_id="mockVpcID",
     vpc_cidr_block="10.0.0.0/16",

{aws_cdk_aws_ec2_alpha-2.175.1a0 → aws_cdk_aws_ec2_alpha-2.176.0a0}/src/aws_cdk.aws_ec2_alpha.egg-info/SOURCES.txt RENAMED Viewed

@@ -12,4 +12,4 @@ src/aws_cdk.aws_ec2_alpha.egg-info/top_level.txt
 src/aws_cdk/aws_ec2_alpha/__init__.py
 src/aws_cdk/aws_ec2_alpha/py.typed
 src/aws_cdk/aws_ec2_alpha/_jsii/__init__.py
-src/aws_cdk/aws_ec2_alpha/_jsii/aws-ec2-alpha@2.175.1-alpha.0.jsii.tgz
+src/aws_cdk/aws_ec2_alpha/_jsii/aws-ec2-alpha@2.176.0-alpha.0.jsii.tgz