@aws-cdk/app-staging-synthesizer-alpha 2.84.0-alpha.0 → 2.86.0-alpha.0

package/.jsii

@@ -8,7 +8,7 @@
     "url": "https://aws.amazon.com"
   },
   "dependencies": {
-    "aws-cdk-lib": "2.84.0",
+    "aws-cdk-lib": "2.86.0",
     "constructs": "^10.0.0"
   },
   "dependencyClosure": {
@@ -547,6 +547,19 @@
             }
           }
         },
+        "aws-cdk-lib.aws_cleanrooms": {
+          "targets": {
+            "dotnet": {
+              "package": "Amazon.CDK.AWS.CleanRooms"
+            },
+            "java": {
+              "package": "services.cleanrooms"
+            },
+            "python": {
+              "module": "aws_cdk.aws_cleanrooms"
+            }
+          }
+        },
         "aws-cdk-lib.aws_cloud9": {
           "targets": {
             "dotnet": {
@@ -3466,7 +3479,7 @@
     "stability": "experimental"
   },
   "homepage": "https://github.com/aws/aws-cdk",
-  "jsiiVersion": "5.0.8 (build b97c75a)",
+  "jsiiVersion": "5.0.11 (build 5e2d6be)",
   "keywords": [
     "aws",
     "cdk"
@@ -3485,7 +3498,7 @@
   },
   "name": "@aws-cdk/app-staging-synthesizer-alpha",
   "readme": {
-    "markdown": "# App Staging Synthesizer\n<!--BEGIN STABILITY BANNER-->\n\n---\n\n![cdk-constructs: Experimental](https://img.shields.io/badge/cdk--constructs-experimental-important.svg?style=for-the-badge)\n\n> The APIs of higher level constructs in this module are experimental and under active development.\n> They are subject to non-backward compatible changes or removal in any future version. These are\n> not subject to the [Semantic Versioning](https://semver.org/) model and breaking changes will be\n> announced in the release notes. This means that while you may use them, you may need to update\n> your source code when upgrading to a newer version of this package.\n\n---\n\n<!--END STABILITY BANNER-->\n\nThis library includes constructs aimed at replacing the current model of bootstrapping and providing\ngreater control of the bootstrap experience to the CDK user. The important constructs in this library\nare as follows:\n\n- the `IStagingResources` interface: a framework for an app-level bootstrap stack that handles\n  file assets and docker assets.\n- the `DefaultStagingStack`, which is a works-out-of-the-box implementation of the `IStagingResources`\n  interface.\n- the `AppStagingSynthesizer`, a new CDK synthesizer that will synthesize CDK applications with\n  the staging resources provided.\n\n> As this library is `experimental`, there are features that are not yet implemented. Please look\n> at the list of [Known Limitations](#known-limitations) before getting started.\n\nTo get started, update your CDK App with a new `defaultStackSynthesizer`:\n\n```ts\nconst app = new App({\n  defaultStackSynthesizer: AppStagingSynthesizer.defaultResources({\n    appId: 'my-app-id', // put a unique id here\n  }),\n});\n```\n\nThis will introduce a `DefaultStagingStack` in your CDK App and staging assets of your App\nwill live in the resources from that stack rather than the CDK Bootstrap stack.\n\nIf you are migrating from a different version of synthesis your updated CDK App will target\nthe resources in the `DefaultStagingStack` and no longer be tied to the bootstrapped resources\nin your account.\n\n## Bootstrap Model\n\nOur current bootstrap model looks like this, when you run `cdk bootstrap aws://<account>/<region>` :\n\n```text\n┌───────────────────────────────────┐┌────────────────────────┐┌────────────────────────┐\n│                                   ││                        ││                        │\n│                                   ││                        ││                        │\n│          ┌───────────────┐        ││    ┌──────────────┐    ││    ┌──────────────┐    │\n│          │Bootstrap Stack│        ││    │  CDK App 1   │    ││    │  CDK App 2   │    │\n│          └───────────────┘        ││    └──────────────┘    ││    └──────────────┘    │\n│                                   ││                        ││                        │\n│                                   ││                        ││                        │\n│   ┌───────────────────────────┐   ││     ┌────────────┐     ││                        │\n│   │IAM Role for CFN execution │   ││┌────│  S3 Asset  │     ││                        │\n│   │    IAM Role for lookup    │   │││    └────────────┘     ││                        │\n│   │  IAM Role for deployment  │   │││                       ││                        │\n│   └───────────────────────────┘   │││                       ││     ┌─────────────┐    │\n│                                   │││            ┌──────────┼┼─────│  S3 Asset   │    │\n│                                   │││            │          ││     └─────────────┘    │\n│ ┌───────────────────────────────┐ │││            │          ││                        │\n│ │ IAM Role for File Publishing  │ │││            │          ││                        │\n│ │ IAM Role for Image Publishing │ │││            │          ││                        │\n│ └───────────────────────────────┘ │││            │          ││                        │\n│                                   │││            │          ││                        │\n│  ┌─────────────────────────────┐  │││            │          ││                        │\n│  │S3 Bucket for Staging Assets │  │││            │          ││                        │\n│  │     KMS Key encryption      │◀─┼┼┴────────────┘          ││      ┌────────────┐    │\n│  └─────────────────────────────┘  ││             ┌──────────┼┼───── │ ECR Asset  │    │\n│                                   ││             │          ││      └────────────┘    │\n│                                   ││             │          ││                        │\n│┌─────────────────────────────────┐││             │          ││                        │\n││ECR Repository for Staging Assets◀┼┼─────────────┘          ││                        │\n│└─────────────────────────────────┘││                        ││                        │\n│                                   ││                        ││                        │\n│                                   ││                        ││                        │\n│                                   ││                        ││                        │\n│                                   ││                        ││                        │\n│                                   ││                        ││                        │\n│                                   ││                        ││                        │\n└───────────────────────────────────┘└────────────────────────┘└────────────────────────┘\n```\n\nYour CDK Application utilizes these resources when deploying. For example, if you have a file asset,\nit gets uploaded to the S3 Staging Bucket using the File Publishing Role when you run `cdk deploy`.\n\nThis library introduces an alternate model to bootstrapping, by splitting out essential CloudFormation IAM roles\nand staging resources. There will still be a Bootstrap Stack, but this will only contain IAM roles necessary for\nCloudFormation deployment. Each CDK App will instead be in charge of its own staging resources, including the\nS3 Bucket, ECR Repositories, and associated IAM roles. It works like this:\n\nThe Staging Stack will contain, on a per-need basis,\n\n- 1 S3 Bucket with KMS encryption for all file assets in the CDK App.\n- An ECR Repository _per_ image (and its revisions).\n- IAM roles with access to the Bucket and Repositories.\n\n```text\n┌─────────────────────────────┐┌───────────────────────────────────────┐┌───────────────────────────────────────┐\n│                             ││                                       ││                                       │\n│      ┌───────────────┐      ││             ┌──────────────┐          ││             ┌──────────────┐          │\n│      │Bootstrap Stack│      ││             │  CDK App 1   │          ││             │  CDK App 2   │          │\n│      └───────────────┘      ││             └──────────────┘          ││             └──────────────┘          │\n│                             ││┌──────────────────┐                   ││┌──────────────────┐                   │\n│                             │││ ┌──────────────┐ │                   │││ ┌──────────────┐ │                   │\n│                             │││ │Staging Stack │ │                   │││ │Staging Stack │ │                   │\n│                             │││ └──────────────┘ │                   │││ └──────────────┘ │                   │\n│                             │││                  │                   │││                  │                   │\n│                             │││                  │                   │││                  │                   │\n│                             │││┌────────────────┐│     ┌────────────┐│││┌────────────────┐│     ┌────────────┐│\n│                             ││││  IAM Role for  ││ ┌───│  S3 Asset  │││││  IAM Role for  ││ ┌───│  S3 Asset  ││\n│                             ││││File Publishing ││ │   └────────────┘││││File Publishing ││ │   └────────────┘│\n│                             │││└────────────────┘│ │                 ││││  IAM Role for  ││ │                 │\n│                             │││                  │ │                 ││││Image Publishing││ │                 │\n│┌───────────────────────────┐│││                  │ │                 │││└────────────────┘│ │                 │\n││IAM Role for CFN execution ││││                  │ │                 │││                  │ │                 │\n││    IAM Role for lookup    ││││                  │ │                 │││                  │ │                 │\n││  IAM Role for deployment  ││││┌────────────────┐│ │                 │││┌────────────────┐│ │                 │\n│└───────────────────────────┘││││ S3 Bucket for  ││ │                 ││││ S3 Bucket for  ││ │                 │\n│                             ││││ Staging Assets │◀─┘                 ││││ Staging Assets │◀─┘                 │\n│                             │││└────────────────┘│                   │││└────────────────┘│      ┌───────────┐│\n│                             │││                  │                   │││                  │  ┌───│ ECR Asset ││\n│                             │││                  │                   │││┌────────────────┐│  │   └───────────┘│\n│                             │││                  │                   ││││ ECR Repository ││  │                │\n│                             │││                  │                   ││││  for Staging   │◀──┘                │\n│                             │││                  │                   ││││     Assets     ││                   │\n│                             │││                  │                   │││└────────────────┘│                   │\n│                             │││                  │                   │││                  │                   │\n│                             │││                  │                   │││                  │                   │\n│                             │││                  │                   │││                  │                   │\n│                             │││                  │                   │││                  │                   │\n│                             │││                  │                   │││                  │                   │\n│                             ││└──────────────────┘                   ││└──────────────────┘                   │\n└─────────────────────────────┘└───────────────────────────────────────┘└───────────────────────────────────────┘\n```\n\nThis allows staging resources to be created when needed next to the CDK App. It has the following\nbenefits:\n\n- Resources between separate CDK Apps are separated so they can be cleaned up and lifecycle\ncontrolled individually.\n- Users have a familiar way to customize staging resources in the CDK Application.\n\n## Using the Default Staging Stack per Environment\n\nThe most common use case will be to use the built-in default resources. In this scenario, the\nsynthesizer will create a new Staging Stack in each environment the CDK App is deployed to store\nits staging resources. To use this kind of synthesizer, use `AppStagingSynthesizer.defaultResources()`.\n\n```ts\nconst app = new App({\n  defaultStackSynthesizer: AppStagingSynthesizer.defaultResources({\n    appId: 'my-app-id',\n  }),\n});\n```\n\nEvery CDK App that uses the `DefaultStagingStack` must include an `appId`. This should\nbe an identifier unique to the app and is used to differentiate staging resources associated\nwith the app.\n\n### Default Staging Stack\n\nThe Default Staging Stack includes all the staging resources necessary for CDK Assets. The below example\nis of a CDK App using the `AppStagingSynthesizer` and creating a file asset for the Lambda Function\nsource code. As part of the `DefaultStagingStack`, an S3 bucket and IAM role will be created that will be\nused to upload the asset to S3.\n\n```ts\nconst app = new App({\n  defaultStackSynthesizer: AppStagingSynthesizer.defaultResources({ appId: 'my-app-id' }),\n});\n\nconst stack = new Stack(app, 'my-stack');\n\nnew lambda.Function(stack, 'lambda', {\n  code: lambda.AssetCode.fromAsset(path.join(__dirname, 'assets')),\n  handler: 'index.handler',\n  runtime: lambda.Runtime.PYTHON_3_9,\n});\n\napp.synth();\n```\n\n### Custom Roles\n\nYou can customize some or all of the roles you'd like to use in the synthesizer as well,\nif all you need is to supply custom roles (and not change anything else in the `DefaultStagingStack`):\n\n```ts\nconst app = new App({\n  defaultStackSynthesizer: AppStagingSynthesizer.defaultResources({\n    appId: 'my-app-id',\n    deploymentIdentities: DeploymentIdentities.specifyRoles({\n      cloudFormationExecutionRole: BootstrapRole.fromRoleArn('arn:aws:iam::123456789012:role/Execute'),\n      deploymentRole: BootstrapRole.fromRoleArn('arn:aws:iam::123456789012:role/Deploy'),\n      lookupRole: BootstrapRole.fromRoleArn('arn:aws:iam::123456789012:role/Lookup'),\n    }),\n  }),\n});\n```\n\nOr, you can ask to use the CLI credentials that exist at deploy-time.\nThese credentials must have the ability to perform CloudFormation calls,\nlookup resources in your account, and perform CloudFormation deployment.\nFor a full list of what is necessary, see `LookupRole`, `DeploymentActionRole`,\nand `CloudFormationExecutionRole` in the\n[bootstrap template](https://github.com/aws/aws-cdk/blob/main/packages/aws-cdk/lib/api/bootstrap/bootstrap-template.yaml).\n\n```ts\nconst app = new App({\n  defaultStackSynthesizer: AppStagingSynthesizer.defaultResources({\n    appId: 'my-app-id',\n    deploymentIdentities: DeploymentIdentities.cliCredentials(),\n  }),\n});\n```\n\nThe default staging stack will create roles to publish to the S3 bucket and ECR repositories,\nassumable by the deployment role. You can also specify an existing IAM role for the\n`fileAssetPublishingRole` or `imageAssetPublishingRole`:\n\n```ts\nconst app = new App({\n  defaultStackSynthesizer: AppStagingSynthesizer.defaultResources({\n    appId: 'my-app-id',\n    fileAssetPublishingRole: BootstrapRole.fromRoleArn('arn:aws:iam::123456789012:role/S3Access'),\n    imageAssetPublishingRole: BootstrapRole.fromRoleArn('arn:aws:iam::123456789012:role/ECRAccess'),\n  }),\n});\n```\n\n### Deploy Time S3 Assets\n\nThere are two types of assets:\n\n- Assets used only during deployment. These are used to hand off a large piece of data to another\nservice, that will make a private copy of that data. After deployment, the asset is only necessary for\na potential future rollback.\n- Assets accessed throughout the running life time of the application.\n\nExamples of assets that are only used at deploy time are CloudFormation Templates and Lambda Code\nbundles. Examples of assets accessed throughout the life time of the application are script files\ndownloaded to run in a CodeBuild Project, or on EC2 instance startup. ECR images are always application\nlife-time assets. S3 deploy time assets are stored with a `deploy-time/` prefix, and a lifecycle rule will collect them after a configurable number of days.\n\nLambda assets are by default marked as deploy time assets:\n\n```ts\ndeclare const stack: Stack;\nnew lambda.Function(stack, 'lambda', {\n  code: lambda.AssetCode.fromAsset(path.join(__dirname, 'assets')), // lambda marks deployTime = true\n  handler: 'index.handler',\n  runtime: lambda.Runtime.PYTHON_3_9,\n});\n```\n\nOr, if you want to create your own deploy time asset:\n\n```ts\nimport { Asset } from 'aws-cdk-lib/aws-s3-assets';\n\ndeclare const stack: Stack;\nconst asset = new Asset(stack, 'deploy-time-asset', {\n  deployTime: true,\n  path: path.join(__dirname, './deploy-time-asset'),\n});\n```\n\nBy default, we store deploy time assets for 30 days, but you can change this number by specifying\n`deployTimeFileAssetLifetime`. The number you specify here is how long you will be able to roll back\nto a previous version of an application just by doing a CloudFormation deployment with the old\ntemplate, without rebuilding and republishing assets.\n\n```ts\nconst app = new App({\n  defaultStackSynthesizer: AppStagingSynthesizer.defaultResources({\n    appId: 'my-app-id',\n    deployTimeFileAssetLifetime: Duration.days(100),\n  }),\n});\n```\n\n### Lifecycle Rules on ECR Repositories\n\nBy default, we store a maximum of 3 revisions of a particular docker image asset. This allows\nfor smooth faciliation of rollback scenarios where we may reference previous versions of an\nimage. When more than 3 revisions of an asset exist in the ECR repository, the oldest one is\npurged.\n\nTo change the number of revisions stored, use `imageAssetVersionCount`:\n\n```ts\nconst app = new App({\n  defaultStackSynthesizer: AppStagingSynthesizer.defaultResources({\n    appId: 'my-app-id',\n    imageAssetVersionCount: 10,\n  }),\n});\n```\n\n## Using a Custom Staging Stack per Environment\n\nIf you want to customize some behavior that is not configurable via properties,\nyou can implement your own class that implements `IStagingResources`. To get a head start,\nyou can subclass `DefaultStagingStack`.\n\n```ts\ninterface CustomStagingStackOptions extends DefaultStagingStackOptions {}\n\nclass CustomStagingStack extends DefaultStagingStack {\n}\n```\n\nOr you can roll your own staging resources from scratch, as long as it implements `IStagingResources`.\n\n```ts\ninterface CustomStagingStackProps extends StackProps {}\n\nclass CustomStagingStack extends Stack implements IStagingResources {\n  public constructor(scope: Construct, id: string, props: CustomStagingStackProps) {\n    super(scope, id, props);\n  }\n\n  public addFile(asset: FileAssetSource): FileStagingLocation {\n    return {\n      bucketName: 'myBucket',\n      assumeRoleArn: 'myArn',\n      dependencyStack: this,\n    };\n  }\n\n  public addDockerImage(asset: DockerImageAssetSource): ImageStagingLocation {\n    return {\n      repoName: 'myRepo',\n      assumeRoleArn: 'myArn',\n      dependencyStack: this,\n    };\n  }\n}\n```\n\nUsing your custom staging resources means implementing a `CustomFactory` class and calling the\n`AppStagingSynthesizer.customFactory()` static method. This has the benefit of providing a\ncustom Staging Stack that can be created in every environment the CDK App is deployed to.\n\n```ts fixture=with-custom-staging\nclass CustomFactory implements IStagingResourcesFactory {\n  public obtainStagingResources(stack: Stack, context: ObtainStagingResourcesContext) {\n    const myApp = App.of(stack);\n\n    return new CustomStagingStack(myApp!, `CustomStagingStack-${context.environmentString}`, {});\n  }\n}\n\nconst app = new App({\n  defaultStackSynthesizer: AppStagingSynthesizer.customFactory({\n    factory: new CustomFactory(),\n    oncePerEnv: true, // by default\n  }),\n});\n```\n\n## Using an Existing Staging Stack\n\nUse `AppStagingSynthesizer.customResources()` to supply an existing stack as the Staging Stack.\nMake sure that the custom stack you provide implements `IStagingResources`.\n\n```ts fixture=with-custom-staging\nconst resourceApp = new App();\nconst resources = new CustomStagingStack(resourceApp, 'CustomStagingStack', {});\n\nconst app = new App({\n  defaultStackSynthesizer: AppStagingSynthesizer.customResources({\n    resources,\n  }),\n});\n```\n\n## Known Limitations\n\nSince this module is experimental, there are some known limitations:\n\n- Currently this module does not support CDK Pipelines. You must deploy CDK Apps using this\n  synthesizer via `cdk deploy`.\n- This synthesizer only needs a bootstrap stack with Roles, without staging resources. We\n  haven't written such a bootstrap stack yet; at the moment you can use the existing modern\n  bootstrap stack, the staging resources in them will just go unused.\n- Due to limitations on the CloudFormation template size, CDK Applications can have\n  at most 38 independent ECR images.\n- When you run `cdk destroy` (for example during testing), the staging bucket and ECR\n  repositories will be left behind because CloudFormation cannot clean up non-empty resources.\n  You must deploy those resources manually if you want to redeploy again using the same `appId`.\n"
+    "markdown": "# App Staging Synthesizer\n<!--BEGIN STABILITY BANNER-->\n\n---\n\n![cdk-constructs: Experimental](https://img.shields.io/badge/cdk--constructs-experimental-important.svg?style=for-the-badge)\n\n> The APIs of higher level constructs in this module are experimental and under active development.\n> They are subject to non-backward compatible changes or removal in any future version. These are\n> not subject to the [Semantic Versioning](https://semver.org/) model and breaking changes will be\n> announced in the release notes. This means that while you may use them, you may need to update\n> your source code when upgrading to a newer version of this package.\n\n---\n\n<!--END STABILITY BANNER-->\n\nThis library includes constructs aimed at replacing the current model of bootstrapping and providing\ngreater control of the bootstrap experience to the CDK user. The important constructs in this library\nare as follows:\n\n- the `IStagingResources` interface: a framework for an app-level bootstrap stack that handles\n  file assets and docker assets.\n- the `DefaultStagingStack`, which is a works-out-of-the-box implementation of the `IStagingResources`\n  interface.\n- the `AppStagingSynthesizer`, a new CDK synthesizer that will synthesize CDK applications with\n  the staging resources provided.\n\n> As this library is `experimental`, there are features that are not yet implemented. Please look\n> at the list of [Known Limitations](#known-limitations) before getting started.\n\nTo get started, update your CDK App with a new `defaultStackSynthesizer`:\n\n```ts\nconst app = new App({\n  defaultStackSynthesizer: AppStagingSynthesizer.defaultResources({\n    appId: 'my-app-id', // put a unique id here\n  }),\n});\n```\n\nThis will introduce a `DefaultStagingStack` in your CDK App and staging assets of your App\nwill live in the resources from that stack rather than the CDK Bootstrap stack.\n\nIf you are migrating from a different version of synthesis your updated CDK App will target\nthe resources in the `DefaultStagingStack` and no longer be tied to the bootstrapped resources\nin your account.\n\n## Bootstrap Model\n\nIn our default bootstrapping process, when you run `cdk bootstrap aws://<account>/<region>`, the following\nresources are created:\n\n- It creates Roles to assume for cross-account deployments and for Pipeline deployments;\n- It creates staging resources: a global S3 bucket and global ECR repository to hold CDK assets;\n- It creates Roles to write to the S3 bucket and ECR repository;\n\nBecause the bootstrapping resources include regional resources, you need to bootstrap\nevery region you plan to deploy to individually. All assets of all CDK apps deploying\nto that account and region will be written to the single S3 Bucket and ECR repository.\n\nBy using the synthesizer in this library, instead of the\n`DefaultStackSynthesizer`, a different set of staging resources will be created\nfor every CDK application, and they will be created automatically as part of a\nregular deployment, in a separate Stack that is deployed before your application\nStacks. The staging resources will be one S3 bucket, and *one ECR repository per\nimage*, and Roles necessary to access those buckets and ECR repositories. The\nRoles from the default bootstrap stack are still used (though their use can be\nturned off).\n\nThis has the following advantages:\n\n- Because staging resources are now application-specific, they can be fully cleaned up when you clean up\n  the application.\n- Because there is now one ECR repository per image instead of one ECR repository for all images, it is\n  possible to effectively use ECR life cycle rules (for example, retain only the most recent 5 images)\n  to cut down on storage costs.\n- Resources between separate CDK Apps are separated so they can be cleaned up and lifecycle\n  controlled individually.\n- Because the only shared bootstrapping resources required are Roles, which are global resources,\n  you now only need to bootstrap every account in one Region (instead of every Region). This makes it\n  easier to do with CloudFormation StackSets.\n\nFor the deployment roles, this synthesizer still uses the Roles from the default\nbootstrap stack, and nothing else. The staging resources from that bootstrap\nstack will be unused. You can customize the template to remove those resources\nif you prefer.  In the future, we will provide a bootstrap stack template with\nonly those Roles, specifically for use with this synthesizer.\n\n## Using the Default Staging Stack per Environment\n\nThe most common use case will be to use the built-in default resources. In this scenario, the\nsynthesizer will create a new Staging Stack in each environment the CDK App is deployed to store\nits staging resources. To use this kind of synthesizer, use `AppStagingSynthesizer.defaultResources()`.\n\n```ts\nconst app = new App({\n  defaultStackSynthesizer: AppStagingSynthesizer.defaultResources({\n    appId: 'my-app-id',\n\n    // The following line is optional. By default it is assumed you have bootstrapped in the same\n    // region(s) as the stack(s) you are deploying.\n    deploymentIdentities: DeploymentIdentities.defaultBootstrapRoles({ bootstrapRegion: 'us-east-1' }),\n  }),\n});\n```\n\nEvery CDK App that uses the `DefaultStagingStack` must include an `appId`. This should\nbe an identifier unique to the app and is used to differentiate staging resources associated\nwith the app.\n\n### Default Staging Stack\n\nThe Default Staging Stack includes all the staging resources necessary for CDK Assets. The below example\nis of a CDK App using the `AppStagingSynthesizer` and creating a file asset for the Lambda Function\nsource code. As part of the `DefaultStagingStack`, an S3 bucket and IAM role will be created that will be\nused to upload the asset to S3.\n\n```ts\nconst app = new App({\n  defaultStackSynthesizer: AppStagingSynthesizer.defaultResources({ appId: 'my-app-id' }),\n});\n\nconst stack = new Stack(app, 'my-stack');\n\nnew lambda.Function(stack, 'lambda', {\n  code: lambda.AssetCode.fromAsset(path.join(__dirname, 'assets')),\n  handler: 'index.handler',\n  runtime: lambda.Runtime.PYTHON_3_9,\n});\n\napp.synth();\n```\n\n### Custom Roles\n\nYou can customize some or all of the roles you'd like to use in the synthesizer as well,\nif all you need is to supply custom roles (and not change anything else in the `DefaultStagingStack`):\n\n```ts\nconst app = new App({\n  defaultStackSynthesizer: AppStagingSynthesizer.defaultResources({\n    appId: 'my-app-id',\n    deploymentIdentities: DeploymentIdentities.specifyRoles({\n      cloudFormationExecutionRole: BootstrapRole.fromRoleArn('arn:aws:iam::123456789012:role/Execute'),\n      deploymentRole: BootstrapRole.fromRoleArn('arn:aws:iam::123456789012:role/Deploy'),\n      lookupRole: BootstrapRole.fromRoleArn('arn:aws:iam::123456789012:role/Lookup'),\n    }),\n  }),\n});\n```\n\nOr, you can ask to use the CLI credentials that exist at deploy-time.\nThese credentials must have the ability to perform CloudFormation calls,\nlookup resources in your account, and perform CloudFormation deployment.\nFor a full list of what is necessary, see `LookupRole`, `DeploymentActionRole`,\nand `CloudFormationExecutionRole` in the\n[bootstrap template](https://github.com/aws/aws-cdk/blob/main/packages/aws-cdk/lib/api/bootstrap/bootstrap-template.yaml).\n\n```ts\nconst app = new App({\n  defaultStackSynthesizer: AppStagingSynthesizer.defaultResources({\n    appId: 'my-app-id',\n    deploymentIdentities: DeploymentIdentities.cliCredentials(),\n  }),\n});\n```\n\nThe default staging stack will create roles to publish to the S3 bucket and ECR repositories,\nassumable by the deployment role. You can also specify an existing IAM role for the\n`fileAssetPublishingRole` or `imageAssetPublishingRole`:\n\n```ts\nconst app = new App({\n  defaultStackSynthesizer: AppStagingSynthesizer.defaultResources({\n    appId: 'my-app-id',\n    fileAssetPublishingRole: BootstrapRole.fromRoleArn('arn:aws:iam::123456789012:role/S3Access'),\n    imageAssetPublishingRole: BootstrapRole.fromRoleArn('arn:aws:iam::123456789012:role/ECRAccess'),\n  }),\n});\n```\n\n### Deploy Time S3 Assets\n\nThere are two types of assets:\n\n- Assets used only during deployment. These are used to hand off a large piece of data to another\nservice, that will make a private copy of that data. After deployment, the asset is only necessary for\na potential future rollback.\n- Assets accessed throughout the running life time of the application.\n\nExamples of assets that are only used at deploy time are CloudFormation Templates and Lambda Code\nbundles. Examples of assets accessed throughout the life time of the application are script files\ndownloaded to run in a CodeBuild Project, or on EC2 instance startup. ECR images are always application\nlife-time assets. S3 deploy time assets are stored with a `deploy-time/` prefix, and a lifecycle rule will collect them after a configurable number of days.\n\nLambda assets are by default marked as deploy time assets:\n\n```ts\ndeclare const stack: Stack;\nnew lambda.Function(stack, 'lambda', {\n  code: lambda.AssetCode.fromAsset(path.join(__dirname, 'assets')), // lambda marks deployTime = true\n  handler: 'index.handler',\n  runtime: lambda.Runtime.PYTHON_3_9,\n});\n```\n\nOr, if you want to create your own deploy time asset:\n\n```ts\nimport { Asset } from 'aws-cdk-lib/aws-s3-assets';\n\ndeclare const stack: Stack;\nconst asset = new Asset(stack, 'deploy-time-asset', {\n  deployTime: true,\n  path: path.join(__dirname, './deploy-time-asset'),\n});\n```\n\nBy default, we store deploy time assets for 30 days, but you can change this number by specifying\n`deployTimeFileAssetLifetime`. The number you specify here is how long you will be able to roll back\nto a previous version of an application just by doing a CloudFormation deployment with the old\ntemplate, without rebuilding and republishing assets.\n\n```ts\nconst app = new App({\n  defaultStackSynthesizer: AppStagingSynthesizer.defaultResources({\n    appId: 'my-app-id',\n    deployTimeFileAssetLifetime: Duration.days(100),\n  }),\n});\n```\n\n### Lifecycle Rules on ECR Repositories\n\nBy default, we store a maximum of 3 revisions of a particular docker image asset. This allows\nfor smooth faciliation of rollback scenarios where we may reference previous versions of an\nimage. When more than 3 revisions of an asset exist in the ECR repository, the oldest one is\npurged.\n\nTo change the number of revisions stored, use `imageAssetVersionCount`:\n\n```ts\nconst app = new App({\n  defaultStackSynthesizer: AppStagingSynthesizer.defaultResources({\n    appId: 'my-app-id',\n    imageAssetVersionCount: 10,\n  }),\n});\n```\n\n## Using a Custom Staging Stack per Environment\n\nIf you want to customize some behavior that is not configurable via properties,\nyou can implement your own class that implements `IStagingResources`. To get a head start,\nyou can subclass `DefaultStagingStack`.\n\n```ts\ninterface CustomStagingStackOptions extends DefaultStagingStackOptions {}\n\nclass CustomStagingStack extends DefaultStagingStack {\n}\n```\n\nOr you can roll your own staging resources from scratch, as long as it implements `IStagingResources`.\n\n```ts\ninterface CustomStagingStackProps extends StackProps {}\n\nclass CustomStagingStack extends Stack implements IStagingResources {\n  public constructor(scope: Construct, id: string, props: CustomStagingStackProps) {\n    super(scope, id, props);\n  }\n\n  public addFile(asset: FileAssetSource): FileStagingLocation {\n    return {\n      bucketName: 'myBucket',\n      assumeRoleArn: 'myArn',\n      dependencyStack: this,\n    };\n  }\n\n  public addDockerImage(asset: DockerImageAssetSource): ImageStagingLocation {\n    return {\n      repoName: 'myRepo',\n      assumeRoleArn: 'myArn',\n      dependencyStack: this,\n    };\n  }\n}\n```\n\nUsing your custom staging resources means implementing a `CustomFactory` class and calling the\n`AppStagingSynthesizer.customFactory()` static method. This has the benefit of providing a\ncustom Staging Stack that can be created in every environment the CDK App is deployed to.\n\n```ts fixture=with-custom-staging\nclass CustomFactory implements IStagingResourcesFactory {\n  public obtainStagingResources(stack: Stack, context: ObtainStagingResourcesContext) {\n    const myApp = App.of(stack);\n\n    return new CustomStagingStack(myApp!, `CustomStagingStack-${context.environmentString}`, {});\n  }\n}\n\nconst app = new App({\n  defaultStackSynthesizer: AppStagingSynthesizer.customFactory({\n    factory: new CustomFactory(),\n    oncePerEnv: true, // by default\n  }),\n});\n```\n\n## Using an Existing Staging Stack\n\nUse `AppStagingSynthesizer.customResources()` to supply an existing stack as the Staging Stack.\nMake sure that the custom stack you provide implements `IStagingResources`.\n\n```ts fixture=with-custom-staging\nconst resourceApp = new App();\nconst resources = new CustomStagingStack(resourceApp, 'CustomStagingStack', {});\n\nconst app = new App({\n  defaultStackSynthesizer: AppStagingSynthesizer.customResources({\n    resources,\n  }),\n});\n```\n\n## Known Limitations\n\nSince this module is experimental, there are some known limitations:\n\n- Currently this module does not support CDK Pipelines. You must deploy CDK Apps using this\n  synthesizer via `cdk deploy`. Please upvote [this issue](https://github.com/aws/aws-cdk/issues/26118)\n  to indicate you want this.\n- This synthesizer only needs a bootstrap stack with Roles, without staging resources. We\n  haven't written such a bootstrap stack yet; at the moment you can use the existing modern\n  bootstrap stack, the staging resources in them will just go unused. You can customize the\n  template to remove them if desired.\n- Due to limitations on the CloudFormation template size, CDK Applications can have\n  at most 38 independent ECR images. Please upvote [this issue](https://github.com/aws/aws-cdk/issues/26119)\n  if you need more than this.\n"
   },
   "repository": {
     "directory": "packages/@aws-cdk/app-staging-synthesizer-alpha",
@@ -3884,7 +3897,7 @@
       "kind": "class",
       "locationInModule": {
         "filename": "lib/bootstrap-roles.ts",
-        "line": 7
+        "line": 8
       },
       "methods": [
         {
@@ -3894,7 +3907,7 @@
           },
           "locationInModule": {
             "filename": "lib/bootstrap-roles.ts",
-            "line": 11
+            "line": 12
           },
           "name": "cliCredentials",
           "returns": {
@@ -3911,7 +3924,7 @@
           },
           "locationInModule": {
             "filename": "lib/bootstrap-roles.ts",
-            "line": 18
+            "line": 19
           },
           "name": "fromRoleArn",
           "parameters": [
@@ -3936,7 +3949,7 @@
           },
           "locationInModule": {
             "filename": "lib/bootstrap-roles.ts",
-            "line": 30
+            "line": 31
           },
           "name": "isCliCredentials",
           "returns": {
@@ -3964,7 +3977,7 @@
       "kind": "interface",
       "locationInModule": {
         "filename": "lib/bootstrap-roles.ts",
-        "line": 89
+        "line": 142
       },
       "name": "BootstrapRoles",
       "properties": [
@@ -3978,7 +3991,7 @@
           "immutable": true,
           "locationInModule": {
             "filename": "lib/bootstrap-roles.ts",
-            "line": 95
+            "line": 148
           },
           "name": "cloudFormationExecutionRole",
           "optional": true,
@@ -3996,7 +4009,7 @@
           "immutable": true,
           "locationInModule": {
             "filename": "lib/bootstrap-roles.ts",
-            "line": 102
+            "line": 155
           },
           "name": "deploymentRole",
           "optional": true,
@@ -4014,7 +4027,7 @@
           "immutable": true,
           "locationInModule": {
             "filename": "lib/bootstrap-roles.ts",
-            "line": 109
+            "line": 162
           },
           "name": "lookupRole",
           "optional": true,
@@ -4125,6 +4138,47 @@
       ],
       "symbolId": "lib/app-staging-synthesizer:CustomResourcesOptions"
     },
+    "@aws-cdk/app-staging-synthesizer-alpha.DefaultBootstrapRolesOptions": {
+      "assembly": "@aws-cdk/app-staging-synthesizer-alpha",
+      "datatype": true,
+      "docs": {
+        "stability": "experimental",
+        "summary": "Options for `DeploymentIdentities.defaultBootstrappedRoles`.",
+        "example": "const app = new App({\n  defaultStackSynthesizer: AppStagingSynthesizer.defaultResources({\n    appId: 'my-app-id',\n\n    // The following line is optional. By default it is assumed you have bootstrapped in the same\n    // region(s) as the stack(s) you are deploying.\n    deploymentIdentities: DeploymentIdentities.defaultBootstrapRoles({ bootstrapRegion: 'us-east-1' }),\n  }),\n});",
+        "custom": {
+          "exampleMetadata": "infused"
+        }
+      },
+      "fqn": "@aws-cdk/app-staging-synthesizer-alpha.DefaultBootstrapRolesOptions",
+      "kind": "interface",
+      "locationInModule": {
+        "filename": "lib/bootstrap-roles.ts",
+        "line": 128
+      },
+      "name": "DefaultBootstrapRolesOptions",
+      "properties": [
+        {
+          "abstract": true,
+          "docs": {
+            "default": "- the stack's current region",
+            "remarks": "By default, the region in which the stack is deployed is used.",
+            "stability": "experimental",
+            "summary": "The region where the default bootstrap roles have been created."
+          },
+          "immutable": true,
+          "locationInModule": {
+            "filename": "lib/bootstrap-roles.ts",
+            "line": 136
+          },
+          "name": "bootstrapRegion",
+          "optional": true,
+          "type": {
+            "primitive": "string"
+          }
+        }
+      ],
+      "symbolId": "lib/bootstrap-roles:DefaultBootstrapRolesOptions"
+    },
     "@aws-cdk/app-staging-synthesizer-alpha.DefaultResourcesOptions": {
       "assembly": "@aws-cdk/app-staging-synthesizer-alpha",
       "datatype": true,
@@ -4164,7 +4218,7 @@
         },
         "locationInModule": {
           "filename": "lib/default-staging-stack.ts",
-          "line": 198
+          "line": 230
         },
         "parameters": [
           {
@@ -4193,7 +4247,7 @@
       "kind": "class",
       "locationInModule": {
         "filename": "lib/default-staging-stack.ts",
-        "line": 118
+        "line": 143
       },
       "methods": [
         {
@@ -4203,7 +4257,7 @@
           },
           "locationInModule": {
             "filename": "lib/default-staging-stack.ts",
-            "line": 122
+            "line": 147
           },
           "name": "factory",
           "parameters": [
@@ -4228,7 +4282,7 @@
           },
           "locationInModule": {
             "filename": "lib/default-staging-stack.ts",
-            "line": 397
+            "line": 450
           },
           "name": "addDockerImage",
           "overrides": "@aws-cdk/app-staging-synthesizer-alpha.IStagingResources",
@@ -4253,7 +4307,7 @@
           },
           "locationInModule": {
             "filename": "lib/default-staging-stack.ts",
-            "line": 385
+            "line": 438
           },
           "name": "addFile",
           "overrides": "@aws-cdk/app-staging-synthesizer-alpha.IStagingResources",
@@ -4282,7 +4336,7 @@
           "immutable": true,
           "locationInModule": {
             "filename": "lib/default-staging-stack.ts",
-            "line": 176
+            "line": 207
           },
           "name": "dependencyStack",
           "type": {
@@ -4297,7 +4351,7 @@
           "immutable": true,
           "locationInModule": {
             "filename": "lib/default-staging-stack.ts",
-            "line": 171
+            "line": 202
           },
           "name": "stagingRepos",
           "type": {
@@ -4317,7 +4371,7 @@
           "immutable": true,
           "locationInModule": {
             "filename": "lib/default-staging-stack.ts",
-            "line": 166
+            "line": 197
           },
           "name": "stagingBucket",
           "optional": true,
@@ -4343,7 +4397,7 @@
       "kind": "interface",
       "locationInModule": {
         "filename": "lib/default-staging-stack.ts",
-        "line": 28
+        "line": 45
       },
       "name": "DefaultStagingStackOptions",
       "properties": [
@@ -4357,13 +4411,31 @@
           "immutable": true,
           "locationInModule": {
             "filename": "lib/default-staging-stack.ts",
-            "line": 38
+            "line": 55
           },
           "name": "appId",
           "type": {
             "primitive": "string"
           }
         },
+        {
+          "abstract": true,
+          "docs": {
+            "default": "true",
+            "stability": "experimental",
+            "summary": "Auto deletes objects in the staging S3 bucket and images in the staging ECR repositories."
+          },
+          "immutable": true,
+          "locationInModule": {
+            "filename": "lib/default-staging-stack.ts",
+            "line": 113
+          },
+          "name": "autoDeleteStagingAssets",
+          "optional": true,
+          "type": {
+            "primitive": "boolean"
+          }
+        },
         {
           "abstract": true,
           "docs": {
@@ -4375,7 +4447,7 @@
           "immutable": true,
           "locationInModule": {
             "filename": "lib/default-staging-stack.ts",
-            "line": 76
+            "line": 93
           },
           "name": "deployTimeFileAssetLifetime",
           "optional": true,
@@ -4393,7 +4465,7 @@
           "immutable": true,
           "locationInModule": {
             "filename": "lib/default-staging-stack.ts",
-            "line": 52
+            "line": 69
           },
           "name": "fileAssetPublishingRole",
           "optional": true,
@@ -4411,7 +4483,7 @@
           "immutable": true,
           "locationInModule": {
             "filename": "lib/default-staging-stack.ts",
-            "line": 59
+            "line": 76
           },
           "name": "imageAssetPublishingRole",
           "optional": true,
@@ -4430,7 +4502,7 @@
           "immutable": true,
           "locationInModule": {
             "filename": "lib/default-staging-stack.ts",
-            "line": 88
+            "line": 105
           },
           "name": "imageAssetVersionCount",
           "optional": true,
@@ -4448,7 +4520,7 @@
           "immutable": true,
           "locationInModule": {
             "filename": "lib/default-staging-stack.ts",
-            "line": 45
+            "line": 62
           },
           "name": "stagingBucketName",
           "optional": true,
@@ -4465,7 +4537,7 @@
       "docs": {
         "stability": "experimental",
         "summary": "Default Staging Stack Properties.",
-        "example": "// The code below shows an example of how to instantiate this type.\n// The values are placeholders you should change.\nimport * as app_staging_synthesizer_alpha from '@aws-cdk/app-staging-synthesizer-alpha';\nimport * as cdk from 'aws-cdk-lib';\n\ndeclare const bootstrapRole: app_staging_synthesizer_alpha.BootstrapRole;\ndeclare const permissionsBoundary: cdk.PermissionsBoundary;\ndeclare const stackSynthesizer: cdk.StackSynthesizer;\nconst defaultStagingStackProps: app_staging_synthesizer_alpha.DefaultStagingStackProps = {\n  appId: 'appId',\n  qualifier: 'qualifier',\n\n  // the properties below are optional\n  analyticsReporting: false,\n  crossRegionReferences: false,\n  deployRoleArn: 'deployRoleArn',\n  deployTimeFileAssetLifetime: cdk.Duration.minutes(30),\n  description: 'description',\n  env: {\n    account: 'account',\n    region: 'region',\n  },\n  fileAssetPublishingRole: bootstrapRole,\n  imageAssetPublishingRole: bootstrapRole,\n  imageAssetVersionCount: 123,\n  permissionsBoundary: permissionsBoundary,\n  stackName: 'stackName',\n  stagingBucketName: 'stagingBucketName',\n  synthesizer: stackSynthesizer,\n  tags: {\n    tagsKey: 'tags',\n  },\n  terminationProtection: false,\n};",
+        "example": "// The code below shows an example of how to instantiate this type.\n// The values are placeholders you should change.\nimport * as app_staging_synthesizer_alpha from '@aws-cdk/app-staging-synthesizer-alpha';\nimport * as cdk from 'aws-cdk-lib';\n\ndeclare const bootstrapRole: app_staging_synthesizer_alpha.BootstrapRole;\ndeclare const permissionsBoundary: cdk.PermissionsBoundary;\ndeclare const stackSynthesizer: cdk.StackSynthesizer;\nconst defaultStagingStackProps: app_staging_synthesizer_alpha.DefaultStagingStackProps = {\n  appId: 'appId',\n  qualifier: 'qualifier',\n\n  // the properties below are optional\n  analyticsReporting: false,\n  autoDeleteStagingAssets: false,\n  crossRegionReferences: false,\n  deployRoleArn: 'deployRoleArn',\n  deployTimeFileAssetLifetime: cdk.Duration.minutes(30),\n  description: 'description',\n  env: {\n    account: 'account',\n    region: 'region',\n  },\n  fileAssetPublishingRole: bootstrapRole,\n  imageAssetPublishingRole: bootstrapRole,\n  imageAssetVersionCount: 123,\n  permissionsBoundary: permissionsBoundary,\n  stackName: 'stackName',\n  stagingBucketName: 'stagingBucketName',\n  suppressTemplateIndentation: false,\n  synthesizer: stackSynthesizer,\n  tags: {\n    tagsKey: 'tags',\n  },\n  terminationProtection: false,\n};",
         "custom": {
           "exampleMetadata": "fixture=_generated"
         }
@@ -4478,7 +4550,7 @@
       "kind": "interface",
       "locationInModule": {
         "filename": "lib/default-staging-stack.ts",
-        "line": 94
+        "line": 119
       },
       "name": "DefaultStagingStackProps",
       "properties": [
@@ -4492,7 +4564,7 @@
           "immutable": true,
           "locationInModule": {
             "filename": "lib/default-staging-stack.ts",
-            "line": 109
+            "line": 134
           },
           "name": "qualifier",
           "type": {
@@ -4510,7 +4582,7 @@
           "immutable": true,
           "locationInModule": {
             "filename": "lib/default-staging-stack.ts",
-            "line": 102
+            "line": 127
           },
           "name": "deployRoleArn",
           "optional": true,
@@ -4526,7 +4598,7 @@
       "docs": {
         "stability": "experimental",
         "summary": "Deployment identities are the class of roles to be assumed by the CDK when deploying the App.",
-        "example": "const app = new App({\n  defaultStackSynthesizer: AppStagingSynthesizer.defaultResources({\n    appId: 'my-app-id',\n    deploymentIdentities: DeploymentIdentities.specifyRoles({\n      cloudFormationExecutionRole: BootstrapRole.fromRoleArn('arn:aws:iam::123456789012:role/Execute'),\n      deploymentRole: BootstrapRole.fromRoleArn('arn:aws:iam::123456789012:role/Deploy'),\n      lookupRole: BootstrapRole.fromRoleArn('arn:aws:iam::123456789012:role/Lookup'),\n    }),\n  }),\n});",
+        "example": "const app = new App({\n  defaultStackSynthesizer: AppStagingSynthesizer.defaultResources({\n    appId: 'my-app-id',\n\n    // The following line is optional. By default it is assumed you have bootstrapped in the same\n    // region(s) as the stack(s) you are deploying.\n    deploymentIdentities: DeploymentIdentities.defaultBootstrapRoles({ bootstrapRegion: 'us-east-1' }),\n  }),\n});",
         "custom": {
           "exampleMetadata": "infused"
         }
@@ -4535,7 +4607,7 @@
       "kind": "class",
       "locationInModule": {
         "filename": "lib/bootstrap-roles.ts",
-        "line": 60
+        "line": 61
       },
       "methods": [
         {
@@ -4545,7 +4617,7 @@
           },
           "locationInModule": {
             "filename": "lib/bootstrap-roles.ts",
-            "line": 64
+            "line": 65
           },
           "name": "cliCredentials",
           "returns": {
@@ -4555,6 +4627,32 @@
           },
           "static": true
         },
+        {
+          "docs": {
+            "stability": "experimental",
+            "summary": "Use the Roles that have been created by the default bootstrap stack."
+          },
+          "locationInModule": {
+            "filename": "lib/bootstrap-roles.ts",
+            "line": 84
+          },
+          "name": "defaultBootstrapRoles",
+          "parameters": [
+            {
+              "name": "options",
+              "optional": true,
+              "type": {
+                "fqn": "@aws-cdk/app-staging-synthesizer-alpha.DefaultBootstrapRolesOptions"
+              }
+            }
+          ],
+          "returns": {
+            "type": {
+              "fqn": "@aws-cdk/app-staging-synthesizer-alpha.DeploymentIdentities"
+            }
+          },
+          "static": true
+        },
         {
           "docs": {
             "remarks": "These roles\nmust already exist.",
@@ -4563,7 +4661,7 @@
           },
           "locationInModule": {
             "filename": "lib/bootstrap-roles.ts",
-            "line": 76
+            "line": 77
           },
           "name": "specifyRoles",
           "parameters": [
@@ -4587,16 +4685,50 @@
         {
           "docs": {
             "stability": "experimental",
-            "summary": "roles that are bootstrapped to your account."
+            "summary": "CloudFormation Execution Role."
           },
           "immutable": true,
           "locationInModule": {
             "filename": "lib/bootstrap-roles.ts",
-            "line": 82
+            "line": 102
           },
-          "name": "roles",
+          "name": "cloudFormationExecutionRole",
+          "optional": true,
           "type": {
-            "fqn": "@aws-cdk/app-staging-synthesizer-alpha.BootstrapRoles"
+            "fqn": "@aws-cdk/app-staging-synthesizer-alpha.BootstrapRole"
+          }
+        },
+        {
+          "docs": {
+            "stability": "experimental",
+            "summary": "Deployment Action Role."
+          },
+          "immutable": true,
+          "locationInModule": {
+            "filename": "lib/bootstrap-roles.ts",
+            "line": 107
+          },
+          "name": "deploymentRole",
+          "optional": true,
+          "type": {
+            "fqn": "@aws-cdk/app-staging-synthesizer-alpha.BootstrapRole"
+          }
+        },
+        {
+          "docs": {
+            "default": "- use bootstrapped role",
+            "stability": "experimental",
+            "summary": "Lookup Role."
+          },
+          "immutable": true,
+          "locationInModule": {
+            "filename": "lib/bootstrap-roles.ts",
+            "line": 113
+          },
+          "name": "lookupRole",
+          "optional": true,
+          "type": {
+            "fqn": "@aws-cdk/app-staging-synthesizer-alpha.BootstrapRole"
           }
         }
       ],
@@ -4980,7 +5112,7 @@
       "kind": "interface",
       "locationInModule": {
         "filename": "lib/bootstrap-roles.ts",
-        "line": 116
+        "line": 169
       },
       "name": "StagingRoles",
       "properties": [
@@ -4994,7 +5126,7 @@
           "immutable": true,
           "locationInModule": {
             "filename": "lib/bootstrap-roles.ts",
-            "line": 129
+            "line": 182
           },
           "name": "dockerAssetPublishingRole",
           "optional": true,
@@ -5012,7 +5144,7 @@
           "immutable": true,
           "locationInModule": {
             "filename": "lib/bootstrap-roles.ts",
-            "line": 122
+            "line": 175
           },
           "name": "fileAssetPublishingRole",
           "optional": true,
@@ -5022,8 +5154,52 @@
         }
       ],
       "symbolId": "lib/bootstrap-roles:StagingRoles"
+    },
+    "@aws-cdk/app-staging-synthesizer-alpha.UsingAppStagingSynthesizer": {
+      "assembly": "@aws-cdk/app-staging-synthesizer-alpha",
+      "base": "constructs.Construct",
+      "docs": {
+        "remarks": "It does not do anything, and is not meant\nto be created on its own. This construct will be a part of the\nconstruct tree only and not the Cfn template. The construct tree is\nthen encoded in the AWS::CDK::Metadata resource of the stack and\ninjested in our metrics like every other construct.",
+        "stability": "experimental",
+        "summary": "This is a dummy construct meant to signify that a stack is utilizing the AppStagingSynthesizer.",
+        "example": "// The code below shows an example of how to instantiate this type.\n// The values are placeholders you should change.\nimport * as app_staging_synthesizer_alpha from '@aws-cdk/app-staging-synthesizer-alpha';\nconst usingAppStagingSynthesizer = new app_staging_synthesizer_alpha.UsingAppStagingSynthesizer(this, 'MyUsingAppStagingSynthesizer');",
+        "custom": {
+          "exampleMetadata": "fixture=_generated"
+        }
+      },
+      "fqn": "@aws-cdk/app-staging-synthesizer-alpha.UsingAppStagingSynthesizer",
+      "initializer": {
+        "docs": {
+          "stability": "experimental"
+        },
+        "locationInModule": {
+          "filename": "lib/default-staging-stack.ts",
+          "line": 37
+        },
+        "parameters": [
+          {
+            "name": "scope",
+            "type": {
+              "fqn": "constructs.Construct"
+            }
+          },
+          {
+            "name": "id",
+            "type": {
+              "primitive": "string"
+            }
+          }
+        ]
+      },
+      "kind": "class",
+      "locationInModule": {
+        "filename": "lib/default-staging-stack.ts",
+        "line": 36
+      },
+      "name": "UsingAppStagingSynthesizer",
+      "symbolId": "lib/default-staging-stack:UsingAppStagingSynthesizer"
     }
   },
-  "version": "2.84.0-alpha.0",
+  "version": "2.86.0-alpha.0",
   "fingerprint": "**********"
 }