aws-cdk.cx-api 2.174.1__tar.gz → 2.175.0__tar.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.cx-api might be problematic. Click here for more details.
- {aws_cdk_cx_api-2.174.1/src/aws_cdk.cx_api.egg-info → aws_cdk_cx_api-2.175.0}/PKG-INFO +43 -1
- {aws_cdk_cx_api-2.174.1 → aws_cdk_cx_api-2.175.0}/README.md +42 -0
- {aws_cdk_cx_api-2.174.1 → aws_cdk_cx_api-2.175.0}/setup.py +2 -2
- {aws_cdk_cx_api-2.174.1 → aws_cdk_cx_api-2.175.0}/src/aws_cdk/cx_api/__init__.py +42 -0
- {aws_cdk_cx_api-2.174.1 → aws_cdk_cx_api-2.175.0}/src/aws_cdk/cx_api/_jsii/__init__.py +1 -1
- aws_cdk_cx_api-2.175.0/src/aws_cdk/cx_api/_jsii/cx-api@2.175.0.jsii.tgz +0 -0
- {aws_cdk_cx_api-2.174.1 → aws_cdk_cx_api-2.175.0/src/aws_cdk.cx_api.egg-info}/PKG-INFO +43 -1
- {aws_cdk_cx_api-2.174.1 → aws_cdk_cx_api-2.175.0}/src/aws_cdk.cx_api.egg-info/SOURCES.txt +1 -1
- aws_cdk_cx_api-2.174.1/src/aws_cdk/cx_api/_jsii/cx-api@2.174.1.jsii.tgz +0 -0
- {aws_cdk_cx_api-2.174.1 → aws_cdk_cx_api-2.175.0}/LICENSE +0 -0
- {aws_cdk_cx_api-2.174.1 → aws_cdk_cx_api-2.175.0}/MANIFEST.in +0 -0
- {aws_cdk_cx_api-2.174.1 → aws_cdk_cx_api-2.175.0}/NOTICE +0 -0
- {aws_cdk_cx_api-2.174.1 → aws_cdk_cx_api-2.175.0}/pyproject.toml +0 -0
- {aws_cdk_cx_api-2.174.1 → aws_cdk_cx_api-2.175.0}/setup.cfg +0 -0
- {aws_cdk_cx_api-2.174.1 → aws_cdk_cx_api-2.175.0}/src/aws_cdk/cx_api/py.typed +0 -0
- {aws_cdk_cx_api-2.174.1 → aws_cdk_cx_api-2.175.0}/src/aws_cdk.cx_api.egg-info/dependency_links.txt +0 -0
- {aws_cdk_cx_api-2.174.1 → aws_cdk_cx_api-2.175.0}/src/aws_cdk.cx_api.egg-info/requires.txt +0 -0
- {aws_cdk_cx_api-2.174.1 → aws_cdk_cx_api-2.175.0}/src/aws_cdk.cx_api.egg-info/top_level.txt +0 -0
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.1
|
|
2
2
|
Name: aws-cdk.cx-api
|
|
3
|
-
Version: 2.
|
|
3
|
+
Version: 2.175.0
|
|
4
4
|
Summary: Cloud executable protocol
|
|
5
5
|
Home-page: https://github.com/aws/aws-cdk
|
|
6
6
|
Author: Amazon Web Services
|
|
@@ -543,3 +543,45 @@ If the flag is set to false then a custom resource will be created when using `U
|
|
|
543
543
|
}
|
|
544
544
|
}
|
|
545
545
|
```
|
|
546
|
+
|
|
547
|
+
* `@aws-cdk/aws-ecs:disableEcsImdsBlocking`
|
|
548
|
+
|
|
549
|
+
When set to true, CDK synth will throw exception if canContainersAccessInstanceRole is false.
|
|
550
|
+
|
|
551
|
+
In an ECS Cluster with `MachineImageType.AMAZON_LINUX_2`, the canContainersAccessInstanceRole=false option attempts to add commands to block containers from
|
|
552
|
+
accessing IMDS. CDK cannot guarantee the correct execution of the feature in all platforms. Setting this feature flag
|
|
553
|
+
to true will ensure CDK does not attempt to implement IMDS blocking. By <ins>**end of 2025**</ins>, CDK will remove the
|
|
554
|
+
IMDS blocking feature. See [Github discussion](https://github.com/aws/aws-cdk/discussions/32609) for more information.
|
|
555
|
+
|
|
556
|
+
**It is recommended to follow ECS documentation to block IMDS for your specific platform and cluster configuration.**
|
|
557
|
+
|
|
558
|
+
*cdk.json*
|
|
559
|
+
|
|
560
|
+
```json
|
|
561
|
+
{
|
|
562
|
+
"context": {
|
|
563
|
+
"@aws-cdk/aws-ecs:disableEcsImdsBlocking": true
|
|
564
|
+
}
|
|
565
|
+
}
|
|
566
|
+
```
|
|
567
|
+
|
|
568
|
+
* `@aws-cdk/aws-ecs:enableImdsBlockingDeprecatedFeature`
|
|
569
|
+
|
|
570
|
+
When set to true along with canContainersAccessInstanceRole=false in ECS cluster, new updated commands will be added to UserData to block container accessing IMDS. **Applicable to Linux only.**
|
|
571
|
+
|
|
572
|
+
In an ECS Cluster with `MachineImageType.AMAZON_LINUX_2`, the canContainersAccessInstanceRole=false option attempts to add commands to block containers from
|
|
573
|
+
accessing IMDS. Set this flag to true in order to use new and updated commands. Please note that this
|
|
574
|
+
feature alone with this feature flag will be deprecated by <ins>end of 2025</ins> as CDK cannot
|
|
575
|
+
guarantee the correct execution of the feature in all platforms. See [Github discussion](https://github.com/aws/aws-cdk/discussions/32609) for more information.
|
|
576
|
+
|
|
577
|
+
**It is recommended to follow ECS documentation to block IMDS for your specific platform and cluster configuration.**
|
|
578
|
+
|
|
579
|
+
*cdk.json*
|
|
580
|
+
|
|
581
|
+
```json
|
|
582
|
+
{
|
|
583
|
+
"context": {
|
|
584
|
+
"@aws-cdk/aws-ecs:enableImdsBlockingDeprecatedFeature": false,
|
|
585
|
+
},
|
|
586
|
+
}
|
|
587
|
+
```
|
|
@@ -513,3 +513,45 @@ If the flag is set to false then a custom resource will be created when using `U
|
|
|
513
513
|
}
|
|
514
514
|
}
|
|
515
515
|
```
|
|
516
|
+
|
|
517
|
+
* `@aws-cdk/aws-ecs:disableEcsImdsBlocking`
|
|
518
|
+
|
|
519
|
+
When set to true, CDK synth will throw exception if canContainersAccessInstanceRole is false.
|
|
520
|
+
|
|
521
|
+
In an ECS Cluster with `MachineImageType.AMAZON_LINUX_2`, the canContainersAccessInstanceRole=false option attempts to add commands to block containers from
|
|
522
|
+
accessing IMDS. CDK cannot guarantee the correct execution of the feature in all platforms. Setting this feature flag
|
|
523
|
+
to true will ensure CDK does not attempt to implement IMDS blocking. By <ins>**end of 2025**</ins>, CDK will remove the
|
|
524
|
+
IMDS blocking feature. See [Github discussion](https://github.com/aws/aws-cdk/discussions/32609) for more information.
|
|
525
|
+
|
|
526
|
+
**It is recommended to follow ECS documentation to block IMDS for your specific platform and cluster configuration.**
|
|
527
|
+
|
|
528
|
+
*cdk.json*
|
|
529
|
+
|
|
530
|
+
```json
|
|
531
|
+
{
|
|
532
|
+
"context": {
|
|
533
|
+
"@aws-cdk/aws-ecs:disableEcsImdsBlocking": true
|
|
534
|
+
}
|
|
535
|
+
}
|
|
536
|
+
```
|
|
537
|
+
|
|
538
|
+
* `@aws-cdk/aws-ecs:enableImdsBlockingDeprecatedFeature`
|
|
539
|
+
|
|
540
|
+
When set to true along with canContainersAccessInstanceRole=false in ECS cluster, new updated commands will be added to UserData to block container accessing IMDS. **Applicable to Linux only.**
|
|
541
|
+
|
|
542
|
+
In an ECS Cluster with `MachineImageType.AMAZON_LINUX_2`, the canContainersAccessInstanceRole=false option attempts to add commands to block containers from
|
|
543
|
+
accessing IMDS. Set this flag to true in order to use new and updated commands. Please note that this
|
|
544
|
+
feature alone with this feature flag will be deprecated by <ins>end of 2025</ins> as CDK cannot
|
|
545
|
+
guarantee the correct execution of the feature in all platforms. See [Github discussion](https://github.com/aws/aws-cdk/discussions/32609) for more information.
|
|
546
|
+
|
|
547
|
+
**It is recommended to follow ECS documentation to block IMDS for your specific platform and cluster configuration.**
|
|
548
|
+
|
|
549
|
+
*cdk.json*
|
|
550
|
+
|
|
551
|
+
```json
|
|
552
|
+
{
|
|
553
|
+
"context": {
|
|
554
|
+
"@aws-cdk/aws-ecs:enableImdsBlockingDeprecatedFeature": false,
|
|
555
|
+
},
|
|
556
|
+
}
|
|
557
|
+
```
|
|
@@ -5,7 +5,7 @@ kwargs = json.loads(
|
|
|
5
5
|
"""
|
|
6
6
|
{
|
|
7
7
|
"name": "aws-cdk.cx-api",
|
|
8
|
-
"version": "2.
|
|
8
|
+
"version": "2.175.0",
|
|
9
9
|
"description": "Cloud executable protocol",
|
|
10
10
|
"license": "Apache-2.0",
|
|
11
11
|
"url": "https://github.com/aws/aws-cdk",
|
|
@@ -26,7 +26,7 @@ kwargs = json.loads(
|
|
|
26
26
|
],
|
|
27
27
|
"package_data": {
|
|
28
28
|
"aws_cdk.cx_api._jsii": [
|
|
29
|
-
"cx-api@2.
|
|
29
|
+
"cx-api@2.175.0.jsii.tgz"
|
|
30
30
|
],
|
|
31
31
|
"aws_cdk.cx_api": [
|
|
32
32
|
"py.typed"
|
|
@@ -514,6 +514,48 @@ If the flag is set to false then a custom resource will be created when using `U
|
|
|
514
514
|
}
|
|
515
515
|
}
|
|
516
516
|
```
|
|
517
|
+
|
|
518
|
+
* `@aws-cdk/aws-ecs:disableEcsImdsBlocking`
|
|
519
|
+
|
|
520
|
+
When set to true, CDK synth will throw exception if canContainersAccessInstanceRole is false.
|
|
521
|
+
|
|
522
|
+
In an ECS Cluster with `MachineImageType.AMAZON_LINUX_2`, the canContainersAccessInstanceRole=false option attempts to add commands to block containers from
|
|
523
|
+
accessing IMDS. CDK cannot guarantee the correct execution of the feature in all platforms. Setting this feature flag
|
|
524
|
+
to true will ensure CDK does not attempt to implement IMDS blocking. By <ins>**end of 2025**</ins>, CDK will remove the
|
|
525
|
+
IMDS blocking feature. See [Github discussion](https://github.com/aws/aws-cdk/discussions/32609) for more information.
|
|
526
|
+
|
|
527
|
+
**It is recommended to follow ECS documentation to block IMDS for your specific platform and cluster configuration.**
|
|
528
|
+
|
|
529
|
+
*cdk.json*
|
|
530
|
+
|
|
531
|
+
```json
|
|
532
|
+
{
|
|
533
|
+
"context": {
|
|
534
|
+
"@aws-cdk/aws-ecs:disableEcsImdsBlocking": true
|
|
535
|
+
}
|
|
536
|
+
}
|
|
537
|
+
```
|
|
538
|
+
|
|
539
|
+
* `@aws-cdk/aws-ecs:enableImdsBlockingDeprecatedFeature`
|
|
540
|
+
|
|
541
|
+
When set to true along with canContainersAccessInstanceRole=false in ECS cluster, new updated commands will be added to UserData to block container accessing IMDS. **Applicable to Linux only.**
|
|
542
|
+
|
|
543
|
+
In an ECS Cluster with `MachineImageType.AMAZON_LINUX_2`, the canContainersAccessInstanceRole=false option attempts to add commands to block containers from
|
|
544
|
+
accessing IMDS. Set this flag to true in order to use new and updated commands. Please note that this
|
|
545
|
+
feature alone with this feature flag will be deprecated by <ins>end of 2025</ins> as CDK cannot
|
|
546
|
+
guarantee the correct execution of the feature in all platforms. See [Github discussion](https://github.com/aws/aws-cdk/discussions/32609) for more information.
|
|
547
|
+
|
|
548
|
+
**It is recommended to follow ECS documentation to block IMDS for your specific platform and cluster configuration.**
|
|
549
|
+
|
|
550
|
+
*cdk.json*
|
|
551
|
+
|
|
552
|
+
```json
|
|
553
|
+
{
|
|
554
|
+
"context": {
|
|
555
|
+
"@aws-cdk/aws-ecs:enableImdsBlockingDeprecatedFeature": false,
|
|
556
|
+
},
|
|
557
|
+
}
|
|
558
|
+
```
|
|
517
559
|
'''
|
|
518
560
|
from pkgutil import extend_path
|
|
519
561
|
__path__ = extend_path(__path__, __name__)
|
|
@@ -31,7 +31,7 @@ def check_type(argname: str, value: object, expected_type: typing.Any) -> typing
|
|
|
31
31
|
import aws_cdk.cloud_assembly_schema._jsii
|
|
32
32
|
|
|
33
33
|
__jsii_assembly__ = jsii.JSIIAssembly.load(
|
|
34
|
-
"@aws-cdk/cx-api", "2.
|
|
34
|
+
"@aws-cdk/cx-api", "2.175.0", __name__[0:-6], "cx-api@2.175.0.jsii.tgz"
|
|
35
35
|
)
|
|
36
36
|
|
|
37
37
|
__all__ = [
|
|
Binary file
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.1
|
|
2
2
|
Name: aws-cdk.cx-api
|
|
3
|
-
Version: 2.
|
|
3
|
+
Version: 2.175.0
|
|
4
4
|
Summary: Cloud executable protocol
|
|
5
5
|
Home-page: https://github.com/aws/aws-cdk
|
|
6
6
|
Author: Amazon Web Services
|
|
@@ -543,3 +543,45 @@ If the flag is set to false then a custom resource will be created when using `U
|
|
|
543
543
|
}
|
|
544
544
|
}
|
|
545
545
|
```
|
|
546
|
+
|
|
547
|
+
* `@aws-cdk/aws-ecs:disableEcsImdsBlocking`
|
|
548
|
+
|
|
549
|
+
When set to true, CDK synth will throw exception if canContainersAccessInstanceRole is false.
|
|
550
|
+
|
|
551
|
+
In an ECS Cluster with `MachineImageType.AMAZON_LINUX_2`, the canContainersAccessInstanceRole=false option attempts to add commands to block containers from
|
|
552
|
+
accessing IMDS. CDK cannot guarantee the correct execution of the feature in all platforms. Setting this feature flag
|
|
553
|
+
to true will ensure CDK does not attempt to implement IMDS blocking. By <ins>**end of 2025**</ins>, CDK will remove the
|
|
554
|
+
IMDS blocking feature. See [Github discussion](https://github.com/aws/aws-cdk/discussions/32609) for more information.
|
|
555
|
+
|
|
556
|
+
**It is recommended to follow ECS documentation to block IMDS for your specific platform and cluster configuration.**
|
|
557
|
+
|
|
558
|
+
*cdk.json*
|
|
559
|
+
|
|
560
|
+
```json
|
|
561
|
+
{
|
|
562
|
+
"context": {
|
|
563
|
+
"@aws-cdk/aws-ecs:disableEcsImdsBlocking": true
|
|
564
|
+
}
|
|
565
|
+
}
|
|
566
|
+
```
|
|
567
|
+
|
|
568
|
+
* `@aws-cdk/aws-ecs:enableImdsBlockingDeprecatedFeature`
|
|
569
|
+
|
|
570
|
+
When set to true along with canContainersAccessInstanceRole=false in ECS cluster, new updated commands will be added to UserData to block container accessing IMDS. **Applicable to Linux only.**
|
|
571
|
+
|
|
572
|
+
In an ECS Cluster with `MachineImageType.AMAZON_LINUX_2`, the canContainersAccessInstanceRole=false option attempts to add commands to block containers from
|
|
573
|
+
accessing IMDS. Set this flag to true in order to use new and updated commands. Please note that this
|
|
574
|
+
feature alone with this feature flag will be deprecated by <ins>end of 2025</ins> as CDK cannot
|
|
575
|
+
guarantee the correct execution of the feature in all platforms. See [Github discussion](https://github.com/aws/aws-cdk/discussions/32609) for more information.
|
|
576
|
+
|
|
577
|
+
**It is recommended to follow ECS documentation to block IMDS for your specific platform and cluster configuration.**
|
|
578
|
+
|
|
579
|
+
*cdk.json*
|
|
580
|
+
|
|
581
|
+
```json
|
|
582
|
+
{
|
|
583
|
+
"context": {
|
|
584
|
+
"@aws-cdk/aws-ecs:enableImdsBlockingDeprecatedFeature": false,
|
|
585
|
+
},
|
|
586
|
+
}
|
|
587
|
+
```
|
|
Binary file
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
{aws_cdk_cx_api-2.174.1 → aws_cdk_cx_api-2.175.0}/src/aws_cdk.cx_api.egg-info/dependency_links.txt
RENAMED
|
File without changes
|
|
File without changes
|
|
File without changes
|