chore(release): 2.199.0 #34561

aws-cdk-automation · 2025-05-27T12:40:00Z

### Issue # (if applicable) Closes #34376. ### Reason for this change ### Description of changes This PR corrects the JSDoc comment for the `storageType` property in `DatabaseCluster`. According to CloudFormation documentation, the default value for Aurora clusters is `aurora` (Aurora Standard), not `aurora-iopt1` (Aurora I/O Optimized) as incorrectly documented. https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-rds-dbcluster.html#cfn-rds-dbcluster-storagetype ### Describe any new or updated permissions being added ### Description of how you validated changes ### Checklist - [ ] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*

Add new models. Ref: https://aws.amazon.com/about-aws/whats-new/2025/05/anthropics-claude-4-foundation-models-amazon-bedrock/ ```sh aws bedrock list-foundation-models \ --region us-west-2 \ --query 'modelSummaries[].modelId' \ --output table ---------------------------------------------------- | ListFoundationModels | +--------------------------------------------------+ ... | anthropic.claude-opus-4-20250514-v1:0 | | anthropic.claude-sonnet-4-20250514-v1:0 | ... ``` ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*

…lEngineVersion.of() (#33564) Previously, AuroraMysqlEngineVersion.of() incorrectly determined whether import and export roles should be combined. This caused inconsistent behavior when specifying engine versions manually using AuroraMysqlEngineVersion.of(...), leading to incorrect parameter settings in the DBClusterParameterGroup. ### Issue #33562 Closes #33562 ### Reason for this change The issue arises when specifying a custom Aurora MySQL version using AuroraMysqlEngineVersion.of(...). The logic for determining whether import and export roles should be combined is incorrect. It should be based on the major version. This bug causes s3ExportBuckets to configure DBClusterParameterGroup incorrectly: - It adds .aurora_select_into_s3_role instead of .aws_default_s3_role - This behavior differs from using built-in versions like AuroraMysqlEngineVersion.VER_3_07_1 ### Description of changes If the major version is not "5.7", _combineImportAndExportRoles is set to true ### Describe any new or updated permissions being added None. ### Description of how you validated changes - Ran unit tests to confirm that the changes work as expected ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*

… to NetworkMultipleTargetGroupsFargateService (#34516) ### Issue # (if applicable) Closes #34368. ### Reason for this change Setting minHealthyPercent on the `NetworkMultipleTargetGroupsFargateService` in ecs_patterns doesn't prevent the warning for not setting `minimumHealthyPercent` from being displayed. When explicitly setting the minimumHealthyPercent via the underlying L1, the warning still appears. This is noisy for users who monitor their deployments for notices/warnings/errors and should also be supported as a feature directly on the L3. ### Description of changes - Added `minHealthyPercent` and `maxHealthyPercent` properties to the `NetworkMultipleTargetGroupsFargateServiceProps` interface - Updated the `createFargateService` method to pass these properties to the underlying `FargateService` constructor - Added tests to verify that setting `minHealthyPercent` properly passes the value to the service and prevents warnings ### Describe any new or updated permissions being added No new or updated permissions are needed. ### Description of how you validated changes Added two unit tests: 1. To verify that setting minHealthyPercent and maxHealthyPercent correctly passes the values to the AWS::ECS::Service resource 2. To verify that setting minHealthyPercent prevents warnings from being displayed ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*

See [CHANGELOG](https://github.com/aws/aws-cdk/blob/merge-back/2.198.0/CHANGELOG.md)

…34418) ### Issue # (if applicable) None ### Reason for this change Cloudformation now supports for configuring deletion protection check for configuration profile in addition to environment. https://docs.aws.amazon.com/appconfig/latest/userguide/deletion-protection.html https://docs.aws.amazon.com/ja_jp/AWSCloudFormation/latest/UserGuide/aws-resource-appconfig-configurationprofile.html#cfn-appconfig-configurationprofile-deletionprotectioncheck ### Description of changes - Add `deletionProtectionCheck` to both `HostedConfigurationProfileProps` and `SourcedConfigurationProfileProps` ### Describe any new or updated permissions being added None ### Description of how you validated changes Add both unit and integ tests. ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*

…arget (#34259) ### Issue # (if applicable) There's currently no issue for this, but I'd be happy to create it. ### Reason for this change Using an IAM role also fixes potential issues of failed published messages in case the target SNS topic is encrypted with KMS. According to this article, it's recommended to use execution roles for EventBridge targets. https://aws.amazon.com/about-aws/whats-new/2025/03/amazon-eventbridge-iam-execution-role-all-targets/ > We recommend configuring execution roles for all your EventBridge targets to benefit from consistent permissions policies and (...) ### Description of changes The `SnsTopic` target still has the same default behavior. However, it's now possible to opt-in to IAM role usage by setting the `authorizeUsingRole` property to `true`. It's also possible to provide a custom `role` as property. ### Describe any new or updated permissions being added The `sns:Publish` action is allowed on the topicArn in case an IAM role is used. ### Description of how you validated changes Unit tests were updated and added. There was already an integration test for the SnsTopic target without role usage. I've added two more integration tests: one where `authorizeUsingRole` is set to true, and one where a custom role is provided. ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*

…ation (#31913) This PR was [previously created](#29043) and passed the community review, but the maintainer review stopped midway, and it was eventually closed. There shouldn’t be any issues with the content, so I am submitting the PR again. ### Issue # (if applicable) Closes #29042 ### Reason for this change AWS stepfunctions support optimized integration with AWS bedrock. Currently, only invokeModel is supported by CDK, but I would like createModelCustomizationJob to be supported in the same manner. ### Description of changes I've added CreatemodelCustomizationJob class. ```ts const taskConfig = { baseModel: model, clientRequestToken: 'MyToken', customizationType: CustomizationType.FINE_TUNING, kmsKey, customModelName: 'MyCustomModel', customModelTags: [{ key: 'key1', value: 'value1' }], hyperParameters: { batchSize: '10', }, jobName: 'MyCustomizationJob', jobTags: [{ key: 'key2', value: 'value2' }], outputDataS3Uri: outputBucket.s3UrlForObject(), trainingDataS3Uri: trainingBucket.s3UrlForObject(), validationDataS3Uri: [validationBucket.s3UrlForObject()], vpcConfig: { securityGroups: [new ec2.SecurityGroup(stack, 'SecurityGroup', { vpc })], subnets: vpc.isolatedSubnets, }, }; const task1 = new BedrockCreateModelCustomizationJob(stack, 'CreateModelCustomizationJob1', taskConfig); const chain = sfn.Chain .start(new sfn.Pass(stack, 'Start')) .next(task1) .next(new sfn.Pass(stack, 'Done')); new sfn.StateMachine(stack, 'StateMachine', { definitionBody: sfn.DefinitionBody.fromChainable(chain), timeout: cdk.Duration.seconds(30), }); ``` ### Description of how you validated changes I've added both unit and integ tests. ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*

Ran npm-check-updates and yarn upgrade to keep the `yarn.lock` file up-to-date.

### Issue # (if applicable) ### Reason for this change We recommend to use cross stack reference but does not provide workaround when fail due to cross stack reference issue. ### Description of changes Adding a readme to explain ### Describe any new or updated permissions being added ### Description of how you validated changes ### Checklist - [ ] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*

…for certificates on HTTP protocol (#34233) ### Issue # (if applicable) ### Reason for this change ElasticLoadBalancerV2 throw a 400 error if you try to append a certificate to a listener on port 80 (or protocol HTTP). This PR brings this same validation to CDK ### Description of changes Added a new check for the application protocol and the length of certificates, and if there is any certificate, throw a validation error. Also, added a test for this case. ### Describe any new or updated permissions being added ### Description of how you validated changes ### Checklist My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

…m CcApi context provider has exactly one resource (#34199) ### Issue # (if applicable) Follow-up to #33619. ### Reason for this change CcApi context provider now can expect the matched count of resources: aws/aws-cdk-cli#251. `PrefixList.fromLookup()` is needed to be updated using this feature not to persist invalid results in `cdk.context.json`. See also aws/aws-cdk-cli#257. ### Description of changes - Bumped `@aws-cdk/cloud-assembly-schema` to latest ^43.6.0. - Specify `expectedMatchCount: 'exactly-one'` to expect exactly one prefix list id is returned. - Updated validation to check unexpected result. Actual error will be returned from the context provider. ### Describe any new or updated permissions being added N/A ### Description of how you validated changes Updated integ tests. ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*

### Issue # (if applicable) Closes #34001 ### Description of changes `Addon` support configurationValues, both v1 and v2 ### Description of how you validated changes Unit + Integ ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*

…om CcApi context provider has exactly one resource (#34557) Reverts #34199

…34555) Updates the L1 CloudFormation resource definitions with the latest changes from `@aws-cdk/aws-service-spec` **L1 CloudFormation resource definition changes:** ``` ├[~] service aws-aps │ └ resources │ └[~] resource AWS::APS::Workspace │ ├ properties │ │ └[+] QueryLoggingConfiguration: QueryLoggingConfiguration │ └ types │ ├[+] type CloudWatchLogDestination │ │ ├ documentation: Represents a cloudwatch logs destination for query logging │ │ │ name: CloudWatchLogDestination │ │ └ properties │ │ └ LogGroupArn: string (required) │ ├[+] type LoggingDestination │ │ ├ documentation: Destinations for query logging │ │ │ name: LoggingDestination │ │ └ properties │ │ ├ CloudWatchLogs: CloudWatchLogDestination (required) │ │ └ Filters: LoggingFilter (required) │ ├[+] type LoggingFilter │ │ ├ documentation: Filters for logging │ │ │ name: LoggingFilter │ │ └ properties │ │ └ QspThreshold: integer (required) │ └[+] type QueryLoggingConfiguration │ ├ documentation: Query logging configuration │ │ name: QueryLoggingConfiguration │ └ properties │ └ Destinations: Array<LoggingDestination> (required) ├[~] service aws-bedrock │ └ resources │ ├[~] resource AWS::Bedrock::Flow │ │ └ types │ │ ├[~] type FlowNodeConfiguration │ │ │ └ properties │ │ │ └[+] InlineCode: InlineCodeFlowNodeConfiguration │ │ └[+] type InlineCodeFlowNodeConfiguration │ │ ├ documentation: Inline code config strucuture, contains code configs │ │ │ name: InlineCodeFlowNodeConfiguration │ │ └ properties │ │ ├ Code: string (required) │ │ └ Language: string (required) │ ├[~] resource AWS::Bedrock::FlowAlias │ │ ├ properties │ │ │ └[+] ConcurrencyConfiguration: FlowAliasConcurrencyConfiguration │ │ └ types │ │ └[+] type FlowAliasConcurrencyConfiguration │ │ ├ name: FlowAliasConcurrencyConfiguration │ │ └ properties │ │ ├ Type: string (required) │ │ └ MaxConcurrency: number │ └[~] resource AWS::Bedrock::FlowVersion │ └ types │ ├[~] type FlowNodeConfiguration │ │ └ properties │ │ └[+] InlineCode: InlineCodeFlowNodeConfiguration │ └[+] type InlineCodeFlowNodeConfiguration │ ├ documentation: Inline code config strucuture, contains code configs │ │ name: InlineCodeFlowNodeConfiguration │ └ properties │ ├ Code: string (required) │ └ Language: string (required) ├[~] service aws-ses │ └ resources │ └[+] resource AWS::SES::MailManagerAddressList │ ├ name: MailManagerAddressList │ │ cloudFormationType: AWS::SES::MailManagerAddressList │ │ documentation: Definition of AWS::SES::MailManagerAddressList Resource Type │ │ tagInformation: {"tagPropertyName":"Tags","variant":"standard"} │ ├ properties │ │ ├ AddressListName: string (immutable) │ │ └ Tags: Array<tag> │ └ attributes │ ├ AddressListId: string │ └ AddressListArn: string └[~] service aws-vpclattice └ resources ├[~] resource AWS::VpcLattice::ResourceConfiguration │ └ properties │ ├ Name: - string │ │ + string (required) │ └ ResourceConfigurationType: - string (immutable) │ + string (required, immutable) └[~] resource AWS::VpcLattice::ResourceGateway └ properties ├ Name: - string (immutable) │ + string (required, immutable) ├ SubnetIds: - Array<string> (immutable) │ + Array<string> (required, immutable) └ VpcIdentifier: - string (immutable) + string (required, immutable) ``` BREAKING CHANGE: Some L1 resources experienced breaking changes due to updated CloudFormation resources. Please check the notes for each specific module for more information. * **aws-cdl-lib.vpc_lattice**: the `name` and `resourceConfigurationType` property in `CfnResourceConfigurationProps` has changed from optional to required. Also, the `name`, `subnetIds` and `vpcIdentifier` properties in `CfnResourceGatewayProps` have changed form optional to mandatory.

updating changelog message

Updated changelog message

aws-cdk-automation · 2025-05-27T13:47:23Z

AWS CodeBuild CI Report

CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
Commit ID: 0c5930d
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

mergify · 2025-05-27T13:47:47Z

Thank you for contributing! Your pull request will be automatically updated and merged without squashing (do not update manually, and be sure to allow changes to be pushed to your fork).

github-actions · 2025-05-27T13:48:04Z

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.

ykethan and others added 17 commits May 22, 2025 23:23

Merge branch 'main' into merge-back/2.198.0

bf1bb75

chore(merge-back): 2.198.0 (#34535)

d604089

See [CHANGELOG](https://github.com/aws/aws-cdk/blob/merge-back/2.198.0/CHANGELOG.md)

chore: npm-check-updates && yarn upgrade (#34513)

7fa3bbd

Ran npm-check-updates and yarn upgrade to keep the `yarn.lock` file up-to-date.

revert(ec2): update PrefixList.fromLookup() to expect the result fr…

0bce2f0

…om CcApi context provider has exactly one resource (#34557) Reverts #34199

chore(release): 2.199.0

0810f33

aws-cdk-automation added auto-approve pr/no-squash This PR should be merged instead of squash-merging it labels May 27, 2025

aws-cdk-automation requested a review from a team May 27, 2025 12:40

github-actions bot added the p2 label May 27, 2025

github-actions bot approved these changes May 27, 2025

View reviewed changes

chore: update analytics metadata blueprints

bba02df

github-actions bot requested a review from a team as a code owner May 27, 2025 12:42

alvazjor added pr/do-not-merge This PR should not be merged at this time. and removed pr/do-not-merge This PR should not be merged at this time. labels May 27, 2025

alvazjor added 2 commits May 27, 2025 16:16

chore: Update CHANGELOG.v2.md

1942bcd

updating changelog message

chore: Update CHANGELOG.v2.alpha.md

0c5930d

Updated changelog message

iliapolo force-pushed the bump/2.199.0 branch from def86e0 to 0c5930d Compare May 27, 2025 13:17

alvazjor removed the pr/do-not-merge This PR should not be merged at this time. label May 27, 2025

mergify bot merged commit e4fc2ac into v2-release May 27, 2025
17 checks passed

mergify bot deleted the bump/2.199.0 branch May 27, 2025 13:47

github-actions bot locked as resolved and limited conversation to collaborators May 27, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

chore(release): 2.199.0 #34561

chore(release): 2.199.0 #34561

Uh oh!

aws-cdk-automation commented May 27, 2025 •

edited

Loading

Uh oh!

aws-cdk-automation commented May 27, 2025

Uh oh!

mergify bot commented May 27, 2025

Uh oh!

Uh oh!

github-actions bot commented May 27, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

12 participants

chore(release): 2.199.0 #34561

chore(release): 2.199.0 #34561

Uh oh!

Conversation

aws-cdk-automation commented May 27, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

aws-cdk-automation commented May 27, 2025

AWS CodeBuild CI Report

Uh oh!

mergify bot commented May 27, 2025

Uh oh!

Uh oh!

github-actions bot commented May 27, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

12 participants

aws-cdk-automation commented May 27, 2025 •

edited

Loading