aws-cdk-lib 2.187.0__py3-none-any.whl → 2.188.0__py3-none-any.whl

aws_cdk/aws_budgets/__init__.py

@@ -76,7 +76,7 @@ class CfnBudget(
 ):
     '''The ``AWS::Budgets::Budget`` resource allows customers to take pre-defined actions that will trigger once a budget threshold has been exceeded.
 
-    creates, replaces, or deletes budgets for Billing and Cost Management. For more information, see `Managing Your Costs with Budgets <https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/budgets-managing-costs.html>`_ in the *AWS Billing and Cost Management User Guide* .
+    creates, replaces, or deletes budgets for Billing and Cost Management. For more information, see `Managing Your Costs with Budgets <https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/budgets-managing-costs.html>`_ in the *Billing and Cost Management User Guide* .
 
     :see: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-budgets-budget.html
     :cloudformationResource: AWS::Budgets::Budget
@@ -405,7 +405,7 @@ class CfnBudget(
             :param cost_filters: The cost filters, such as ``Region`` , ``Service`` , ``LinkedAccount`` , ``Tag`` , or ``CostCategory`` , that are applied to a budget. AWS Budgets supports the following services as a ``Service`` filter for RI budgets: - Amazon EC2 - Amazon Redshift - Amazon Relational Database Service - Amazon ElastiCache - Amazon OpenSearch Service
             :param cost_types: The types of costs that are included in this ``COST`` budget. ``USAGE`` , ``RI_UTILIZATION`` , ``RI_COVERAGE`` , ``SAVINGS_PLANS_UTILIZATION`` , and ``SAVINGS_PLANS_COVERAGE`` budgets do not have ``CostTypes`` .
             :param planned_budget_limits: A map containing multiple ``BudgetLimit`` , including current or future limits. ``PlannedBudgetLimits`` is available for cost or usage budget and supports both monthly and quarterly ``TimeUnit`` . For monthly budgets, provide 12 months of ``PlannedBudgetLimits`` values. This must start from the current month and include the next 11 months. The ``key`` is the start of the month, ``UTC`` in epoch seconds. For quarterly budgets, provide four quarters of ``PlannedBudgetLimits`` value entries in standard calendar quarter increments. This must start from the current quarter and include the next three quarters. The ``key`` is the start of the quarter, ``UTC`` in epoch seconds. If the planned budget expires before 12 months for monthly or four quarters for quarterly, provide the ``PlannedBudgetLimits`` values only for the remaining periods. If the budget begins at a date in the future, provide ``PlannedBudgetLimits`` values from the start date of the budget. After all of the ``BudgetLimit`` values in ``PlannedBudgetLimits`` are used, the budget continues to use the last limit as the ``BudgetLimit`` . At that point, the planned budget provides the same experience as a fixed budget. ``DescribeBudget`` and ``DescribeBudgets`` response along with ``PlannedBudgetLimits`` also contain ``BudgetLimit`` representing the current month or quarter limit present in ``PlannedBudgetLimits`` . This only applies to budgets that are created with ``PlannedBudgetLimits`` . Budgets that are created without ``PlannedBudgetLimits`` only contain ``BudgetLimit`` . They don't contain ``PlannedBudgetLimits`` .
-            :param time_period: The period of time that is covered by a budget. The period has a start date and an end date. The start date must come before the end date. There are no restrictions on the end date. The start date for a budget. If you created your budget and didn't specify a start date, the start date defaults to the start of the chosen time period (MONTHLY, QUARTERLY, or ANNUALLY). For example, if you create your budget on January 24, 2019, choose ``MONTHLY`` , and don't set a start date, the start date defaults to ``01/01/19 00:00 UTC`` . The defaults are the same for the AWS Billing and Cost Management console and the API. You can change your start date with the ``UpdateBudget`` operation. After the end date, AWS deletes the budget and all associated notifications and subscribers.
+            :param time_period: The period of time that is covered by a budget. The period has a start date and an end date. The start date must come before the end date. There are no restrictions on the end date. The start date for a budget. If you created your budget and didn't specify a start date, the start date defaults to the start of the chosen time period (MONTHLY, QUARTERLY, or ANNUALLY). For example, if you create your budget on January 24, 2019, choose ``MONTHLY`` , and don't set a start date, the start date defaults to ``01/01/19 00:00 UTC`` . The defaults are the same for the Billing and Cost Management console and the API. You can change your start date with the ``UpdateBudget`` operation. After the end date, AWS deletes the budget and all associated notifications and subscribers.
 
             :see: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-budgets-budget-budgetdata.html
             :exampleMetadata: fixture=_generated
@@ -606,7 +606,7 @@ class CfnBudget(
 
             The period has a start date and an end date. The start date must come before the end date. There are no restrictions on the end date.
 
-            The start date for a budget. If you created your budget and didn't specify a start date, the start date defaults to the start of the chosen time period (MONTHLY, QUARTERLY, or ANNUALLY). For example, if you create your budget on January 24, 2019, choose ``MONTHLY`` , and don't set a start date, the start date defaults to ``01/01/19 00:00 UTC`` . The defaults are the same for the AWS Billing and Cost Management console and the API.
+            The start date for a budget. If you created your budget and didn't specify a start date, the start date defaults to the start of the chosen time period (MONTHLY, QUARTERLY, or ANNUALLY). For example, if you create your budget on January 24, 2019, choose ``MONTHLY`` , and don't set a start date, the start date defaults to ``01/01/19 00:00 UTC`` . The defaults are the same for the Billing and Cost Management console and the API.
 
             You can change your start date with the ``UpdateBudget`` operation.
 
@@ -1403,8 +1403,8 @@ class CfnBudget(
 
             The period has a start date and an end date. The start date must come before the end date. There are no restrictions on the end date.
 
-            :param end: The end date for a budget. If you didn't specify an end date, AWS set your end date to ``06/15/87 00:00 UTC`` . The defaults are the same for the AWS Billing and Cost Management console and the API. After the end date, AWS deletes the budget and all the associated notifications and subscribers. You can change your end date with the ``UpdateBudget`` operation.
-            :param start: The start date for a budget. If you created your budget and didn't specify a start date, the start date defaults to the start of the chosen time period (MONTHLY, QUARTERLY, or ANNUALLY). For example, if you create your budget on January 24, 2019, choose ``MONTHLY`` , and don't set a start date, the start date defaults to ``01/01/19 00:00 UTC`` . The defaults are the same for the AWS Billing and Cost Management console and the API. You can change your start date with the ``UpdateBudget`` operation. Valid values depend on the value of ``BudgetType`` : - If ``BudgetType`` is ``COST`` or ``USAGE`` : Valid values are ``MONTHLY`` , ``QUARTERLY`` , and ``ANNUALLY`` . - If ``BudgetType`` is ``RI_UTILIZATION`` or ``RI_COVERAGE`` : Valid values are ``DAILY`` , ``MONTHLY`` , ``QUARTERLY`` , and ``ANNUALLY`` .
+            :param end: The end date for a budget. If you didn't specify an end date, AWS set your end date to ``06/15/87 00:00 UTC`` . The defaults are the same for the Billing and Cost Management console and the API. After the end date, AWS deletes the budget and all the associated notifications and subscribers. You can change your end date with the ``UpdateBudget`` operation.
+            :param start: The start date for a budget. If you created your budget and didn't specify a start date, the start date defaults to the start of the chosen time period (MONTHLY, QUARTERLY, or ANNUALLY). For example, if you create your budget on January 24, 2019, choose ``MONTHLY`` , and don't set a start date, the start date defaults to ``01/01/19 00:00 UTC`` . The defaults are the same for the Billing and Cost Management console and the API. You can change your start date with the ``UpdateBudget`` operation. Valid values depend on the value of ``BudgetType`` : - If ``BudgetType`` is ``COST`` or ``USAGE`` : Valid values are ``MONTHLY`` , ``QUARTERLY`` , and ``ANNUALLY`` . - If ``BudgetType`` is ``RI_UTILIZATION`` or ``RI_COVERAGE`` : Valid values are ``DAILY`` , ``MONTHLY`` , ``QUARTERLY`` , and ``ANNUALLY`` .
 
             :see: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-budgets-budget-timeperiod.html
             :exampleMetadata: fixture=_generated
@@ -1434,7 +1434,7 @@ class CfnBudget(
         def end(self) -> typing.Optional[builtins.str]:
             '''The end date for a budget.
 
-            If you didn't specify an end date, AWS set your end date to ``06/15/87 00:00 UTC`` . The defaults are the same for the AWS Billing and Cost Management console and the API.
+            If you didn't specify an end date, AWS set your end date to ``06/15/87 00:00 UTC`` . The defaults are the same for the Billing and Cost Management console and the API.
 
             After the end date, AWS deletes the budget and all the associated notifications and subscribers. You can change your end date with the ``UpdateBudget`` operation.
 
@@ -1447,7 +1447,7 @@ class CfnBudget(
         def start(self) -> typing.Optional[builtins.str]:
             '''The start date for a budget.
 
-            If you created your budget and didn't specify a start date, the start date defaults to the start of the chosen time period (MONTHLY, QUARTERLY, or ANNUALLY). For example, if you create your budget on January 24, 2019, choose ``MONTHLY`` , and don't set a start date, the start date defaults to ``01/01/19 00:00 UTC`` . The defaults are the same for the AWS Billing and Cost Management console and the API.
+            If you created your budget and didn't specify a start date, the start date defaults to the start of the chosen time period (MONTHLY, QUARTERLY, or ANNUALLY). For example, if you create your budget on January 24, 2019, choose ``MONTHLY`` , and don't set a start date, the start date defaults to ``01/01/19 00:00 UTC`` . The defaults are the same for the Billing and Cost Management console and the API.
 
             You can change your start date with the ``UpdateBudget`` operation.
 
@@ -1642,7 +1642,7 @@ class CfnBudgetsAction(
 ):
     '''The ``AWS::Budgets::BudgetsAction`` resource enables you to take predefined actions that are initiated when a budget threshold has been exceeded.
 
-    For more information, see `Managing Your Costs with Budgets <https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/budgets-managing-costs.html>`_ in the *AWS Billing and Cost Management User Guide* .
+    For more information, see `Managing Your Costs with Budgets <https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/budgets-managing-costs.html>`_ in the *Billing and Cost Management User Guide* .
 
     :see: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-budgets-budgetsaction.html
     :cloudformationResource: AWS::Budgets::BudgetsAction

aws_cdk/aws_cassandra/__init__.py

@@ -263,7 +263,7 @@ class CfnKeyspace(
 
             For more information about multi-Region replication, see `Multi-Region replication <https://docs.aws.amazon.com/keyspaces/latest/devguide/multiRegion-replication.html>`_ in the *Amazon Keyspaces Developer Guide* .
 
-            :param region_list: Specifies the AWS Regions that the keyspace is replicated in. You must specify at least two Regions, including the Region that the keyspace is being created in.
+            :param region_list: Specifies the AWS Regions that the keyspace is replicated in. You must specify at least two Regions, including the Region that the keyspace is being created in. To specify a Region `that's disabled by default <https://docs.aws.amazon.com/accounts/latest/reference/manage-acct-regions.html#rande-manage-enable>`_ , you must first enable the Region. For more information, see `Multi-Region replication in AWS Regions disabled by default <https://docs.aws.amazon.com/keyspaces/latest/devguide/multiRegion-replication_how-it-works.html#howitworks_mrr_opt_in>`_ in the *Amazon Keyspaces Developer Guide* .
             :param replication_strategy: The options are:. - ``SINGLE_REGION`` (optional) - ``MULTI_REGION`` If no value is specified, the default is ``SINGLE_REGION`` . If ``MULTI_REGION`` is specified, ``RegionList`` is required.
 
             :see: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-cassandra-keyspace-replicationspecification.html
@@ -296,6 +296,8 @@ class CfnKeyspace(
 
             You must specify at least two Regions, including the Region that the keyspace is being created in.
 
+            To specify a Region `that's disabled by default <https://docs.aws.amazon.com/accounts/latest/reference/manage-acct-regions.html#rande-manage-enable>`_ , you must first enable the Region. For more information, see `Multi-Region replication in AWS Regions disabled by default <https://docs.aws.amazon.com/keyspaces/latest/devguide/multiRegion-replication_how-it-works.html#howitworks_mrr_opt_in>`_ in the *Amazon Keyspaces Developer Guide* .
+
             :see: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-cassandra-keyspace-replicationspecification.html#cfn-cassandra-keyspace-replicationspecification-regionlist
             '''
             result = self._values.get("region_list")

aws_cdk/aws_ce/__init__.py

@@ -1076,9 +1076,9 @@ class CfnCostCategory(
     metaclass=jsii.JSIIMeta,
     jsii_type="aws-cdk-lib.aws_ce.CfnCostCategory",
 ):
-    '''The ``AWS::CE::CostCategory`` resource creates groupings of cost that you can use across products in the AWS Billing and Cost Management console, such as Cost Explorer and AWS Budgets.
+    '''The ``AWS::CE::CostCategory`` resource creates groupings of cost that you can use across products in the Billing and Cost Management console, such as Cost Explorer and AWS Budgets.
 
-    For more information, see `Managing Your Costs with Cost Categories <https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/manage-cost-categories.html>`_ in the *AWS Billing and Cost Management User Guide* .
+    For more information, see `Managing Your Costs with Cost Categories <https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/manage-cost-categories.html>`_ in the *Billing and Cost Management User Guide* .
 
     :see: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ce-costcategory.html
     :cloudformationResource: AWS::CE::CostCategory

aws_cdk/aws_cloudformation/__init__.py

@@ -5460,7 +5460,7 @@ class CfnStack(
     You must acknowledge IAM capabilities for nested stacks that contain IAM resources. Also, verify that you have cancel update stack permissions, which is required if an update rolls back. For more information about IAM and CloudFormation , see `Controlling access with AWS Identity and Access Management <https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/control-access-with-iam.html>`_ in the *AWS CloudFormation User Guide* .
     .. epigraph::
 
-       A subset of ``AWS::CloudFormation::Stack`` resource type properties listed below are available to customers using CloudFormation , AWS CDK , and AWS Cloud Control API to configure.
+       A subset of ``AWS::CloudFormation::Stack`` resource type properties listed below are available to customers using CloudFormation , AWS CDK , and Cloud Control  to configure.
 
        - ``NotificationARNs``
        - ``Parameters``
@@ -5468,7 +5468,7 @@ class CfnStack(
        - ``TemplateURL``
        - ``TimeoutInMinutes``
 
-       These properties can be configured only when using AWS Cloud Control API . This is because the below properties are set by the parent stack, and thus cannot be configured using CloudFormation or AWS CDK but only AWS Cloud Control API .
+       These properties can be configured only when using Cloud Control  . This is because the below properties are set by the parent stack, and thus cannot be configured using CloudFormation or AWS CDK but only Cloud Control  .
 
        - ``Capabilities``
        - ``Description``
@@ -5483,7 +5483,7 @@ class CfnStack(
 
        Customers that configure ``AWS::CloudFormation::Stack`` using CloudFormation and AWS CDK can do so for nesting a CloudFormation stack as a resource in their top-level template.
 
-       These read-only properties can be accessed only when using AWS Cloud Control API .
+       These read-only properties can be accessed only when using Cloud Control  .
 
        - ``ChangeSetId``
        - ``CreationTime``

aws_cdk/aws_codebuild/__init__.py

@@ -3470,6 +3470,7 @@ class CfnProject(
                 type="type",
         
                 # the properties below are optional
+                cache_namespace="cacheNamespace",
                 location="location",
                 modes=["modes"]
             ),
@@ -5276,19 +5277,26 @@ class CfnProject(
     @jsii.data_type(
         jsii_type="aws-cdk-lib.aws_codebuild.CfnProject.ProjectCacheProperty",
         jsii_struct_bases=[],
-        name_mapping={"type": "type", "location": "location", "modes": "modes"},
+        name_mapping={
+            "type": "type",
+            "cache_namespace": "cacheNamespace",
+            "location": "location",
+            "modes": "modes",
+        },
     )
     class ProjectCacheProperty:
         def __init__(
             self,
             *,
             type: builtins.str,
+            cache_namespace: typing.Optional[builtins.str] = None,
             location: typing.Optional[builtins.str] = None,
             modes: typing.Optional[typing.Sequence[builtins.str]] = None,
         ) -> None:
             '''``ProjectCache`` is a property of the `AWS CodeBuild Project <https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-codebuild-project.html>`_ resource that specifies information about the cache for the build project. If ``ProjectCache`` is not specified, then both of its properties default to ``NO_CACHE`` .
 
             :param type: The type of cache used by the build project. Valid values include:. - ``NO_CACHE`` : The build project does not use any cache. - ``S3`` : The build project reads and writes from and to S3. - ``LOCAL`` : The build project stores a cache locally on a build host that is only available to that build host.
+            :param cache_namespace: 
             :param location: Information about the cache location:. - ``NO_CACHE`` or ``LOCAL`` : This value is ignored. - ``S3`` : This is the S3 bucket name/prefix.
             :param modes: An array of strings that specify the local cache modes. You can use one or more local cache modes at the same time. This is only used for ``LOCAL`` cache types. Possible values are: - **LOCAL_SOURCE_CACHE** - Caches Git metadata for primary and secondary sources. After the cache is created, subsequent builds pull only the change between commits. This mode is a good choice for projects with a clean working directory and a source that is a large Git repository. If you choose this option and your project does not use a Git repository (GitHub, GitHub Enterprise, or Bitbucket), the option is ignored. - **LOCAL_DOCKER_LAYER_CACHE** - Caches existing Docker layers. This mode is a good choice for projects that build or pull large Docker images. It can prevent the performance issues caused by pulling large Docker images down from the network. .. epigraph:: - You can use a Docker layer cache in the Linux environment only. - The ``privileged`` flag must be set so that your project has the required Docker permissions. - You should consider the security implications before you use a Docker layer cache. - **LOCAL_CUSTOM_CACHE** - Caches directories you specify in the buildspec file. This mode is a good choice if your build scenario is not suited to one of the other three local cache modes. If you use a custom cache: - Only directories can be specified for caching. You cannot specify individual files. - Symlinks are used to reference cached directories. - Cached directories are linked to your build before it downloads its project sources. Cached items are overridden if a source item has the same name. Directories are specified using cache paths in the buildspec file.
 
@@ -5305,6 +5313,7 @@ class CfnProject(
                     type="type",
                 
                     # the properties below are optional
+                    cache_namespace="cacheNamespace",
                     location="location",
                     modes=["modes"]
                 )
@@ -5312,11 +5321,14 @@ class CfnProject(
             if __debug__:
                 type_hints = typing.get_type_hints(_typecheckingstub__1f7b942816ca448d0a1e5b046754abe3bbf6042e79982a46edfd284c87941f59)
                 check_type(argname="argument type", value=type, expected_type=type_hints["type"])
+                check_type(argname="argument cache_namespace", value=cache_namespace, expected_type=type_hints["cache_namespace"])
                 check_type(argname="argument location", value=location, expected_type=type_hints["location"])
                 check_type(argname="argument modes", value=modes, expected_type=type_hints["modes"])
             self._values: typing.Dict[builtins.str, typing.Any] = {
                 "type": type,
             }
+            if cache_namespace is not None:
+                self._values["cache_namespace"] = cache_namespace
             if location is not None:
                 self._values["location"] = location
             if modes is not None:
@@ -5336,6 +5348,14 @@ class CfnProject(
             assert result is not None, "Required property 'type' is missing"
             return typing.cast(builtins.str, result)
 
+        @builtins.property
+        def cache_namespace(self) -> typing.Optional[builtins.str]:
+            '''
+            :see: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-codebuild-project-projectcache.html#cfn-codebuild-project-projectcache-cachenamespace
+            '''
+            result = self._values.get("cache_namespace")
+            return typing.cast(typing.Optional[builtins.str], result)
+
         @builtins.property
         def location(self) -> typing.Optional[builtins.str]:
             '''Information about the cache location:.
@@ -6812,6 +6832,7 @@ class CfnProjectProps:
                     type="type",
             
                     # the properties below are optional
+                    cache_namespace="cacheNamespace",
                     location="location",
                     modes=["modes"]
                 ),
@@ -19082,6 +19103,7 @@ def _typecheckingstub__bd7a159b208cebb3cbebac16a64724eaec87e10d0a867f62bf9021489
 def _typecheckingstub__1f7b942816ca448d0a1e5b046754abe3bbf6042e79982a46edfd284c87941f59(
     *,
     type: builtins.str,
+    cache_namespace: typing.Optional[builtins.str] = None,
     location: typing.Optional[builtins.str] = None,
     modes: typing.Optional[typing.Sequence[builtins.str]] = None,
 ) -> None:

aws_cdk/aws_codepipeline/__init__.py

@@ -818,13 +818,11 @@ codepipeline.Pipeline(self, "Pipeline",
 
 Conditions are used for specific types of expressions and each has specific options for results available as follows:
 
-```
 Entry - The conditions for making checks that, if met, allow entry to a stage. Rules are engaged with the following result options: Fail or Skip
 
 On Failure - The conditions for making checks for the stage when it fails. Rules are engaged with the following result option: Rollback
 
 On Success - The conditions for making checks for the stage when it succeeds. Rules are engaged with the following result options: Rollback or Fail
-```
 
 Conditions are supported by a set of rules for each type of condition.
 
@@ -894,6 +892,10 @@ codepipeline.Pipeline(self, "Pipeline",
 )
 ```
 
+## Use pipeline service role as default action role in pipeline
+
+You could enable this field to use pipeline service role as default action role in Codepipeline by set `usePipelineServiceRoleForActions` as true if no action role provided.
+
 ## Migrating a pipeline type from V1 to V2
 
 To migrate your pipeline type from V1 to V2, you just need to update the `pipelineType` property to `PipelineType.V2`.
@@ -1540,39 +1542,32 @@ class Artifact(
 
     Example::
 
-        # later:
-        # project: codebuild.PipelineProject
-        lambda_invoke_action = codepipeline_actions.LambdaInvokeAction(
-            action_name="Lambda",
-            lambda_=lambda_.Function(self, "Func",
-                runtime=lambda_.Runtime.NODEJS_LATEST,
-                handler="index.handler",
-                code=lambda_.Code.from_inline("""
-                            const { CodePipeline } = require('@aws-sdk/client-codepipeline');
+        # pipeline: codepipeline.Pipeline
+        
         
-                            exports.handler = async function(event, context) {
-                                const codepipeline = new AWS.CodePipeline();
-                                await codepipeline.putJobSuccessResult({
-                                    jobId: event['CodePipeline.job'].id,
-                                    outputVariables: {
-                                        MY_VAR: "some value",
-                                    },
-                                });
-                            }
-                        """)
-            ),
-            variables_namespace="MyNamespace"
-        )
         source_output = codepipeline.Artifact()
-        codepipeline_actions.CodeBuildAction(
-            action_name="CodeBuild",
-            project=project,
+        source_action = codepipeline_actions.CodeStarConnectionsSourceAction(
+            action_name="CodeStarConnectionsSourceAction",
+            output=source_output,
+            connection_arn="your-connection-arn",
+            owner="your-owner",
+            repo="your-repo"
+        )
+        
+        scan_output = codepipeline.Artifact()
+        scan_action = codepipeline_actions.InspectorSourceCodeScanAction(
+            action_name="InspectorSourceCodeScanAction",
             input=source_output,
-            environment_variables={
-                "MyVar": codebuild.BuildEnvironmentVariable(
-                    value=lambda_invoke_action.variable("MY_VAR")
-                )
-            }
+            output=scan_output
+        )
+        
+        pipeline.add_stage(
+            stage_name="Source",
+            actions=[source_action]
+        )
+        pipeline.add_stage(
+            stage_name="Scan",
+            actions=[scan_action]
         )
     '''
 
@@ -9307,6 +9302,7 @@ class Pipeline(
         role: typing.Optional[_IRole_235f5d8e] = None,
         stages: typing.Optional[typing.Sequence[typing.Union["StageProps", typing.Dict[builtins.str, typing.Any]]]] = None,
         triggers: typing.Optional[typing.Sequence[typing.Union["TriggerProps", typing.Dict[builtins.str, typing.Any]]]] = None,
+        use_pipeline_role_for_actions: typing.Optional[builtins.bool] = None,
         variables: typing.Optional[typing.Sequence["Variable"]] = None,
     ) -> None:
         '''
@@ -9324,6 +9320,7 @@ class Pipeline(
         :param role: The IAM role to be assumed by this Pipeline. Default: a new IAM role will be created.
         :param stages: The list of Stages, in order, to create this Pipeline with. You can always add more Stages later by calling ``Pipeline#addStage``. Default: - None.
         :param triggers: The trigger configuration specifying a type of event, such as Git tags, that starts the pipeline. When a trigger configuration is specified, default change detection for repository and branch commits is disabled. ``triggers`` can only be used when ``pipelineType`` is set to ``PipelineType.V2``. You can always add more triggers later by calling ``Pipeline#addTrigger``. Default: - No triggers
+        :param use_pipeline_role_for_actions: Use pipeline service role for actions if no action role configured. Default: - false
         :param variables: A list that defines the pipeline variables for a pipeline resource. ``variables`` can only be used when ``pipelineType`` is set to ``PipelineType.V2``. You can always add more variables later by calling ``Pipeline#addVariable``. Default: - No variables
         '''
         if __debug__:
@@ -9343,6 +9340,7 @@ class Pipeline(
             role=role,
             stages=stages,
             triggers=triggers,
+            use_pipeline_role_for_actions=use_pipeline_role_for_actions,
             variables=variables,
         )
 
@@ -9970,6 +9968,7 @@ class PipelineNotifyOnOptions(_NotificationRuleOptions_dff73281):
         "role": "role",
         "stages": "stages",
         "triggers": "triggers",
+        "use_pipeline_role_for_actions": "usePipelineRoleForActions",
         "variables": "variables",
     },
 )
@@ -9989,6 +9988,7 @@ class PipelineProps:
         role: typing.Optional[_IRole_235f5d8e] = None,
         stages: typing.Optional[typing.Sequence[typing.Union["StageProps", typing.Dict[builtins.str, typing.Any]]]] = None,
         triggers: typing.Optional[typing.Sequence[typing.Union["TriggerProps", typing.Dict[builtins.str, typing.Any]]]] = None,
+        use_pipeline_role_for_actions: typing.Optional[builtins.bool] = None,
         variables: typing.Optional[typing.Sequence["Variable"]] = None,
     ) -> None:
         '''
@@ -10004,6 +10004,7 @@ class PipelineProps:
         :param role: The IAM role to be assumed by this Pipeline. Default: a new IAM role will be created.
         :param stages: The list of Stages, in order, to create this Pipeline with. You can always add more Stages later by calling ``Pipeline#addStage``. Default: - None.
         :param triggers: The trigger configuration specifying a type of event, such as Git tags, that starts the pipeline. When a trigger configuration is specified, default change detection for repository and branch commits is disabled. ``triggers`` can only be used when ``pipelineType`` is set to ``PipelineType.V2``. You can always add more triggers later by calling ``Pipeline#addTrigger``. Default: - No triggers
+        :param use_pipeline_role_for_actions: Use pipeline service role for actions if no action role configured. Default: - false
         :param variables: A list that defines the pipeline variables for a pipeline resource. ``variables`` can only be used when ``pipelineType`` is set to ``PipelineType.V2``. You can always add more variables later by calling ``Pipeline#addVariable``. Default: - No variables
 
         :exampleMetadata: infused
@@ -10057,6 +10058,7 @@ class PipelineProps:
             check_type(argname="argument role", value=role, expected_type=type_hints["role"])
             check_type(argname="argument stages", value=stages, expected_type=type_hints["stages"])
             check_type(argname="argument triggers", value=triggers, expected_type=type_hints["triggers"])
+            check_type(argname="argument use_pipeline_role_for_actions", value=use_pipeline_role_for_actions, expected_type=type_hints["use_pipeline_role_for_actions"])
             check_type(argname="argument variables", value=variables, expected_type=type_hints["variables"])
         self._values: typing.Dict[builtins.str, typing.Any] = {}
         if artifact_bucket is not None:
@@ -10083,6 +10085,8 @@ class PipelineProps:
             self._values["stages"] = stages
         if triggers is not None:
             self._values["triggers"] = triggers
+        if use_pipeline_role_for_actions is not None:
+            self._values["use_pipeline_role_for_actions"] = use_pipeline_role_for_actions
         if variables is not None:
             self._values["variables"] = variables
 
@@ -10229,6 +10233,15 @@ class PipelineProps:
         result = self._values.get("triggers")
         return typing.cast(typing.Optional[typing.List["TriggerProps"]], result)
 
+    @builtins.property
+    def use_pipeline_role_for_actions(self) -> typing.Optional[builtins.bool]:
+        '''Use pipeline service role for actions if no action role configured.
+
+        :default: - false
+        '''
+        result = self._values.get("use_pipeline_role_for_actions")
+        return typing.cast(typing.Optional[builtins.bool], result)
+
     @builtins.property
     def variables(self) -> typing.Optional[typing.List["Variable"]]:
         '''A list that defines the pipeline variables for a pipeline resource.
@@ -12729,6 +12742,7 @@ def _typecheckingstub__dccc82ea9bcac61a3fb8c34055734a04a1bee7f59ee6675fdade2d8b5
     role: typing.Optional[_IRole_235f5d8e] = None,
     stages: typing.Optional[typing.Sequence[typing.Union[StageProps, typing.Dict[builtins.str, typing.Any]]]] = None,
     triggers: typing.Optional[typing.Sequence[typing.Union[TriggerProps, typing.Dict[builtins.str, typing.Any]]]] = None,
+    use_pipeline_role_for_actions: typing.Optional[builtins.bool] = None,
     variables: typing.Optional[typing.Sequence[Variable]] = None,
 ) -> None:
     """Type checking stubs"""
@@ -12876,6 +12890,7 @@ def _typecheckingstub__22f00fc379808105702c3f59369205afd36025a51e45bcaf5d1cec0a3
     role: typing.Optional[_IRole_235f5d8e] = None,
     stages: typing.Optional[typing.Sequence[typing.Union[StageProps, typing.Dict[builtins.str, typing.Any]]]] = None,
     triggers: typing.Optional[typing.Sequence[typing.Union[TriggerProps, typing.Dict[builtins.str, typing.Any]]]] = None,
+    use_pipeline_role_for_actions: typing.Optional[builtins.bool] = None,
     variables: typing.Optional[typing.Sequence[Variable]] = None,
 ) -> None:
     """Type checking stubs"""