aws-cdk-lib 2.215.0__py3-none-any.whl → 2.217.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 (64) hide show
  1. aws_cdk/__init__.py +90 -58
  2. aws_cdk/_jsii/__init__.py +1 -1
  3. aws_cdk/_jsii/{aws-cdk-lib@2.215.0.jsii.tgz → aws-cdk-lib@2.217.0.jsii.tgz} +0 -0
  4. aws_cdk/aws_acmpca/__init__.py +1 -1
  5. aws_cdk/aws_amplify/__init__.py +8 -8
  6. aws_cdk/aws_apigateway/__init__.py +26 -6
  7. aws_cdk/aws_apigatewayv2/__init__.py +32 -21
  8. aws_cdk/aws_appmesh/__init__.py +12 -12
  9. aws_cdk/aws_appstream/__init__.py +14 -4
  10. aws_cdk/aws_appsync/__init__.py +3 -3
  11. aws_cdk/aws_aps/__init__.py +459 -0
  12. aws_cdk/aws_batch/__init__.py +6 -2
  13. aws_cdk/aws_bedrock/__init__.py +162 -0
  14. aws_cdk/aws_bedrockagentcore/__init__.py +3178 -0
  15. aws_cdk/aws_certificatemanager/__init__.py +9 -10
  16. aws_cdk/aws_cleanrooms/__init__.py +163 -0
  17. aws_cdk/aws_cloudformation/__init__.py +14 -14
  18. aws_cdk/aws_cloudfront/__init__.py +91 -10
  19. aws_cdk/aws_cloudfront_origins/__init__.py +422 -47
  20. aws_cdk/aws_cognito/__init__.py +2 -2
  21. aws_cdk/aws_connect/__init__.py +138 -10
  22. aws_cdk/aws_cur/__init__.py +57 -3
  23. aws_cdk/aws_datasync/__init__.py +351 -0
  24. aws_cdk/aws_datazone/__init__.py +675 -2
  25. aws_cdk/aws_dynamodb/__init__.py +123 -0
  26. aws_cdk/aws_ec2/__init__.py +55 -10
  27. aws_cdk/aws_ecr/__init__.py +4 -0
  28. aws_cdk/aws_ecs/__init__.py +55 -12
  29. aws_cdk/aws_elasticloadbalancingv2/__init__.py +275 -0
  30. aws_cdk/aws_elasticsearch/__init__.py +2 -2
  31. aws_cdk/aws_events/__init__.py +187 -0
  32. aws_cdk/aws_evs/__init__.py +58 -4
  33. aws_cdk/aws_gamelift/__init__.py +72 -56
  34. aws_cdk/aws_iam/__init__.py +1 -1
  35. aws_cdk/aws_iotcoredeviceadvisor/__init__.py +35 -38
  36. aws_cdk/aws_iotsitewise/__init__.py +75 -111
  37. aws_cdk/aws_kinesisanalytics/__init__.py +315 -125
  38. aws_cdk/aws_kms/__init__.py +10 -2
  39. aws_cdk/aws_lambda/__init__.py +62 -8
  40. aws_cdk/aws_medialive/__init__.py +127 -0
  41. aws_cdk/aws_mediapackage/__init__.py +2 -2
  42. aws_cdk/aws_networkfirewall/__init__.py +10 -10
  43. aws_cdk/aws_networkmanager/__init__.py +63 -0
  44. aws_cdk/aws_odb/__init__.py +2082 -195
  45. aws_cdk/aws_omics/__init__.py +1414 -171
  46. aws_cdk/aws_opensearchserverless/__init__.py +164 -21
  47. aws_cdk/aws_opensearchservice/__init__.py +5 -4
  48. aws_cdk/aws_pcs/__init__.py +9 -9
  49. aws_cdk/aws_quicksight/__init__.py +295 -3
  50. aws_cdk/aws_rds/__init__.py +338 -58
  51. aws_cdk/aws_route53/__init__.py +5926 -4376
  52. aws_cdk/aws_sagemaker/__init__.py +251 -1
  53. aws_cdk/aws_servicecatalog/__init__.py +162 -154
  54. aws_cdk/aws_smsvoice/__init__.py +5218 -0
  55. aws_cdk/aws_stepfunctions_tasks/__init__.py +669 -81
  56. aws_cdk/aws_transfer/__init__.py +13 -12
  57. aws_cdk/aws_verifiedpermissions/__init__.py +1 -1
  58. aws_cdk/aws_workspacesinstances/__init__.py +641 -2
  59. {aws_cdk_lib-2.215.0.dist-info → aws_cdk_lib-2.217.0.dist-info}/METADATA +1 -1
  60. {aws_cdk_lib-2.215.0.dist-info → aws_cdk_lib-2.217.0.dist-info}/RECORD +64 -62
  61. {aws_cdk_lib-2.215.0.dist-info → aws_cdk_lib-2.217.0.dist-info}/LICENSE +0 -0
  62. {aws_cdk_lib-2.215.0.dist-info → aws_cdk_lib-2.217.0.dist-info}/NOTICE +0 -0
  63. {aws_cdk_lib-2.215.0.dist-info → aws_cdk_lib-2.217.0.dist-info}/WHEEL +0 -0
  64. {aws_cdk_lib-2.215.0.dist-info → aws_cdk_lib-2.217.0.dist-info}/top_level.txt +0 -0
@@ -7361,7 +7361,7 @@ class CfnServiceProps:
7361
7361
  ) -> None:
7362
7362
  '''Properties for defining a ``CfnService``.
7363
7363
 
7364
- :param availability_zone_rebalancing: Indicates whether to use Availability Zone rebalancing for the service. For more information, see `Balancing an Amazon ECS service across Availability Zones <https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-rebalancing.html>`_ in the **Amazon Elastic Container Service Developer Guide** . Default: - "ENABLED"
7364
+ :param availability_zone_rebalancing: Indicates whether to use Availability Zone rebalancing for the service. For more information, see `Balancing an Amazon ECS service across Availability Zones <https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-rebalancing.html>`_ in the **Amazon Elastic Container Service Developer Guide** . The default behavior of ``AvailabilityZoneRebalancing`` differs between create and update requests: - For create service requests, when no value is specified for ``AvailabilityZoneRebalancing`` , Amazon ECS defaults the value to ``ENABLED`` . - For update service requests, when no value is specified for ``AvailabilityZoneRebalancing`` , Amazon ECS defaults to the existing service’s ``AvailabilityZoneRebalancing`` value. If the service never had an ``AvailabilityZoneRebalancing`` value set, Amazon ECS treats this as ``DISABLED`` . Default: - "ENABLED"
7365
7365
  :param capacity_provider_strategy: The capacity provider strategy to use for the service. If a ``capacityProviderStrategy`` is specified, the ``launchType`` parameter must be omitted. If no ``capacityProviderStrategy`` or ``launchType`` is specified, the ``defaultCapacityProviderStrategy`` for the cluster is used. A capacity provider strategy can contain a maximum of 20 capacity providers. .. epigraph:: To remove this property from your service resource, specify an empty ``CapacityProviderStrategyItem`` array.
7366
7366
  :param cluster: The short name or full Amazon Resource Name (ARN) of the cluster that you run your service on. If you do not specify a cluster, the default cluster is assumed.
7367
7367
  :param deployment_configuration: Optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks.
@@ -7370,7 +7370,7 @@ class CfnServiceProps:
7370
7370
  :param enable_ecs_managed_tags: Specifies whether to turn on Amazon ECS managed tags for the tasks within the service. For more information, see `Tagging your Amazon ECS resources <https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-using-tags.html>`_ in the *Amazon Elastic Container Service Developer Guide* . When you use Amazon ECS managed tags, you must set the ``propagateTags`` request parameter.
7371
7371
  :param enable_execute_command: Determines whether the execute command functionality is turned on for the service. If ``true`` , the execute command functionality is turned on for all containers in tasks as part of the service.
7372
7372
  :param force_new_deployment: Determines whether to force a new deployment of the service. By default, deployments aren't forced. You can use this option to start a new deployment with no service definition changes. For example, you can update a service's tasks to use a newer Docker image with the same image/tag combination ( ``my_image:latest`` ) or to roll Fargate tasks onto a newer platform version.
7373
- :param health_check_grace_period_seconds: The period of time, in seconds, that the Amazon ECS service scheduler ignores unhealthy Elastic Load Balancing, VPC Lattice, and container health checks after a task has first started. If you don't specify a health check grace period value, the default value of ``0`` is used. If you don't use any of the health checks, then ``healthCheckGracePeriodSeconds`` is unused. If your service's tasks take a while to start and respond to health checks, you can specify a health check grace period of up to 2,147,483,647 seconds (about 69 years). During that time, the Amazon ECS service scheduler ignores health check status. This grace period can prevent the service scheduler from marking tasks as unhealthy and stopping them before they have time to come up.
7373
+ :param health_check_grace_period_seconds: The period of time, in seconds, that the Amazon Amazon ECS service scheduler ignores unhealthy Elastic Load Balancing, VPC Lattice, and container health checks after a task has first started. If you do not specify a health check grace period value, the default value of 0 is used. If you do not use any of the health checks, then ``healthCheckGracePeriodSeconds`` is unused. If your service has more running tasks than desired, unhealthy tasks in the grace period might be stopped to reach the desired count.
7374
7374
  :param launch_type: The launch type on which to run your service. For more information, see `Amazon ECS Launch Types <https://docs.aws.amazon.com/AmazonECS/latest/developerguide/launch_types.html>`_ in the *Amazon Elastic Container Service Developer Guide* .
7375
7375
  :param load_balancers: A list of load balancer objects to associate with the service. If you specify the ``Role`` property, ``LoadBalancers`` must be specified as well. For information about the number of load balancers that you can specify per service, see `Service Load Balancing <https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-load-balancing.html>`_ in the *Amazon Elastic Container Service Developer Guide* . .. epigraph:: To remove this property from your service resource, specify an empty ``LoadBalancer`` array.
7376
7376
  :param network_configuration: The network configuration for the service. This parameter is required for task definitions that use the ``awsvpc`` network mode to receive their own elastic network interface, and it is not supported for other network modes. For more information, see `Task Networking <https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-networking.html>`_ in the *Amazon Elastic Container Service Developer Guide* .
@@ -7397,6 +7397,8 @@ class CfnServiceProps:
7397
7397
  # The values are placeholders you should change.
7398
7398
  from aws_cdk import aws_ecs as ecs
7399
7399
 
7400
+ # hook_details: Any
7401
+
7400
7402
  cfn_service_props = ecs.CfnServiceProps(
7401
7403
  availability_zone_rebalancing="availabilityZoneRebalancing",
7402
7404
  capacity_provider_strategy=[ecs.CfnService.CapacityProviderStrategyItemProperty(
@@ -7419,7 +7421,10 @@ class CfnServiceProps:
7419
7421
  lifecycle_hooks=[ecs.CfnService.DeploymentLifecycleHookProperty(
7420
7422
  hook_target_arn="hookTargetArn",
7421
7423
  lifecycle_stages=["lifecycleStages"],
7422
- role_arn="roleArn"
7424
+ role_arn="roleArn",
7425
+
7426
+ # the properties below are optional
7427
+ hook_details=hook_details
7423
7428
  )],
7424
7429
  maximum_percent=123,
7425
7430
  minimum_healthy_percent=123,
@@ -7664,6 +7669,11 @@ class CfnServiceProps:
7664
7669
 
7665
7670
  For more information, see `Balancing an Amazon ECS service across Availability Zones <https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-rebalancing.html>`_ in the **Amazon Elastic Container Service Developer Guide** .
7666
7671
 
7672
+ The default behavior of ``AvailabilityZoneRebalancing`` differs between create and update requests:
7673
+
7674
+ - For create service requests, when no value is specified for ``AvailabilityZoneRebalancing`` , Amazon ECS defaults the value to ``ENABLED`` .
7675
+ - For update service requests, when no value is specified for ``AvailabilityZoneRebalancing`` , Amazon ECS defaults to the existing service’s ``AvailabilityZoneRebalancing`` value. If the service never had an ``AvailabilityZoneRebalancing`` value set, Amazon ECS treats this as ``DISABLED`` .
7676
+
7667
7677
  :default: - "ENABLED"
7668
7678
 
7669
7679
  :see: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-service.html#cfn-ecs-service-availabilityzonerebalancing
@@ -7778,11 +7788,11 @@ class CfnServiceProps:
7778
7788
 
7779
7789
  @builtins.property
7780
7790
  def health_check_grace_period_seconds(self) -> typing.Optional[jsii.Number]:
7781
- '''The period of time, in seconds, that the Amazon ECS service scheduler ignores unhealthy Elastic Load Balancing, VPC Lattice, and container health checks after a task has first started.
7791
+ '''The period of time, in seconds, that the Amazon Amazon ECS service scheduler ignores unhealthy Elastic Load Balancing, VPC Lattice, and container health checks after a task has first started.
7782
7792
 
7783
- If you don't specify a health check grace period value, the default value of ``0`` is used. If you don't use any of the health checks, then ``healthCheckGracePeriodSeconds`` is unused.
7793
+ If you do not specify a health check grace period value, the default value of 0 is used. If you do not use any of the health checks, then ``healthCheckGracePeriodSeconds`` is unused.
7784
7794
 
7785
- If your service's tasks take a while to start and respond to health checks, you can specify a health check grace period of up to 2,147,483,647 seconds (about 69 years). During that time, the Amazon ECS service scheduler ignores health check status. This grace period can prevent the service scheduler from marking tasks as unhealthy and stopping them before they have time to come up.
7795
+ If your service has more running tasks than desired, unhealthy tasks in the grace period might be stopped to reach the desired count.
7786
7796
 
7787
7797
  :see: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-service.html#cfn-ecs-service-healthcheckgraceperiodseconds
7788
7798
  '''
@@ -32493,6 +32503,8 @@ class CfnService(
32493
32503
  # The values are placeholders you should change.
32494
32504
  from aws_cdk import aws_ecs as ecs
32495
32505
 
32506
+ # hook_details: Any
32507
+
32496
32508
  cfn_service = ecs.CfnService(self, "MyCfnService",
32497
32509
  availability_zone_rebalancing="availabilityZoneRebalancing",
32498
32510
  capacity_provider_strategy=[ecs.CfnService.CapacityProviderStrategyItemProperty(
@@ -32515,7 +32527,10 @@ class CfnService(
32515
32527
  lifecycle_hooks=[ecs.CfnService.DeploymentLifecycleHookProperty(
32516
32528
  hook_target_arn="hookTargetArn",
32517
32529
  lifecycle_stages=["lifecycleStages"],
32518
- role_arn="roleArn"
32530
+ role_arn="roleArn",
32531
+
32532
+ # the properties below are optional
32533
+ hook_details=hook_details
32519
32534
  )],
32520
32535
  maximum_percent=123,
32521
32536
  minimum_healthy_percent=123,
@@ -32708,7 +32723,7 @@ class CfnService(
32708
32723
  '''
32709
32724
  :param scope: Scope in which this resource is defined.
32710
32725
  :param id: Construct identifier for this resource (unique in its scope).
32711
- :param availability_zone_rebalancing: Indicates whether to use Availability Zone rebalancing for the service. For more information, see `Balancing an Amazon ECS service across Availability Zones <https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-rebalancing.html>`_ in the **Amazon Elastic Container Service Developer Guide** . Default: - "ENABLED"
32726
+ :param availability_zone_rebalancing: Indicates whether to use Availability Zone rebalancing for the service. For more information, see `Balancing an Amazon ECS service across Availability Zones <https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-rebalancing.html>`_ in the **Amazon Elastic Container Service Developer Guide** . The default behavior of ``AvailabilityZoneRebalancing`` differs between create and update requests: - For create service requests, when no value is specified for ``AvailabilityZoneRebalancing`` , Amazon ECS defaults the value to ``ENABLED`` . - For update service requests, when no value is specified for ``AvailabilityZoneRebalancing`` , Amazon ECS defaults to the existing service’s ``AvailabilityZoneRebalancing`` value. If the service never had an ``AvailabilityZoneRebalancing`` value set, Amazon ECS treats this as ``DISABLED`` . Default: - "ENABLED"
32712
32727
  :param capacity_provider_strategy: The capacity provider strategy to use for the service. If a ``capacityProviderStrategy`` is specified, the ``launchType`` parameter must be omitted. If no ``capacityProviderStrategy`` or ``launchType`` is specified, the ``defaultCapacityProviderStrategy`` for the cluster is used. A capacity provider strategy can contain a maximum of 20 capacity providers. .. epigraph:: To remove this property from your service resource, specify an empty ``CapacityProviderStrategyItem`` array.
32713
32728
  :param cluster: The short name or full Amazon Resource Name (ARN) of the cluster that you run your service on. If you do not specify a cluster, the default cluster is assumed.
32714
32729
  :param deployment_configuration: Optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks.
@@ -32717,7 +32732,7 @@ class CfnService(
32717
32732
  :param enable_ecs_managed_tags: Specifies whether to turn on Amazon ECS managed tags for the tasks within the service. For more information, see `Tagging your Amazon ECS resources <https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-using-tags.html>`_ in the *Amazon Elastic Container Service Developer Guide* . When you use Amazon ECS managed tags, you must set the ``propagateTags`` request parameter.
32718
32733
  :param enable_execute_command: Determines whether the execute command functionality is turned on for the service. If ``true`` , the execute command functionality is turned on for all containers in tasks as part of the service.
32719
32734
  :param force_new_deployment: Determines whether to force a new deployment of the service. By default, deployments aren't forced. You can use this option to start a new deployment with no service definition changes. For example, you can update a service's tasks to use a newer Docker image with the same image/tag combination ( ``my_image:latest`` ) or to roll Fargate tasks onto a newer platform version.
32720
- :param health_check_grace_period_seconds: The period of time, in seconds, that the Amazon ECS service scheduler ignores unhealthy Elastic Load Balancing, VPC Lattice, and container health checks after a task has first started. If you don't specify a health check grace period value, the default value of ``0`` is used. If you don't use any of the health checks, then ``healthCheckGracePeriodSeconds`` is unused. If your service's tasks take a while to start and respond to health checks, you can specify a health check grace period of up to 2,147,483,647 seconds (about 69 years). During that time, the Amazon ECS service scheduler ignores health check status. This grace period can prevent the service scheduler from marking tasks as unhealthy and stopping them before they have time to come up.
32735
+ :param health_check_grace_period_seconds: The period of time, in seconds, that the Amazon Amazon ECS service scheduler ignores unhealthy Elastic Load Balancing, VPC Lattice, and container health checks after a task has first started. If you do not specify a health check grace period value, the default value of 0 is used. If you do not use any of the health checks, then ``healthCheckGracePeriodSeconds`` is unused. If your service has more running tasks than desired, unhealthy tasks in the grace period might be stopped to reach the desired count.
32721
32736
  :param launch_type: The launch type on which to run your service. For more information, see `Amazon ECS Launch Types <https://docs.aws.amazon.com/AmazonECS/latest/developerguide/launch_types.html>`_ in the *Amazon Elastic Container Service Developer Guide* .
32722
32737
  :param load_balancers: A list of load balancer objects to associate with the service. If you specify the ``Role`` property, ``LoadBalancers`` must be specified as well. For information about the number of load balancers that you can specify per service, see `Service Load Balancing <https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-load-balancing.html>`_ in the *Amazon Elastic Container Service Developer Guide* . .. epigraph:: To remove this property from your service resource, specify an empty ``LoadBalancer`` array.
32723
32738
  :param network_configuration: The network configuration for the service. This parameter is required for task definitions that use the ``awsvpc`` network mode to receive their own elastic network interface, and it is not supported for other network modes. For more information, see `Task Networking <https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-networking.html>`_ in the *Amazon Elastic Container Service Developer Guide* .
@@ -32990,7 +33005,7 @@ class CfnService(
32990
33005
  @builtins.property
32991
33006
  @jsii.member(jsii_name="healthCheckGracePeriodSeconds")
32992
33007
  def health_check_grace_period_seconds(self) -> typing.Optional[jsii.Number]:
32993
- '''The period of time, in seconds, that the Amazon ECS service scheduler ignores unhealthy Elastic Load Balancing, VPC Lattice, and container health checks after a task has first started.'''
33008
+ '''The period of time, in seconds, that the Amazon Amazon ECS service scheduler ignores unhealthy Elastic Load Balancing, VPC Lattice, and container health checks after a task has first started.'''
32994
33009
  return typing.cast(typing.Optional[jsii.Number], jsii.get(self, "healthCheckGracePeriodSeconds"))
32995
33010
 
32996
33011
  @health_check_grace_period_seconds.setter
@@ -33825,6 +33840,8 @@ class CfnService(
33825
33840
  # The values are placeholders you should change.
33826
33841
  from aws_cdk import aws_ecs as ecs
33827
33842
 
33843
+ # hook_details: Any
33844
+
33828
33845
  deployment_configuration_property = ecs.CfnService.DeploymentConfigurationProperty(
33829
33846
  alarms=ecs.CfnService.DeploymentAlarmsProperty(
33830
33847
  alarm_names=["alarmNames"],
@@ -33839,7 +33856,10 @@ class CfnService(
33839
33856
  lifecycle_hooks=[ecs.CfnService.DeploymentLifecycleHookProperty(
33840
33857
  hook_target_arn="hookTargetArn",
33841
33858
  lifecycle_stages=["lifecycleStages"],
33842
- role_arn="roleArn"
33859
+ role_arn="roleArn",
33860
+
33861
+ # the properties below are optional
33862
+ hook_details=hook_details
33843
33863
  )],
33844
33864
  maximum_percent=123,
33845
33865
  minimum_healthy_percent=123,
@@ -34105,6 +34125,7 @@ class CfnService(
34105
34125
  "hook_target_arn": "hookTargetArn",
34106
34126
  "lifecycle_stages": "lifecycleStages",
34107
34127
  "role_arn": "roleArn",
34128
+ "hook_details": "hookDetails",
34108
34129
  },
34109
34130
  )
34110
34131
  class DeploymentLifecycleHookProperty:
@@ -34114,6 +34135,7 @@ class CfnService(
34114
34135
  hook_target_arn: builtins.str,
34115
34136
  lifecycle_stages: typing.Sequence[builtins.str],
34116
34137
  role_arn: builtins.str,
34138
+ hook_details: typing.Any = None,
34117
34139
  ) -> None:
34118
34140
  '''A deployment lifecycle hook runs custom logic at specific stages of the deployment process.
34119
34141
 
@@ -34124,6 +34146,7 @@ class CfnService(
34124
34146
  :param hook_target_arn: The Amazon Resource Name (ARN) of the hook target. Currently, only Lambda function ARNs are supported. You must provide this parameter when configuring a deployment lifecycle hook.
34125
34147
  :param lifecycle_stages: The lifecycle stages at which to run the hook. Choose from these valid values:. - RECONCILE_SERVICE The reconciliation stage that only happens when you start a new service deployment with more than 1 service revision in an ACTIVE state. You can use a lifecycle hook for this stage. - PRE_SCALE_UP The green service revision has not started. The blue service revision is handling 100% of the production traffic. There is no test traffic. You can use a lifecycle hook for this stage. - POST_SCALE_UP The green service revision has started. The blue service revision is handling 100% of the production traffic. There is no test traffic. You can use a lifecycle hook for this stage. - TEST_TRAFFIC_SHIFT The blue and green service revisions are running. The blue service revision handles 100% of the production traffic. The green service revision is migrating from 0% to 100% of test traffic. You can use a lifecycle hook for this stage. - POST_TEST_TRAFFIC_SHIFT The test traffic shift is complete. The green service revision handles 100% of the test traffic. You can use a lifecycle hook for this stage. - PRODUCTION_TRAFFIC_SHIFT Production traffic is shifting to the green service revision. The green service revision is migrating from 0% to 100% of production traffic. You can use a lifecycle hook for this stage. - POST_PRODUCTION_TRAFFIC_SHIFT The production traffic shift is complete. You can use a lifecycle hook for this stage. You must provide this parameter when configuring a deployment lifecycle hook.
34126
34148
  :param role_arn: The Amazon Resource Name (ARN) of the IAM role that grants Amazon ECS permission to call Lambda functions on your behalf. For more information, see `Permissions required for Lambda functions in Amazon ECS blue/green deployments <https://docs.aws.amazon.com/AmazonECS/latest/developerguide/blue-green-permissions.html>`_ in the *Amazon Elastic Container Service Developer Guide* .
34149
+ :param hook_details: Use this field to specify custom parameters that Amazon ECS passes to your hook target invocations (such as a Lambda function). This field must be a JSON object as a string.
34127
34150
 
34128
34151
  :see: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ecs-service-deploymentlifecyclehook.html
34129
34152
  :exampleMetadata: fixture=_generated
@@ -34134,10 +34157,15 @@ class CfnService(
34134
34157
  # The values are placeholders you should change.
34135
34158
  from aws_cdk import aws_ecs as ecs
34136
34159
 
34160
+ # hook_details: Any
34161
+
34137
34162
  deployment_lifecycle_hook_property = ecs.CfnService.DeploymentLifecycleHookProperty(
34138
34163
  hook_target_arn="hookTargetArn",
34139
34164
  lifecycle_stages=["lifecycleStages"],
34140
- role_arn="roleArn"
34165
+ role_arn="roleArn",
34166
+
34167
+ # the properties below are optional
34168
+ hook_details=hook_details
34141
34169
  )
34142
34170
  '''
34143
34171
  if __debug__:
@@ -34145,11 +34173,14 @@ class CfnService(
34145
34173
  check_type(argname="argument hook_target_arn", value=hook_target_arn, expected_type=type_hints["hook_target_arn"])
34146
34174
  check_type(argname="argument lifecycle_stages", value=lifecycle_stages, expected_type=type_hints["lifecycle_stages"])
34147
34175
  check_type(argname="argument role_arn", value=role_arn, expected_type=type_hints["role_arn"])
34176
+ check_type(argname="argument hook_details", value=hook_details, expected_type=type_hints["hook_details"])
34148
34177
  self._values: typing.Dict[builtins.str, typing.Any] = {
34149
34178
  "hook_target_arn": hook_target_arn,
34150
34179
  "lifecycle_stages": lifecycle_stages,
34151
34180
  "role_arn": role_arn,
34152
34181
  }
34182
+ if hook_details is not None:
34183
+ self._values["hook_details"] = hook_details
34153
34184
 
34154
34185
  @builtins.property
34155
34186
  def hook_target_arn(self) -> builtins.str:
@@ -34229,6 +34260,17 @@ class CfnService(
34229
34260
  assert result is not None, "Required property 'role_arn' is missing"
34230
34261
  return typing.cast(builtins.str, result)
34231
34262
 
34263
+ @builtins.property
34264
+ def hook_details(self) -> typing.Any:
34265
+ '''Use this field to specify custom parameters that Amazon ECS passes to your hook target invocations (such as a Lambda function).
34266
+
34267
+ This field must be a JSON object as a string.
34268
+
34269
+ :see: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ecs-service-deploymentlifecyclehook.html#cfn-ecs-service-deploymentlifecyclehook-hookdetails
34270
+ '''
34271
+ result = self._values.get("hook_details")
34272
+ return typing.cast(typing.Any, result)
34273
+
34232
34274
  def __eq__(self, rhs: typing.Any) -> builtins.bool:
34233
34275
  return isinstance(rhs, self.__class__) and rhs._values == self._values
34234
34276
 
@@ -49622,6 +49664,7 @@ def _typecheckingstub__81d51cf744a434ad2ba13fc9f3dea23611c28b28f4a9414d8324cf577
49622
49664
  hook_target_arn: builtins.str,
49623
49665
  lifecycle_stages: typing.Sequence[builtins.str],
49624
49666
  role_arn: builtins.str,
49667
+ hook_details: typing.Any = None,
49625
49668
  ) -> None:
49626
49669
  """Type checking stubs"""
49627
49670
  pass