aws-cdk-lib 2.140.0__py3-none-any.whl → 2.142.0__py3-none-any.whl

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-lib might be problematic. Click here for more details.

Files changed (49) hide show
  1. aws_cdk/__init__.py +9 -1
  2. aws_cdk/_jsii/__init__.py +1 -1
  3. aws_cdk/_jsii/{aws-cdk-lib@2.140.0.jsii.tgz → aws-cdk-lib@2.142.0.jsii.tgz} +0 -0
  4. aws_cdk/aws_appsync/__init__.py +224 -94
  5. aws_cdk/aws_autoscaling/__init__.py +109 -25
  6. aws_cdk/aws_bedrock/__init__.py +51 -41
  7. aws_cdk/aws_cloudfront/__init__.py +34 -78
  8. aws_cdk/aws_cloudtrail/__init__.py +13 -4
  9. aws_cdk/aws_codepipeline/__init__.py +364 -27
  10. aws_cdk/aws_connectcampaigns/__init__.py +2 -2
  11. aws_cdk/aws_datasync/__init__.py +51 -56
  12. aws_cdk/aws_docdb/__init__.py +181 -4
  13. aws_cdk/aws_dynamodb/__init__.py +410 -0
  14. aws_cdk/aws_ec2/__init__.py +91 -42
  15. aws_cdk/aws_ecr/__init__.py +32 -7
  16. aws_cdk/aws_ecs/__init__.py +65 -18
  17. aws_cdk/aws_eks/__init__.py +36 -3
  18. aws_cdk/aws_entityresolution/__init__.py +6 -2
  19. aws_cdk/aws_events/__init__.py +46 -25
  20. aws_cdk/aws_events_targets/__init__.py +341 -0
  21. aws_cdk/aws_fms/__init__.py +7 -7
  22. aws_cdk/aws_gamelift/__init__.py +261 -160
  23. aws_cdk/aws_iam/__init__.py +13 -8
  24. aws_cdk/aws_ivs/__init__.py +1 -3
  25. aws_cdk/aws_kms/__init__.py +11 -5
  26. aws_cdk/aws_lambda_nodejs/__init__.py +3 -0
  27. aws_cdk/aws_location/__init__.py +8 -4
  28. aws_cdk/aws_logs/__init__.py +6 -6
  29. aws_cdk/aws_oam/__init__.py +45 -11
  30. aws_cdk/aws_omics/__init__.py +4 -4
  31. aws_cdk/aws_paymentcryptography/__init__.py +128 -48
  32. aws_cdk/aws_pinpoint/__init__.py +7 -5
  33. aws_cdk/aws_qbusiness/__init__.py +620 -294
  34. aws_cdk/aws_quicksight/__init__.py +103 -40
  35. aws_cdk/aws_rds/__init__.py +80 -16
  36. aws_cdk/aws_route53profiles/__init__.py +49 -49
  37. aws_cdk/aws_s3/__init__.py +9 -2
  38. aws_cdk/aws_sagemaker/__init__.py +30 -30
  39. aws_cdk/aws_servicecatalog/__init__.py +27 -4
  40. aws_cdk/aws_ses/__init__.py +9 -9
  41. aws_cdk/aws_stepfunctions_tasks/__init__.py +7 -6
  42. aws_cdk/aws_transfer/__init__.py +4 -4
  43. aws_cdk/aws_voiceid/__init__.py +2 -2
  44. {aws_cdk_lib-2.140.0.dist-info → aws_cdk_lib-2.142.0.dist-info}/METADATA +10 -2
  45. {aws_cdk_lib-2.140.0.dist-info → aws_cdk_lib-2.142.0.dist-info}/RECORD +49 -49
  46. {aws_cdk_lib-2.140.0.dist-info → aws_cdk_lib-2.142.0.dist-info}/LICENSE +0 -0
  47. {aws_cdk_lib-2.140.0.dist-info → aws_cdk_lib-2.142.0.dist-info}/NOTICE +0 -0
  48. {aws_cdk_lib-2.140.0.dist-info → aws_cdk_lib-2.142.0.dist-info}/WHEEL +0 -0
  49. {aws_cdk_lib-2.140.0.dist-info → aws_cdk_lib-2.142.0.dist-info}/top_level.txt +0 -0
@@ -544,13 +544,12 @@ Additionally, you can load the function's code from a file using the `FunctionCo
544
544
 
545
545
  If you set `autoPublish` to false, the function will not be automatically published to the LIVE stage when it’s created.
546
546
 
547
- ``ts
548
- new cloudfront.Function(this, 'Function', {
549
- code: cloudfront.FunctionCode.fromInline('function handler(event) { return event.request }'),
550
- runtime: cloudfront.FunctionRuntime.JS_2_0,
551
- autoPublish: false
552
- });
553
-
547
+ ```python
548
+ cloudfront.Function(self, "Function",
549
+ code=cloudfront.FunctionCode.from_inline("function handler(event) { return event.request }"),
550
+ runtime=cloudfront.FunctionRuntime.JS_2_0,
551
+ auto_publish=False
552
+ )
554
553
  ```
555
554
 
556
555
  ### Key Value Store
@@ -560,8 +559,8 @@ by default.
560
559
 
561
560
  To create an empty Key Value Store:
562
561
 
563
- ```ts
564
- const store = new cloudfront.KeyValueStore(this, 'KeyValueStore');
562
+ ```python
563
+ store = cloudfront.KeyValueStore(self, "KeyValueStore")
565
564
  ```
566
565
 
567
566
  To also include an initial set of values, the `source` property can be specified, either from a
@@ -16480,20 +16479,12 @@ class FunctionCode(
16480
16479
 
16481
16480
  Example::
16482
16481
 
16483
- # s3_bucket: s3.Bucket
16484
- # Add a cloudfront Function to a Distribution
16485
- cf_function = cloudfront.Function(self, "Function",
16482
+ store = cloudfront.KeyValueStore(self, "KeyValueStore")
16483
+ cloudfront.Function(self, "Function",
16486
16484
  code=cloudfront.FunctionCode.from_inline("function handler(event) { return event.request }"),
16487
- runtime=cloudfront.FunctionRuntime.JS_2_0
16488
- )
16489
- cloudfront.Distribution(self, "distro",
16490
- default_behavior=cloudfront.BehaviorOptions(
16491
- origin=origins.S3Origin(s3_bucket),
16492
- function_associations=[cloudfront.FunctionAssociation(
16493
- function=cf_function,
16494
- event_type=cloudfront.FunctionEventType.VIEWER_REQUEST
16495
- )]
16496
- )
16485
+ # Note that JS_2_0 must be used for Key Value Store support
16486
+ runtime=cloudfront.FunctionRuntime.JS_2_0,
16487
+ key_value_store=store
16497
16488
  )
16498
16489
  '''
16499
16490
 
@@ -16611,20 +16602,12 @@ class FunctionProps:
16611
16602
 
16612
16603
  Example::
16613
16604
 
16614
- # s3_bucket: s3.Bucket
16615
- # Add a cloudfront Function to a Distribution
16616
- cf_function = cloudfront.Function(self, "Function",
16605
+ store = cloudfront.KeyValueStore(self, "KeyValueStore")
16606
+ cloudfront.Function(self, "Function",
16617
16607
  code=cloudfront.FunctionCode.from_inline("function handler(event) { return event.request }"),
16618
- runtime=cloudfront.FunctionRuntime.JS_2_0
16619
- )
16620
- cloudfront.Distribution(self, "distro",
16621
- default_behavior=cloudfront.BehaviorOptions(
16622
- origin=origins.S3Origin(s3_bucket),
16623
- function_associations=[cloudfront.FunctionAssociation(
16624
- function=cf_function,
16625
- event_type=cloudfront.FunctionEventType.VIEWER_REQUEST
16626
- )]
16627
- )
16608
+ # Note that JS_2_0 must be used for Key Value Store support
16609
+ runtime=cloudfront.FunctionRuntime.JS_2_0,
16610
+ key_value_store=store
16628
16611
  )
16629
16612
  '''
16630
16613
  if __debug__:
@@ -16726,20 +16709,12 @@ class FunctionRuntime(
16726
16709
 
16727
16710
  Example::
16728
16711
 
16729
- # s3_bucket: s3.Bucket
16730
- # Add a cloudfront Function to a Distribution
16731
- cf_function = cloudfront.Function(self, "Function",
16712
+ store = cloudfront.KeyValueStore(self, "KeyValueStore")
16713
+ cloudfront.Function(self, "Function",
16732
16714
  code=cloudfront.FunctionCode.from_inline("function handler(event) { return event.request }"),
16733
- runtime=cloudfront.FunctionRuntime.JS_2_0
16734
- )
16735
- cloudfront.Distribution(self, "distro",
16736
- default_behavior=cloudfront.BehaviorOptions(
16737
- origin=origins.S3Origin(s3_bucket),
16738
- function_associations=[cloudfront.FunctionAssociation(
16739
- function=cf_function,
16740
- event_type=cloudfront.FunctionEventType.VIEWER_REQUEST
16741
- )]
16742
- )
16715
+ # Note that JS_2_0 must be used for Key Value Store support
16716
+ runtime=cloudfront.FunctionRuntime.JS_2_0,
16717
+ key_value_store=store
16743
16718
  )
16744
16719
  '''
16745
16720
 
@@ -17941,23 +17916,12 @@ class KeyValueStore(
17941
17916
 
17942
17917
  Example::
17943
17918
 
17944
- store_asset = cloudfront.KeyValueStore(self, "KeyValueStoreAsset",
17945
- key_value_store_name="KeyValueStoreAsset",
17946
- source=cloudfront.ImportSource.from_asset("path-to-data.json")
17947
- )
17948
-
17949
- store_inline = cloudfront.KeyValueStore(self, "KeyValueStoreInline",
17950
- key_value_store_name="KeyValueStoreInline",
17951
- source=cloudfront.ImportSource.from_inline(JSON.stringify({
17952
- "data": [{
17953
- "key": "key1",
17954
- "value": "value1"
17955
- }, {
17956
- "key": "key2",
17957
- "value": "value2"
17958
- }
17959
- ]
17960
- }))
17919
+ store = cloudfront.KeyValueStore(self, "KeyValueStore")
17920
+ cloudfront.Function(self, "Function",
17921
+ code=cloudfront.FunctionCode.from_inline("function handler(event) { return event.request }"),
17922
+ # Note that JS_2_0 must be used for Key Value Store support
17923
+ runtime=cloudfront.FunctionRuntime.JS_2_0,
17924
+ key_value_store=store
17961
17925
  )
17962
17926
  '''
17963
17927
 
@@ -23802,20 +23766,12 @@ class Function(
23802
23766
 
23803
23767
  Example::
23804
23768
 
23805
- # s3_bucket: s3.Bucket
23806
- # Add a cloudfront Function to a Distribution
23807
- cf_function = cloudfront.Function(self, "Function",
23769
+ store = cloudfront.KeyValueStore(self, "KeyValueStore")
23770
+ cloudfront.Function(self, "Function",
23808
23771
  code=cloudfront.FunctionCode.from_inline("function handler(event) { return event.request }"),
23809
- runtime=cloudfront.FunctionRuntime.JS_2_0
23810
- )
23811
- cloudfront.Distribution(self, "distro",
23812
- default_behavior=cloudfront.BehaviorOptions(
23813
- origin=origins.S3Origin(s3_bucket),
23814
- function_associations=[cloudfront.FunctionAssociation(
23815
- function=cf_function,
23816
- event_type=cloudfront.FunctionEventType.VIEWER_REQUEST
23817
- )]
23818
- )
23772
+ # Note that JS_2_0 must be used for Key Value Store support
23773
+ runtime=cloudfront.FunctionRuntime.JS_2_0,
23774
+ key_value_store=store
23819
23775
  )
23820
23776
  '''
23821
23777
 
@@ -3383,9 +3383,18 @@ class CfnTrail(
3383
3383
  type: builtins.str,
3384
3384
  values: typing.Optional[typing.Sequence[builtins.str]] = None,
3385
3385
  ) -> None:
3386
- '''The Amazon S3 buckets, AWS Lambda functions, or Amazon DynamoDB tables that you specify in your event selectors for your trail to log data events.
3386
+ '''Data events provide information about the resource operations performed on or within a resource itself.
3387
+
3388
+ These are also known as data plane operations. You can specify up to 250 data resources for a trail.
3389
+
3390
+ Configure the ``DataResource`` to specify the resource type and resource ARNs for which you want to log data events.
3391
+
3392
+ You can specify the following resource types in your event selectors for your trail:
3393
+
3394
+ - ``AWS::DynamoDB::Table``
3395
+ - ``AWS::Lambda::Function``
3396
+ - ``AWS::S3::Object``
3387
3397
 
3388
- Data events provide information about the resource operations performed on or within a resource itself. These are also known as data plane operations. You can specify up to 250 data resources for a trail.
3389
3398
  .. epigraph::
3390
3399
 
3391
3400
  The total number of allowed data resources is 250. This number can be distributed between 1 and 5 event selectors, but the total cannot exceed 250 across all selectors for the trail.
@@ -3406,7 +3415,7 @@ class CfnTrail(
3406
3415
  - The ``Invoke`` API operation on *MyOtherLambdaFunction* is an Lambda API. Because the CloudTrail user did not specify logging data events for all Lambda functions, the ``Invoke`` operation for *MyOtherLambdaFunction* does not match the function specified for the trail. The trail doesn’t log the event.
3407
3416
 
3408
3417
  :param type: The resource type in which you want to log data events. You can specify the following *basic* event selector resource types: - ``AWS::DynamoDB::Table`` - ``AWS::Lambda::Function`` - ``AWS::S3::Object`` Additional resource types are available through *advanced* event selectors. For more information about these additional resource types, see `AdvancedFieldSelector <https://docs.aws.amazon.com/awscloudtrail/latest/APIReference/API_AdvancedFieldSelector.html>`_ .
3409
- :param values: An array of Amazon Resource Name (ARN) strings or partial ARN strings for the specified objects. - To log data events for all objects in all S3 buckets in your AWS account , specify the prefix as ``arn:aws:s3`` . .. epigraph:: This also enables logging of data event activity performed by any user or role in your AWS account , even if that activity is performed on a bucket that belongs to another AWS account . - To log data events for all objects in an S3 bucket, specify the bucket and an empty object prefix such as ``arn:aws:s3:::bucket-1/`` . The trail logs data events for all objects in this S3 bucket. - To log data events for specific objects, specify the S3 bucket and object prefix such as ``arn:aws:s3:::bucket-1/example-images`` . The trail logs data events for objects in this S3 bucket that match the prefix. - To log data events for all Lambda functions in your AWS account , specify the prefix as ``arn:aws:lambda`` . .. epigraph:: This also enables logging of ``Invoke`` activity performed by any user or role in your AWS account , even if that activity is performed on a function that belongs to another AWS account . - To log data events for a specific Lambda function, specify the function ARN. .. epigraph:: Lambda function ARNs are exact. For example, if you specify a function ARN *arn:aws:lambda:us-west-2:111111111111:function:helloworld* , data events will only be logged for *arn:aws:lambda:us-west-2:111111111111:function:helloworld* . They will not be logged for *arn:aws:lambda:us-west-2:111111111111:function:helloworld2* . - To log data events for all DynamoDB tables in your AWS account , specify the prefix as ``arn:aws:dynamodb`` .
3418
+ :param values: An array of Amazon Resource Name (ARN) strings or partial ARN strings for the specified resource type. - To log data events for all objects in all S3 buckets in your AWS account , specify the prefix as ``arn:aws:s3`` . .. epigraph:: This also enables logging of data event activity performed by any user or role in your AWS account , even if that activity is performed on a bucket that belongs to another AWS account . - To log data events for all objects in an S3 bucket, specify the bucket and an empty object prefix such as ``arn:aws:s3:::bucket-1/`` . The trail logs data events for all objects in this S3 bucket. - To log data events for specific objects, specify the S3 bucket and object prefix such as ``arn:aws:s3:::bucket-1/example-images`` . The trail logs data events for objects in this S3 bucket that match the prefix. - To log data events for all Lambda functions in your AWS account , specify the prefix as ``arn:aws:lambda`` . .. epigraph:: This also enables logging of ``Invoke`` activity performed by any user or role in your AWS account , even if that activity is performed on a function that belongs to another AWS account . - To log data events for a specific Lambda function, specify the function ARN. .. epigraph:: Lambda function ARNs are exact. For example, if you specify a function ARN *arn:aws:lambda:us-west-2:111111111111:function:helloworld* , data events will only be logged for *arn:aws:lambda:us-west-2:111111111111:function:helloworld* . They will not be logged for *arn:aws:lambda:us-west-2:111111111111:function:helloworld2* . - To log data events for all DynamoDB tables in your AWS account , specify the prefix as ``arn:aws:dynamodb`` .
3410
3419
 
3411
3420
  :see: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-cloudtrail-trail-dataresource.html
3412
3421
  :exampleMetadata: fixture=_generated
@@ -3454,7 +3463,7 @@ class CfnTrail(
3454
3463
 
3455
3464
  @builtins.property
3456
3465
  def values(self) -> typing.Optional[typing.List[builtins.str]]:
3457
- '''An array of Amazon Resource Name (ARN) strings or partial ARN strings for the specified objects.
3466
+ '''An array of Amazon Resource Name (ARN) strings or partial ARN strings for the specified resource type.
3458
3467
 
3459
3468
  - To log data events for all objects in all S3 buckets in your AWS account , specify the prefix as ``arn:aws:s3`` .
3460
3469