Customise CDK bootstraping

[dai-knapz-tr]

Environment information

System:
  OS: Linux 6.6 Ubuntu 24.04.3 LTS 24.04.3 LTS (Noble Numbat)
  CPU: (14) x64 Intel(R) Core(TM) Ultra 5 135U
  Memory: 6.59 GB / 7.49 GB
  Shell: /usr/bin/zsh
Binaries:
  Node: 22.15.0 - ~/.nvm/versions/node/v22.15.0/bin/node
  Yarn: undefined - undefined
  npm: 10.9.2 - ~/.nvm/versions/node/v22.15.0/bin/npm
  pnpm: undefined - undefined
NPM Packages:
  @aws-amplify/auth-construct: 1.3.2
  @aws-amplify/backend: 1.5.1
  @aws-amplify/backend-auth: 1.2.0
  @aws-amplify/backend-cli: 1.3.0
  @aws-amplify/backend-data: 1.1.5
  @aws-amplify/backend-deployer: 1.1.5
  @aws-amplify/backend-function: 1.7.1
  @aws-amplify/backend-output-schemas: 1.4.0
  @aws-amplify/backend-output-storage: 1.1.2
  @aws-amplify/backend-secret: 1.1.4
  @aws-amplify/backend-storage: 1.2.1
  @aws-amplify/cli-core: 1.1.3
  @aws-amplify/client-config: 1.5.0
  @aws-amplify/deployed-backend-client: 1.4.2
  @aws-amplify/form-generator: 1.0.3
  @aws-amplify/model-generator: 1.0.8
  @aws-amplify/platform-core: 1.1.0
  @aws-amplify/plugin-types: 1.3.0
  @aws-amplify/sandbox: 1.2.3
  @aws-amplify/schema-generator: 1.2.4
  aws-amplify: 6.6.6
  aws-cdk: 2.163.1
  aws-cdk-lib: 2.214.0
  typescript: 5.6.3
AWS environment variables:
  AWS_STS_REGIONAL_ENDPOINTS = regional
  AWS_NODEJS_CONNECTION_REUSE_ENABLED = 1
  AWS_SDK_LOAD_CONFIG = 1
No CDK environment variables

Describe the feature

We would like the ability to customise the CDK bootstrap stack that Amplify uses for deployment. This would allow us to follow our organisations tagging and naming requirements. I've also raised a support ticket for this (Case ID 175769097700390) if you need more organisation specifics.

Use case

We have tagging and naming requirements imposed on our account that mean we cannot use the default CDK bootstrap command. We have a custom wrapper on the CDK & CDK CLI that allows us to create a CF bootstrap stack that follows all naming and tagging requirements, but amplify cannot detect this stack as I have no options to customise the synth as described by https://docs.aws.amazon.com/cdk/v2/guide/customize-synth.html

[pahud]

Hi @dai-knapz-tr,

Thank you for this feature request and the detailed use case with your support ticket reference. The ability to customize CDK bootstrap configuration is indeed a valuable enhancement for enterprise customers with organizational compliance requirements.

Current Limitation: Amplify Gen 2 uses the CDK Toolkit internally without exposing bootstrap customization options. This prevents organizations from applying required tagging policies, naming conventions, and other compliance requirements to the CDK bootstrap stack.

Existing CDK Support: The underlying AWS CDK already supports custom bootstrap templates via cdk bootstrap --template custom-template.yaml, and there are active discussions in the CDK community about expanding bootstrap customization (see aws/aws-cdk#19130 and aws/aws-cdk-cli#284).

After reviewing the Amplify documentation, there's no supported method for Amplify to detect or use pre-existing custom bootstrap stacks. Amplify manages its own bootstrap process internally through the CDK Toolkit so I am making this a feature request.

Thank you for providing the comprehensive context and support ticket reference.