chore(release): 2.151.0 #31005
Merged
chore(release): 2.151.0 #31005
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
### Issue # (if applicable) ### Reason for this change The `description` property existed in the L1 construct but was not present in the L2 construct ### Description of changes Add the `description` property for `HttpStage` and `WebSocketStage`, which was missing in the L2 construct. ### Description of how you validated changes I Added both unit test and integration tests. ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https:/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https:/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*
…meter string (#30902) ### Issue # (if applicable) Closes #30798. ### Reason for this change `fromServiceArnWithCluster()` function can't handle token value correctly. ### Description of changes Replace ``` const resourceName = arn.resourceName; ``` With ``` Arn.extractResourceName() ``` because the function above has the ability to handle token values. ### Description of how you validated changes - Updated the unit test - Manually verified the ECS cluster resource was used in the code pipeline when using the SSM parameter. ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https:/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https:/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) N/A ### Reason for this change Amazon EventBridge supports Customer Managed Key for Event Bus since 2024/5. But current L2 Construct does not support CMK. For more information, see [Amazon EventBridge now supports Customer Managed Keys (CMK) for Event Buses](https://aws.amazon.com/about-aws/whats-new/2024/05/amazon-eventbridge-cmk-event-buses/?nc1=h_ls). ### Description of changes Add `kmsKey` property to the `EventBus` class ### Description of how you validated changes Add unit tests and integ tests. ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https:/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https:/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 #30751. ### Reason for this change `runTask` on `${taskDefinitionFamilyArn}` is no longer relevant (see validation errors in the linked issue. This was currently disabled with a FF. This PR removes the permission entirely, and removes the FF. ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https:/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https:/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*
…30298) ### Issue # (if applicable) Closes #29229. ### Reason for this change When trying to use JsonPath to specify the S3 URIs that BedrockInvokeModel will read from and write from, you get an error. Example of the Error message: `jsii.errors.JavaScriptError: Error: Field references must be the entire string, cannot concatenate them (found 's3://${Token[prompt_bucket.348]}/${Token[prompt_key.349]}')` ### Description of changes Extended the inputPath property to be allowed as an input value for the task state. Instead of adding a new S3Uri props in current `BedrockInvokeModelProps` as proposed in the original issue, leveraged the `inputPath` property that is already defined in `sfn.TaskStateBaseProps` and being extended by `BedrockInvokeModelInputProps` and `BedrockInvokeModelOutputProps` **Limitation:** We cannot limit the resource policy to specific input token for which the value might be coming from the prompt, so had to keep it as [*] here. ### Description of how you validated changes Added unit tests. Successful deployment of integration tests in the account. ### Checklist - [x] Unit Tests - [x] Integration Tests - [x] Updated ReadMe - [x] My code adheres to the [CONTRIBUTING GUIDE](https:/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https:/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*
…0837) ### Issue # (if applicable) ### Reason for this change The change introduces the `versionDescription` property to the `LaunchTemplate` ### Description of changes - Add the `versionDescription` property for `LaunchTemplateProps`, which was missing in the L2 construct. - Add validation for character limit ### Description of how you validated changes I Added a unit test for launch template and added the `versionDescription` property in the integration tests. ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https:/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https:/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*
update `framework-integ/test/aws-eks/test/integ.eks-helm-asset.ts` that might fail in some cases: 1. set `aws.region` for the helm charts to ensure successful helm deployment 2. make sure each helm charts assertion use different chart source to avoid conflict 3. update the snapshots ### Issue # (if applicable) Closes #<issue number here>. ### Reason for this change ### Description of changes ### Description of how you validated changes ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https:/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https:/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) N/A ### Reason for this change Remind users to submit security-related issues using the existing mechanism in GitHub. ### Description of changes Add note to the top of the template ### Description of how you validated changes Previewed the template in GitHub (can't find a way to actually view the updated template locally) ### Checklist - [n/a] My code adheres to the [CONTRIBUTING GUIDE](https:/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https:/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*
### Reason for this change
Documentation does not state clearly that feature needs to be manually enabled when using Postgres
Example :
The following code will fail with the error message
```ts
const cluster = new rds.DatabaseCluster(this, 'Database', {
engine: rds.DatabaseClusterEngine.auroraPostgres({version: AuroraPostgresEngineVersion.of('12.7','12')}),
writer: rds.ClusterInstance.provisioned('writer', {
instanceType: ec2.InstanceType.of(ec2.InstanceClass.R6G, ec2.InstanceSize.XLARGE4),
}),
serverlessV2MinCapacity: 6.5,
serverlessV2MaxCapacity: 64,
s3ImportRole: sampleRole
});
```
Will fail with this error message :`Error: s3Import is not supported for Postgres version: 12.7. Use a version that supports the s3Import feature`
But the thing is that 12.7 does support it ! The real problem here is that the feature needs to be enabled as such
```ts
const cluster = new rds.DatabaseCluster(this, 'Database', {
engine: rds.DatabaseClusterEngine.auroraPostgres({version: AuroraPostgresEngineVersion.of('12.7','12', {s3Export: true, s3Import:true})}),
writer: rds.ClusterInstance.provisioned('writer', {
instanceType: ec2.InstanceType.of(ec2.InstanceClass.R6G, ec2.InstanceSize.XLARGE4),
}),
serverlessV2MinCapacity: 6.5,
serverlessV2MaxCapacity: 64,
s3ImportRole: sampleRole
});
```
### Description of changes
Small update to Readme.md and inline TSdoc
### Description of how you validated changes
None
### Checklist
- [x] My code adheres to the [CONTRIBUTING GUIDE](https:/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https:/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) ### Reason for this change Lock conversations on closed issues and PRs to make sure important comments are not left on closed items and no one would be able to see it. Force people to create new issues instead. ### Description of changes Lock conversations. ### Description of how you validated changes Tested in a forked repo and it works correctly. ### Checklist - [ ] My code adheres to the [CONTRIBUTING GUIDE](https:/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https:/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*
#30659) ### Reason for this change ALB supports metrics for specific load balancer generated 5XX level error metrics. https://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-cloudwatch-metrics.html However, they are currently not included in `HttpCodeElb`, so the `metrics.httpCodeElb` method is not available and `metrics.custom` must be used. ```ts let alb: IApplicationLoadBalancer; alb.metrics.httpCodeElb(HttpCodeElb.ELB_5XX_COUNT); // we can do this alb.metrics.httpCodeElb(HttpCodeElb.ELB_500_COUNT); // currently we cannot do this alb.metrics.custom("HTTPCode_ELB_500_Count"); ``` Adding the metric names to `HttpCodeElb` makes it easier to understand as it can be configured in the same way as `HTTPCode_ELB_5XX_Count`. ### Description of changes Add metrics names to `HttpCodeElb`. ### Description of how you validated changes ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https:/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https:/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) Fix the misleading message in #30941 ### Reason for this change Update message left by GHA ### Description of changes Since we lock conversations, we should update the message to be more accurate. ### Description of how you validated changes Tested in private fork with GHA. ### Checklist - [ ] My code adheres to the [CONTRIBUTING GUIDE](https:/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https:/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 Meta Llama 3.1 model. Ref * https://aws.amazon.com/about-aws/whats-new/2024/07/meta-llama-3-1-generative-ai-models-amazon-bedrock/ * https://docs.aws.amazon.com/bedrock/latest/userguide/model-ids.html ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https:/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https:/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) N/A ### Reason for this change Add `ashishdhingra` to ignore list for merit badger. ### Description of changes Add `ashishdhingra` to ignore list for merit badger. ### Description of how you validated changes ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https:/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https:/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*
Bumps [requirejs](https:/jrburke/r.js) from 2.3.6 to 2.3.7. <details> <summary>Commits</summary> <ul> <li><a href="https:/requirejs/r.js/commit/1874a29ad51a395703629e3aece5d094a791b7ea"><code>1874a29</code></a> Rev to 2.3.7</li> <li><a href="https:/requirejs/r.js/commit/152f450a84bf6be4192c828cbea2515eeb2d9588"><code>152f450</code></a> Merge pull request <a href="https://redirect.github.com/jrburke/r.js/issues/1016">#1016</a> from requirejs/jr/1854-pollution</li> <li><a href="https:/requirejs/r.js/commit/ecc356a219b79075c562d002c21d18436482e15a"><code>ecc356a</code></a> Fixes <a href="https://redirect.github.com/requirejs/requirejs/issues/1854">requirejs/requirejs#1854</a>, pollution</li> <li><a href="https:/requirejs/r.js/commit/acec5366eb9094e670b6d1a87457634e74d6384e"><code>acec536</code></a> SECURITY.md</li> <li>See full diff in <a href="https:/jrburke/r.js/compare/2.3.6...2.3.7">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https:/aws/aws-cdk/network/alerts). </details>
### Issue # (if applicable) Closes #30609 ### Reason for this change To refactor the retrievalRole creation logic. ### Description of changes ### Description of how you validated changes Unit tests: 1. configuration with retrievalRole undefined from bucket source should create a new role 2. configuration with retrievalRole defined should NOT create a new role and should use the passed role for the retrievalRoleArn 3. configuration with retrievalRole undefined from CodePipeline source should NOT create a new role Integ test: 1. update the existing integ test to assert a use case where the retrievalRole is provided. ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https:/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https:/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*
…um (#30314) ### Issue # (if applicable) Closes #30310 . ### Reason for this change Missing enum option of `otel-sqs-handler` ### Description of changes Add `SQS_HANDLER` option ### Description of how you validated changes I verified that the correct values were set in the environment variables after deploying. Since only an enum option was added, I determined that adding unit tests or integration tests was unnecessary. ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https:/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https:/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 #NA. ### Reason for this change Current link is broken in the contributing guide and gives 404. ### Description of changes Fix broken link to point to correct AWS RFC repo. ### Description of how you validated changes ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https:/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https:/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 Mistral Large 2 foundation model. Ref: * https://aws.amazon.com/about-aws/whats-new/2024/07/mistral-large-2-foundation-model-amazon-bedrock/ * https://docs.aws.amazon.com/bedrock/latest/userguide/model-ids.html <img width="724" alt="image" src="https:/user-attachments/assets/7c880ed2-eb1f-4aa8-bf8b-bb51de836a29"> ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https:/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https:/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*
### Reason for this change This Updated. https://aws.amazon.com/jp/about-aws/whats-new/2024/07/amazon-cloudfront-managed-cache-policies-web-applications/ ### Description of changes Adding Managed Cache Policies. - [UseOriginCacheControlHeaders](https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/using-managed-cache-policies.html#managed-cache-policy-origin-cache-headers) - [UseOriginCacheControlHeaders-QueryStrings](https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/using-managed-cache-policies.html#managed-cache-policy-origin-cache-headers-query-strings) ### Description of how you validated changes no ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https:/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https:/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*
…30926) ### Description of changes If we don't specify the tag parameter for fromEcrRepository method, `latest` is used as default value. https:/aws/aws-cdk/blob/c8e5924bbc83b91b929838518f4955dd3bbb884f/packages/aws-cdk-lib/aws-ecs/lib/container-image.ts#L19-L24 However, currently this behavior is not described in document. https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_ecs.ContainerImage.html#static-fromwbrecrwbrrepositoryrepository-tag I'm adding the description regarding this default value. ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https:/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https:/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)
--
### Reason for this change
Display errors before deploying
### Description of changes
- Implement length check for displayName (maximum 100 characters long)
- [AWS::SNS::Topic](https://docs.aws.amazon.com/ja_jp/AWSCloudFormation/latest/UserGuide/aws-resource-sns-topic.html#cfn-sns-topic-displayname)
### Description of how you validated changes
I added unit tests and confirmed all tests passed.
### Checklist
- [x] My code adheres to the [CONTRIBUTING GUIDE](https:/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https:/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 #<issue number here>. ### Reason for this change G6 instances were announced for general availability in april 2024 [Announcing general availability of Amazon EC2 G6 instances](https://aws.amazon.com/about-aws/whats-new/2024/04/general-availability-amazon-ec2-g6-instances/) [G6 instances can be used for sagemaker notebooks and endpoints](https://aws.amazon.com/about-aws/whats-new/2024/05/amazon-sagemaker-notebooks-g6-instance-types/)  I would like to add the instance type in cdk so that cdk app can spin up g6 instance as needed ### Description of changes defined new instanceTypes following the same convention as G5 instances ### Description of how you validated changes minor change and existing file does not have unit tests ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https:/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https:/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*
…ions (#30896) ### Issue # (if applicable) Closes #30862. ### Reason for this change Per [TagResource](https://docs.aws.amazon.com/efs/latest/ug/API_TagResource.html), the operation requires permissions for the `elasticfilesystem:TagResource` action. Also per [AWS managed policies for Amazon EFS](https://docs.aws.amazon.com/efs/latest/ug/security-iam-awsmanpol.html), all the `Action`(s) are prefixed with `elasticfilesystem:` (not `efs`). ### Description of changes Updates the `iamServiceMap` that maintains list of services having mapping to IAM policy prefix names. ### Description of how you validated changes Added unit test and integration test (along with snapshot). ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https:/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https:/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*
…utomatic Target Weights for alb (#30542) ### Issue # (if applicable) Closes #29969 ### Reason for this change Application Load Balancer supports Weight Random routing Algorithm and Automatic Target Weights. ([link](https://aws.amazon.com/about-aws/whats-new/2023/11/application-load-balancer-availability-target-weights/)) But current L2 construct does not support it. ### Description of changes * Add `weighted_random` algorithm to ENUM. * Add a flag for setting Automatic Target Weights anomaly mitigation. ### Description of how you validated changes Add unit tests and integ tests. ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https:/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https:/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*
…E compatible task definitions (#30166) ### Issue # (if applicable) Closes #22216 ### Reason for this change Adds a validation that would point out invalid CPU - Memory limits for a FARGATE compatible task definition. This is based on the document https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-cpu-memory-error.html ### Description of changes Added a `validateFargateTaskDefinitionMemoryCpu` method in the base task definition and run this validation when a task definition has FARGATE in requiresCompatibilities. This is in line with the ECS requirement that even if a task definition has EC2 compatibility (along with FARGATE), FARGATE validations apply ### Description of how you validated changes Validated the changes by providing incorrect as well as correct values, fixed all the invalid combinations that are present in the unit tests ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https:/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https:/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*
### Reason for this change VPC Flow log added several fields regarding ECS in v7. https://aws.amazon.com/about-aws/whats-new/2024/05/amazon-vpc-flow-logs-extends-support-ecs/ https://docs.aws.amazon.com/vpc/latest/userguide/flow-logs.html#flow-log-records This change supports these fields in L2 construct. ### Description of changes Added new log fields to `LogFormat` class. ### Description of how you validated changes Unit test and integ test are both updated. Changes of logFormat configuration requires resource replacement, which is necessary. It seems like that in order to enable these ecs related log fields, at least one ECS cluster is required in the VPC. So a new ECS cluster is also created in the integ test. ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https:/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https:/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*
…ationMetrics property (#30979) ### Issue # (if applicable) Closes #30968. ### Reason for this change The default value of `ConfigurationSet.reputationMetrics` if not set in the CDK stack is actually `true` (refer #30968 (comment) for details). ### Description of changes Corrected default value as `true` for `ConfigurationSet.reputationMetrics` property in documentation comment. ### Description of how you validated changes N/A ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https:/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https:/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) ### Reason for this change Add comments and enhance the code around method authorizers. ### Description of changes No behavioural change, should only include comments, variables name update and re-ordering. ### Description of how you validated changes All existing tests pass. ### Checklist - [ ] My code adheres to the [CONTRIBUTING GUIDE](https:/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https:/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*
Updates the L1 CloudFormation resource definitions with the latest changes from `@aws-cdk/aws-service-spec` **L1 CloudFormation resource definition changes:** ``` ├[~] service aws-backup │ └ resources │ └[~] resource AWS::Backup::BackupVault │ └ properties │ └ BackupVaultName: (documentation changed) ├[~] service aws-cleanrooms │ └ resources │ └[~] resource AWS::CleanRooms::PrivacyBudgetTemplate │ ├ properties │ │ └ Parameters: (documentation changed) │ └ types │ └[~] type Parameters │ └ - documentation: Specifies the epislon and noise parameters for the privacy budget template. │ + documentation: Specifies the epsilon and noise parameters for the privacy budget template. ├[~] service aws-cloudformation │ └ resources │ └[~] resource AWS::CloudFormation::StackSet │ └ types │ └[~] type DeploymentTargets │ └ properties │ └ AccountFilterType: (documentation changed) ├[~] service aws-cloudfront │ └ resources │ ├[~] resource AWS::CloudFront::ContinuousDeploymentPolicy │ │ └ types │ │ ├[~] type SingleHeaderPolicyConfig │ │ │ ├ - documentation: undefined │ │ │ │ + documentation: Defines a single header policy for a CloudFront distribution. │ │ │ │ > This property is legacy. We recommend that you use [TrafficConfig](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-cloudfront-continuousdeploymentpolicy-trafficconfig.html) and specify the [SingleHeaderConfig](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-cloudfront-continuousdeploymentpolicy-trafficconfig.html#cfn-cloudfront-continuousdeploymentpolicy-trafficconfig-singleheaderconfig) property instead. │ │ │ └ properties │ │ │ ├ Header: (documentation changed) │ │ │ └ Value: (documentation changed) │ │ └[~] type SingleWeightPolicyConfig │ │ ├ - documentation: undefined │ │ │ + documentation: Configure a policy that CloudFront uses to route requests to different origins or use different cache settings, based on the weight assigned to each option. │ │ │ > This property is legacy. We recommend that you use [TrafficConfig](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-cloudfront-continuousdeploymentpolicy-trafficconfig.html) and specify the [SingleWeightConfig](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-cloudfront-continuousdeploymentpolicy-trafficconfig.html#cfn-cloudfront-continuousdeploymentpolicy-trafficconfig-singleweightconfig) property instead. │ │ └ properties │ │ ├ SessionStickinessConfig: (documentation changed) │ │ └ Weight: (documentation changed) │ └[~] resource AWS::CloudFront::Distribution │ └ types │ ├[~] type DistributionConfig │ │ └ properties │ │ ├ CNAMEs: (documentation changed) │ │ ├ CustomOrigin: (documentation changed) │ │ └ S3Origin: (documentation changed) │ ├[~] type LegacyCustomOrigin │ │ ├ - documentation: undefined │ │ │ + documentation: A custom origin. A custom origin is any origin that is *not* an Amazon S3 bucket, with one exception. An Amazon S3 bucket that is [configured with static website hosting](https://docs.aws.amazon.com/AmazonS3/latest/dev/WebsiteHosting.html) *is* a custom origin. │ │ │ > This property is legacy. We recommend that you use [Origin](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-cloudfront-distribution-origin.html) instead. │ │ └ properties │ │ ├ DNSName: (documentation changed) │ │ ├ HTTPPort: (documentation changed) │ │ ├ HTTPSPort: (documentation changed) │ │ ├ OriginProtocolPolicy: (documentation changed) │ │ └ OriginSSLProtocols: (documentation changed) │ └[~] type LegacyS3Origin │ ├ - documentation: undefined │ │ + documentation: The origin as an Amazon S3 bucket. │ │ > This property is legacy. We recommend that you use [Origin](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-cloudfront-distribution-origin.html) instead. │ └ properties │ ├ DNSName: (documentation changed) │ └ OriginAccessIdentity: (documentation changed) ├[~] service aws-cloudtrail │ └ resources │ ├[~] resource AWS::CloudTrail::EventDataStore │ │ └ types │ │ └[~] type AdvancedFieldSelector │ │ └ properties │ │ └ Field: (documentation changed) │ └[~] resource AWS::CloudTrail::Trail │ └ types │ └[~] type AdvancedFieldSelector │ └ properties │ └ Field: (documentation changed) ├[~] service aws-ec2 │ └ resources │ └[~] resource AWS::EC2::IPAMPool │ └ properties │ └ Locale: (documentation changed) ├[~] service aws-entityresolution │ └ resources │ ├[~] resource AWS::EntityResolution::IdMappingWorkflow │ │ ├ properties │ │ │ └ IdMappingTechniques: (documentation changed) │ │ └ types │ │ ├[~] type IdMappingTechniques │ │ │ └ - documentation: An object which defines the ID mapping techniques and provider configurations. │ │ │ + documentation: An object which defines the ID mapping technique and any additional configurations. │ │ └[~] type IdMappingWorkflowInputSource │ │ └ properties │ │ ├ InputSourceARN: (documentation changed) │ │ └ Type: (documentation changed) │ ├[~] resource AWS::EntityResolution::IdNamespace │ │ ├ properties │ │ │ └ Type: (documentation changed) │ │ └ types │ │ ├[~] type IdNamespaceIdMappingWorkflowProperties │ │ │ └ - documentation: An object containing `IdMappingType` and `ProviderProperties` . │ │ │ + documentation: An object containing `IdMappingType` , `ProviderProperties` , and `RuleBasedProperties` . │ │ └[~] type IdNamespaceInputSource │ │ └ properties │ │ └ InputSourceARN: (documentation changed) │ ├[~] resource AWS::EntityResolution::MatchingWorkflow │ │ └ types │ │ └[~] type RuleBasedProperties │ │ ├ - documentation: An object which defines the list of matching rules to run and has a field `Rules` , which is a list of rule objects. │ │ │ + documentation: An object which defines the list of matching rules to run in a matching workflow. RuleBasedProperties contain a `Rules` field, which is a list of rule objects. │ │ └ properties │ │ └ AttributeMatchingModel: (documentation changed) │ └[~] resource AWS::EntityResolution::SchemaMapping │ └ types │ └[~] type SchemaInputAttribute │ ├ - documentation: An object containing `FieldName` , `Type` , `GroupName` , `MatchKey` , and `SubType` . │ │ + documentation: An object containing `FieldName` , `Type` , `GroupName` , `MatchKey` , `Hashing` , and `SubType` . │ └ properties │ └ MatchKey: (documentation changed) ├[~] service aws-iam │ └ resources │ ├[~] resource AWS::IAM::ManagedPolicy │ │ └ attributes │ │ ├ AttachmentCount: (documentation changed) │ │ ├ CreateDate: (documentation changed) │ │ ├ DefaultVersionId: (documentation changed) │ │ ├ IsAttachable: (documentation changed) │ │ ├ PermissionsBoundaryUsageCount: (documentation changed) │ │ ├ PolicyId: (documentation changed) │ │ └ UpdateDate: (documentation changed) │ └[~] resource AWS::IAM::OIDCProvider │ └ properties │ └ ThumbprintList: (documentation changed) ├[~] service aws-iotsitewise │ └ resources │ ├[~] resource AWS::IoTSiteWise::AssetModel │ │ └ properties │ │ └ AssetModelName: (documentation changed) │ └[~] resource AWS::IoTSiteWise::Gateway │ └ properties │ └ GatewayName: (documentation changed) ├[~] service aws-mwaa │ └ resources │ └[~] resource AWS::MWAA::Environment │ └ properties │ └ AirflowVersion: (documentation changed) ├[~] service aws-pipes │ └ resources │ └[~] resource AWS::Pipes::Pipe │ └ types │ └[~] type SelfManagedKafkaAccessConfigurationVpc │ └ properties │ └ SecurityGroup: (documentation changed) ├[~] service aws-rds │ └ resources │ ├[~] resource AWS::RDS::DBCluster │ │ ├ - documentation: The `AWS::RDS::DBCluster` resource creates an Amazon Aurora DB cluster or Multi-AZ DB cluster. │ │ │ For more information about creating an Aurora DB cluster, see [Creating an Amazon Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.CreateInstance.html) in the *Amazon Aurora User Guide* . │ │ │ For more information about creating a Multi-AZ DB cluster, see [Creating a Multi-AZ DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/create-multi-az-db-cluster.html) in the *Amazon RDS User Guide* . │ │ │ > You can only create this resource in AWS Regions where Amazon Aurora or Multi-AZ DB clusters are supported. │ │ │ *Updating DB clusters* │ │ │ When properties labeled " *Update requires:* [Replacement](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-update-behaviors.html#update-replacement) " are updated, AWS CloudFormation first creates a replacement DB cluster, then changes references from other dependent resources to point to the replacement DB cluster, and finally deletes the old DB cluster. │ │ │ > We highly recommend that you take a snapshot of the database before updating the stack. If you don't, you lose the data when AWS CloudFormation replaces your DB cluster. To preserve your data, perform the following procedure: │ │ │ > │ │ │ > - Deactivate any applications that are using the DB cluster so that there's no activity on the DB instance. │ │ │ > - Create a snapshot of the DB cluster. For more information, see [Creating a DB Cluster Snapshot](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_CreateSnapshotCluster.html) . │ │ │ > - If you want to restore your DB cluster using a DB cluster snapshot, modify the updated template with your DB cluster changes and add the `SnapshotIdentifier` property with the ID of the DB cluster snapshot that you want to use. │ │ │ > │ │ │ > After you restore a DB cluster with a `SnapshotIdentifier` property, you must specify the same `SnapshotIdentifier` property for any future updates to the DB cluster. When you specify this property for an update, the DB cluster is not restored from the DB cluster snapshot again, and the data in the database is not changed. However, if you don't specify the `SnapshotIdentifier` property, an empty DB cluster is created, and the original DB cluster is deleted. If you specify a property that is different from the previous snapshot restore property, a new DB cluster is restored from the specified `SnapshotIdentifier` property, and the original DB cluster is deleted. │ │ │ > - Update the stack. │ │ │ Currently, when you are updating the stack for an Aurora Serverless DB cluster, you can't include changes to any other properties when you specify one of the following properties: `PreferredBackupWindow` , `PreferredMaintenanceWindow` , and `Port` . This limitation doesn't apply to provisioned DB clusters. │ │ │ For more information about updating other properties of this resource, see `[ModifyDBCluster](https://docs.aws.amazon.com//AmazonRDS/latest/APIReference/API_ModifyDBCluster.html)` . For more information about updating stacks, see [AWS CloudFormation Stacks Updates](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks.html) . │ │ │ *Deleting DB clusters* │ │ │ The default `DeletionPolicy` for `AWS::RDS::DBCluster` resources is `Snapshot` . For more information about how AWS CloudFormation deletes resources, see [DeletionPolicy Attribute](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-attribute-deletionpolicy.html) . │ │ │ + documentation: The `AWS::RDS::DBCluster` resource creates an Amazon Aurora DB cluster or Multi-AZ DB cluster. │ │ │ For more information about creating an Aurora DB cluster, see [Creating an Amazon Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.CreateInstance.html) in the *Amazon Aurora User Guide* . │ │ │ For more information about creating a Multi-AZ DB cluster, see [Creating a Multi-AZ DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/create-multi-az-db-cluster.html) in the *Amazon RDS User Guide* . │ │ │ > You can only create this resource in AWS Regions where Amazon Aurora or Multi-AZ DB clusters are supported. │ │ │ *Updating DB clusters* │ │ │ When properties labeled " *Update requires:* [Replacement](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-update-behaviors.html#update-replacement) " are updated, AWS CloudFormation first creates a replacement DB cluster, then changes references from other dependent resources to point to the replacement DB cluster, and finally deletes the old DB cluster. │ │ │ > We highly recommend that you take a snapshot of the database before updating the stack. If you don't, you lose the data when AWS CloudFormation replaces your DB cluster. To preserve your data, perform the following procedure: │ │ │ > │ │ │ > - Deactivate any applications that are using the DB cluster so that there's no activity on the DB instance. │ │ │ > - Create a snapshot of the DB cluster. For more information, see [Creating a DB cluster snapshot](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_CreateSnapshotCluster.html) . │ │ │ > - If you want to restore your DB cluster using a DB cluster snapshot, modify the updated template with your DB cluster changes and add the `SnapshotIdentifier` property with the ID of the DB cluster snapshot that you want to use. │ │ │ > │ │ │ > After you restore a DB cluster with a `SnapshotIdentifier` property, you must specify the same `SnapshotIdentifier` property for any future updates to the DB cluster. When you specify this property for an update, the DB cluster is not restored from the DB cluster snapshot again, and the data in the database is not changed. However, if you don't specify the `SnapshotIdentifier` property, an empty DB cluster is created, and the original DB cluster is deleted. If you specify a property that is different from the previous snapshot restore property, a new DB cluster is restored from the specified `SnapshotIdentifier` property, and the original DB cluster is deleted. │ │ │ > - Update the stack. │ │ │ Currently, when you are updating the stack for an Aurora Serverless DB cluster, you can't include changes to any other properties when you specify one of the following properties: `PreferredBackupWindow` , `PreferredMaintenanceWindow` , and `Port` . This limitation doesn't apply to provisioned DB clusters. │ │ │ For more information about updating other properties of this resource, see `[ModifyDBCluster](https://docs.aws.amazon.com//AmazonRDS/latest/APIReference/API_ModifyDBCluster.html)` . For more information about updating stacks, see [AWS CloudFormation Stacks Updates](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks.html) . │ │ │ *Deleting DB clusters* │ │ │ The default `DeletionPolicy` for `AWS::RDS::DBCluster` resources is `Snapshot` . For more information about how AWS CloudFormation deletes resources, see [DeletionPolicy Attribute](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-attribute-deletionpolicy.html) . │ │ └ properties │ │ ├ BacktrackWindow: (documentation changed) │ │ └ Tags: (documentation changed) │ ├[~] resource AWS::RDS::DBClusterParameterGroup │ │ ├ - documentation: The `AWS::RDS::DBClusterParameterGroup` resource creates a new Amazon RDS DB cluster parameter group. │ │ │ For information about configuring parameters for Amazon Aurora DB clusters, see [Working with parameter groups](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_WorkingWithParamGroups.html) in the *Amazon Aurora User Guide* . │ │ │ > If you apply a parameter group to a DB cluster, then its DB instances might need to reboot. This can result in an outage while the DB instances are rebooting. │ │ │ > │ │ │ > If you apply a change to parameter group associated with a stopped DB cluster, then the update stack waits until the DB cluster is started. │ │ │ + documentation: The `AWS::RDS::DBClusterParameterGroup` resource creates a new Amazon RDS DB cluster parameter group. │ │ │ For information about configuring parameters for Amazon Aurora DB clusters, see [Working with parameter groups](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_WorkingWithParamGroups.html) in the *Amazon Aurora User Guide* . │ │ │ > If you apply a parameter group to a DB cluster, then its DB instances might need to reboot. This can result in an outage while the DB instances are rebooting. │ │ │ > │ │ │ > If you apply a change to parameter group associated with a stopped DB cluster, then the updated stack waits until the DB cluster is started. │ │ └ properties │ │ ├ DBClusterParameterGroupName: (documentation changed) │ │ ├ Description: (documentation changed) │ │ ├ Family: (documentation changed) │ │ └ Tags: (documentation changed) │ ├[~] resource AWS::RDS::DBInstance │ │ └ properties │ │ ├ DBClusterIdentifier: (documentation changed) │ │ ├ DBSnapshotIdentifier: (documentation changed) │ │ ├ DBSubnetGroupName: (documentation changed) │ │ ├ DeletionProtection: (documentation changed) │ │ ├ MonitoringInterval: (documentation changed) │ │ ├ MultiAZ: (documentation changed) │ │ ├ Port: (documentation changed) │ │ └ Tags: (documentation changed) │ ├[~] resource AWS::RDS::DBParameterGroup │ │ └ properties │ │ ├ Family: (documentation changed) │ │ ├ Parameters: (documentation changed) │ │ └ Tags: (documentation changed) │ ├[~] resource AWS::RDS::DBProxy │ │ ├ properties │ │ │ └ EngineFamily: (documentation changed) │ │ ├ attributes │ │ │ ├ DBProxyArn: (documentation changed) │ │ │ └ Endpoint: (documentation changed) │ │ └ types │ │ ├[~] type AuthFormat │ │ │ └ properties │ │ │ ├ AuthScheme: (documentation changed) │ │ │ └ IAMAuth: (documentation changed) │ │ └[~] type TagFormat │ │ ├ - documentation: Metadata assigned to a DB proxy consisting of a key-value pair. │ │ │ + documentation: Metadata assigned to an Amazon RDS resource consisting of a key-value pair. │ │ │ For more information, see [Tagging Amazon RDS Resources](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_Tagging.html) in the *Amazon RDS User Guide* or [Tagging Amazon Aurora and Amazon RDS Resources](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_Tagging.html) in the *Amazon Aurora User Guide* . │ │ └ properties │ │ ├ Key: (documentation changed) │ │ └ Value: (documentation changed) │ ├[~] resource AWS::RDS::DBProxyEndpoint │ │ ├ properties │ │ │ └ TargetRole: (documentation changed) │ │ ├ attributes │ │ │ ├ DBProxyEndpointArn: (documentation changed) │ │ │ ├ Endpoint: (documentation changed) │ │ │ ├ IsDefault: (documentation changed) │ │ │ └ VpcId: (documentation changed) │ │ └ types │ │ └[~] type TagFormat │ │ ├ - documentation: Metadata assigned to a DB proxy endpoint consisting of a key-value pair. │ │ │ + documentation: Metadata assigned to an Amazon RDS resource consisting of a key-value pair. │ │ │ For more information, see [Tagging Amazon RDS Resources](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_Tagging.html) in the *Amazon RDS User Guide* or [Tagging Amazon Aurora and Amazon RDS Resources](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_Tagging.html) in the *Amazon Aurora User Guide* . │ │ └ properties │ │ ├ Key: (documentation changed) │ │ └ Value: (documentation changed) │ ├[~] resource AWS::RDS::DBProxyTargetGroup │ │ └ properties │ │ └ ConnectionPoolConfigurationInfo: (documentation changed) │ ├[~] resource AWS::RDS::DBSecurityGroup │ │ └ properties │ │ ├ EC2VpcId: (documentation changed) │ │ └ Tags: (documentation changed) │ ├[~] resource AWS::RDS::DBSubnetGroup │ │ └ properties │ │ ├ DBSubnetGroupName: (documentation changed) │ │ └ Tags: (documentation changed) │ ├[~] resource AWS::RDS::EventSubscription │ │ └ properties │ │ ├ SourceIds: (documentation changed) │ │ └ SourceType: (documentation changed) │ ├[~] resource AWS::RDS::Integration │ │ └ properties │ │ └ Tags: (documentation changed) │ └[~] resource AWS::RDS::OptionGroup │ └ properties │ ├ OptionConfigurations: (documentation changed) │ └ Tags: (documentation changed) ├[~] service aws-s3 │ └ resources │ └[~] resource AWS::S3::Bucket │ ├ properties │ │ └ VersioningConfiguration: (documentation changed) │ └ types │ └[~] type VersioningConfiguration │ └ - documentation: Describes the versioning state of an Amazon S3 bucket. For more information, see [PUT Bucket versioning](https://docs.aws.amazon.com/AmazonS3/latest/API/RESTBucketPUTVersioningStatus.html) in the *Amazon S3 API Reference* . │ + documentation: Describes the versioning state of an Amazon S3 bucket. For more information, see [PUT Bucket versioning](https://docs.aws.amazon.com/AmazonS3/latest/API/RESTBucketPUTVersioningStatus.html) in the *Amazon S3 API Reference* . │ > When you enable versioning on a bucket for the first time, it might take a short amount of time for the change to be fully propagated. We recommend that you wait for 15 minutes after enabling versioning before issuing write operations ( `PUT` or `DELETE` ) on objects in the bucket. └[~] service aws-stepfunctions └ resources └[~] resource AWS::StepFunctions::StateMachineAlias └ types └[~] type DeploymentPreference └ properties └ Alarms: (documentation changed) ```
…/@aws-cdk-testing/framework-integ/test/aws-eks/test/sdk-call-integ-test-docker-app/app (#30987) Bumps [fast-xml-parser](https:/NaturalIntelligence/fast-xml-parser) to 4.4.1 and updates ancestor dependency [@aws-sdk/client-s3](https:/aws/aws-sdk-js-v3/tree/HEAD/clients/client-s3). These dependencies need to be updated together. Updates `fast-xml-parser` from 4.2.5 to 4.4.1 <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https:/NaturalIntelligence/fast-xml-parser/blob/master/CHANGELOG.md">fast-xml-parser's changelog</a>.</em></p> <blockquote> <p>Note: If you find missing information about particular minor version, that version must have been changed without any functional change in this library.</p> <p><strong>4.4.1 / 2024-07-28</strong></p> <ul> <li>v5 fix: maximum length limit to currency value</li> <li>fix <a href="https://redirect.github.com/NaturalIntelligence/fast-xml-parser/issues/634">#634</a>: build attributes with oneListGroup and attributesGroupName (<a href="https://redirect.github.com/NaturalIntelligence/fast-xml-parser/issues/653">#653</a>)(By <a href="https:/a-rasin">Andreas Naziris</a>)</li> <li>fix: get oneListGroup to work as expected for array of strings (<a href="https://redirect.github.com/NaturalIntelligence/fast-xml-parser/issues/662">#662</a>)(By <a href="https:/a-rasin">Andreas Naziris</a>)</li> </ul> <p><strong>4.4.0 / 2024-05-18</strong></p> <ul> <li>fix <a href="https://redirect.github.com/NaturalIntelligence/fast-xml-parser/issues/654">#654</a>: parse attribute list correctly for self closing stop node.</li> <li>fix: validator bug when closing tag is not opened. (<a href="https://redirect.github.com/NaturalIntelligence/fast-xml-parser/issues/647">#647</a>) (By <a href="https:/RyosukeFukatani">Ryosuke Fukatani</a>)</li> <li>fix <a href="https://redirect.github.com/NaturalIntelligence/fast-xml-parser/issues/581">#581</a>: typings; return type of <code>tagValueProcessor</code> & <code>attributeValueProcessor</code> (<a href="https://redirect.github.com/NaturalIntelligence/fast-xml-parser/issues/582">#582</a>) (By <a href="">monholm</a>)</li> </ul> <p><strong>4.3.6 / 2024-03-16</strong></p> <ul> <li>Add support for parsing HTML numeric entities (<a href="https://redirect.github.com/NaturalIntelligence/fast-xml-parser/issues/645">#645</a>) (By <a href="https:/DerZade">Jonas Schade </a>)</li> </ul> <p><strong>4.3.5 / 2024-02-24</strong></p> <ul> <li>code for v5 is added for experimental use</li> </ul> <p><strong>4.3.4 / 2024-01-10</strong></p> <ul> <li>fix: Don't escape entities in CDATA sections (<a href="https://redirect.github.com/NaturalIntelligence/fast-xml-parser/issues/633">#633</a>) (By <a href="https:/wackbyte">wackbyte</a>)</li> </ul> <p><strong>4.3.3 / 2024-01-10</strong></p> <ul> <li>Remove unnecessary regex</li> </ul> <p><strong>4.3.2 / 2023-10-02</strong></p> <ul> <li>fix <code>jObj.hasOwnProperty</code> when give input is null (By <a href="https:/ardatan">Arda TANRIKULU</a>)</li> </ul> <p><strong>4.3.1 / 2023-09-24</strong></p> <ul> <li>revert back "Fix typings for builder and parser to make return type generic" to avoid failure of existing projects. Need to decide a common approach.</li> </ul> <p><strong>4.3.0 / 2023-09-20</strong></p> <ul> <li>Fix stopNodes to work with removeNSPrefix (<a href="https://redirect.github.com/NaturalIntelligence/fast-xml-parser/issues/607">#607</a>) (<a href="https://redirect.github.com/NaturalIntelligence/fast-xml-parser/issues/608">#608</a>) (By [Craig Andrews]<a href="https:/candrews">https:/candrews</a>))</li> <li>Fix <a href="https://redirect.github.com/NaturalIntelligence/fast-xml-parser/issues/610">#610</a> ignore properties set to Object.prototype</li> <li>Fix typings for builder and parser to make return type generic (By <a href="https:/sarahdayan">Sarah Dayan</a>)</li> </ul> <p><strong>4.2.7 / 2023-07-30</strong></p> <ul> <li>Fix: builder should set text node correctly when only textnode is present (<a href="https://redirect.github.com/NaturalIntelligence/fast-xml-parser/issues/589">#589</a>) (By <a href="https:/joneqian">qianqing</a>)</li> <li>Fix: Fix for null and undefined attributes when building xml (<a href="https://redirect.github.com/NaturalIntelligence/fast-xml-parser/issues/585">#585</a>) (<a href="https://redirect.github.com/NaturalIntelligence/fast-xml-parser/issues/598">#598</a>). A null or undefined value should be ignored. (By <a href="https:/cecia234">Eugenio Ceschia</a>)</li> </ul> <p><strong>4.2.6 / 2023-07-17</strong></p> <ul> <li>Fix: Remove trailing slash from jPath for self-closing tags (<a href="https://redirect.github.com/NaturalIntelligence/fast-xml-parser/issues/595">#595</a>) (By <a href="https:/m-radzikowski">Maciej Radzikowski</a>)</li> </ul> <p><strong>4.2.5 / 2023-06-22</strong></p> <ul> <li>change code implementation</li> </ul> <p><strong>4.2.4 / 2023-06-06</strong></p> <ul> <li>fix security bug</li> </ul> <p><strong>4.2.3 / 2023-06-05</strong></p> <ul> <li>fix security bug</li> </ul> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https:/NaturalIntelligence/fast-xml-parser/commit/d40e29cc4bbe637d7c95060b44f7a4d275facd01"><code>d40e29c</code></a> update package detail and browser bundles</li> <li><a href="https:/NaturalIntelligence/fast-xml-parser/commit/d0bfe8a3a2813a185f39591bbef222212d856164"><code>d0bfe8a</code></a> fix maxlength for currency value</li> <li><a href="https:/NaturalIntelligence/fast-xml-parser/commit/2c14fcf0482380646f67ba98ff658f11c914ac04"><code>2c14fcf</code></a> Update bug-report-or-unexpected-output.md</li> <li><a href="https:/NaturalIntelligence/fast-xml-parser/commit/acf610f25d75ece793c4e24b4673e60871c04341"><code>acf610f</code></a> fix <a href="https://redirect.github.com/NaturalIntelligence/fast-xml-parser/issues/634">#634</a>: build attributes with oneListGroup and attributesGroupName (<a href="https://redirect.github.com/NaturalIntelligence/fast-xml-parser/issues/653">#653</a>)</li> <li><a href="https:/NaturalIntelligence/fast-xml-parser/commit/931e91013b6ea6bb7425c3b1758dc50a6dfc730c"><code>931e910</code></a> fix: get oneListGroup to work as expected for array of strings (<a href="https://redirect.github.com/NaturalIntelligence/fast-xml-parser/issues/662">#662</a>)</li> <li><a href="https:/NaturalIntelligence/fast-xml-parser/commit/b8e40c842bf63b7d4d706f016d00e259cbc4379e"><code>b8e40c8</code></a> Update ISSUE_TEMPLATE.md</li> <li><a href="https:/NaturalIntelligence/fast-xml-parser/commit/a6265ba8563eac3080a48397dcbcd9c847b21df2"><code>a6265ba</code></a> chore: add trend image (<a href="https://redirect.github.com/NaturalIntelligence/fast-xml-parser/issues/658">#658</a>)</li> <li><a href="https:/NaturalIntelligence/fast-xml-parser/commit/db1c5484808b1100224c258a40d1b07057f1d054"><code>db1c548</code></a> redesign README.md</li> <li><a href="https:/NaturalIntelligence/fast-xml-parser/commit/338a2c62664f9c9474cf0ec9e47bdfc092ce7f5f"><code>338a2c6</code></a> Rename 1.Getting Started.md to 1.GettingStarted.md</li> <li><a href="https:/NaturalIntelligence/fast-xml-parser/commit/c762537495aa1c44c8d9088a0e2f6004b45116c7"><code>c762537</code></a> Rename v5 docs filenames (<a href="https://redirect.github.com/NaturalIntelligence/fast-xml-parser/issues/659">#659</a>)</li> <li>Additional commits viewable in <a href="https:/NaturalIntelligence/fast-xml-parser/compare/v4.2.5...v4.4.1">compare view</a></li> </ul> </details> <br /> Updates `@aws-sdk/client-s3` from 3.421.0 to 3.621.0 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https:/aws/aws-sdk-js-v3/releases"><code>@aws-sdk/client-s3</code>'s releases</a>.</em></p> <blockquote> <h2>v3.621.0</h2> <h4>3.621.0(2024-07-30)</h4> <h5>Chores</h5> <ul> <li><strong>codegen:</strong> <ul> <li>remove fast-xml-parser from AwsDependency (<a href="https://redirect.github.com/aws/aws-sdk-js-v3/pull/6328">#6328</a>) (<a href="https:/aws/aws-sdk-js-v3/commit/197bc7d8fe13abb07f09e2671b6ecd4cbe5d2ec6">197bc7d8</a>)</li> <li>bump smithy package versions (<a href="https://redirect.github.com/aws/aws-sdk-js-v3/pull/6329">#6329</a>) (<a href="https:/aws/aws-sdk-js-v3/commit/8dd7fb633c5333712bd18eb626fe1eb90939b0a7">8dd7fb63</a>)</li> </ul> </li> <li><strong>deps:</strong> bump fast-xml-parser from 4.2.5 to 4.4.1 (<a href="https://redirect.github.com/aws/aws-sdk-js-v3/pull/6330">#6330</a>) (<a href="https:/aws/aws-sdk-js-v3/commit/c547e234ac91baa3a3b1755889bcccf464775547">c547e234</a>)</li> </ul> <h5>Documentation Changes</h5> <ul> <li><strong>client-elasticache:</strong> Doc only update for changes to deletion API. (<a href="https:/aws/aws-sdk-js-v3/commit/3cf46f190a6421f0846d1bac819f1cd2f5a5d574">3cf46f19</a>)</li> <li><strong>client-workspaces:</strong> Removing multi-session as it isn't supported for pools (<a href="https:/aws/aws-sdk-js-v3/commit/01552b00bfc18dd1f08bc2b029af5389dae37b5f">01552b00</a>)</li> </ul> <h5>New Features</h5> <ul> <li><strong>clients:</strong> update client endpoints as of 2024-07-30 (<a href="https:/aws/aws-sdk-js-v3/commit/ecc97a25cbd88d79cb965400aec61892cf1d2976">ecc97a25</a>)</li> <li><strong>client-lex-models-v2:</strong> This release adds new capabilities to the AMAZON.QnAIntent: Custom prompting, Guardrails integration and ExactResponse support for Bedrock Knowledge Base. (<a href="https:/aws/aws-sdk-js-v3/commit/4d9c7a12e3b68a83156aa7dd063183cae1c11ed2">4d9c7a12</a>)</li> <li><strong>client-eventbridge:</strong> Add v2 smoke tests and smithy smokeTests trait for SDK testing. (<a href="https:/aws/aws-sdk-js-v3/commit/65290c8130eb3b5a581bdf77ce2da29858f3a7ad">65290c81</a>)</li> <li><strong>client-rolesanywhere:</strong> IAM RolesAnywhere now supports custom role session name on the CreateSession. This release adds the acceptRoleSessionName option to a profile to control whether a role session name will be accepted in a session request with a given profile. (<a href="https:/aws/aws-sdk-js-v3/commit/5bc30087750ef62b067fb310e7d4fd86c6021dae">5bc30087</a>)</li> <li><strong>client-cloudwatch-logs:</strong> Add v2 smoke tests and smithy smokeTests trait for SDK testing. (<a href="https:/aws/aws-sdk-js-v3/commit/88b6a41c4193e217b2f404b39f7db83d70efcf8e">88b6a41c</a>)</li> <li><strong>client-codepipeline:</strong> AWS CodePipeline V2 type pipelines now support stage level conditions to enable development teams to safely release changes that meet quality and compliance requirements. (<a href="https:/aws/aws-sdk-js-v3/commit/5e8b92d3ad100d0a2a75fbddb18205b6154c778c">5e8b92d3</a>)</li> <li><strong>client-elastic-load-balancing:</strong> Add v2 smoke tests and smithy smokeTests trait for SDK testing. (<a href="https:/aws/aws-sdk-js-v3/commit/6cbe7bf601f3ef926cd6bbf5ae5f48fb48ec0d6e">6cbe7bf6</a>)</li> <li><strong>client-tnb:</strong> This release adds Network Service Update, through which customers will be able to update their instantiated networks to a new network package. See the documentation for limitations. The release also enhances the Get network operation API to return parameter overrides used during the operation. (<a href="https:/aws/aws-sdk-js-v3/commit/cee6948a0b747b200aee7b1ead4d3b0840ef983e">cee6948a</a>)</li> <li><strong>client-auto-scaling:</strong> Increase the length limit for VPCZoneIdentifier from 2047 to 5000 (<a href="https:/aws/aws-sdk-js-v3/commit/23471630bc06deed7474a742d21ab245382080c2">23471630</a>)</li> <li><strong>client-appstream:</strong> Added support for Red Hat Enterprise Linux 8 on Amazon AppStream 2.0 (<a href="https:/aws/aws-sdk-js-v3/commit/bbb4450b91ceaf6140ec59f98fdd636117752181">bbb4450b</a>)</li> </ul> <h5>Bug Fixes</h5> <ul> <li>package.json <code>homepage</code> links to use the <code>main</code> branch (<a href="https://redirect.github.com/aws/aws-sdk-js-v3/pull/6336">#6336</a>) (<a href="https:/aws/aws-sdk-js-v3/commit/e33223023c48451533cc0bd8dbe3dd2c62e12317">e3322302</a>)</li> <li><strong>polly-request-presigner:</strong> override middleware name to allow concurrent presigning (<a href="https://redirect.github.com/aws/aws-sdk-js-v3/pull/6335">#6335</a>) (<a href="https:/aws/aws-sdk-js-v3/commit/54990fa2f2500bd7c82814f65394f09622db49df">54990fa2</a>)</li> </ul> <hr /> <p>For list of updated packages, view <strong>updated-packages.md</strong> in <strong>assets-3.621.0.zip</strong></p> <h2>v3.620.1</h2> <h4>3.620.1(2024-07-29)</h4> <h5>Chores</h5> <ul> <li>release accountId-endpoints config and codegen changes (<a href="https://redirect.github.com/aws/aws-sdk-js-v3/pull/6313">#6313</a>) (<a href="https:/aws/aws-sdk-js-v3/commit/de8d4a6bcffdb94f0d3b23f65fdb203136498a31">de8d4a6b</a>)</li> <li>release accountId-endpoints credential-provider changes (<a href="https:/aws/aws-sdk-js-v3/commit/d5011a5f39ef27e9f2b83f855a68f719c6c16591">d5011a5f</a>)</li> </ul> <h5>Documentation Changes</h5> <ul> <li><strong>client-memorydb:</strong> Renaming full service name as it appears in developer documentation. (<a href="https:/aws/aws-sdk-js-v3/commit/c94ecdde18c2f9a6cccadd0de27e13196de2b594">c94ecdde</a>)</li> <li><strong>client-elasticache:</strong> Renaming full service name as it appears in developer documentation. (<a href="https:/aws/aws-sdk-js-v3/commit/b5146baaf78a62face6db4ff140dfc3a302753b7">b5146baa</a>)</li> </ul> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https:/aws/aws-sdk-js-v3/blob/main/clients/client-s3/CHANGELOG.md"><code>@aws-sdk/client-s3</code>'s changelog</a>.</em></p> <blockquote> <h1><a href="https:/aws/aws-sdk-js-v3/compare/v3.620.1...v3.621.0">3.621.0</a> (2024-07-30)</h1> <p><strong>Note:</strong> Version bump only for package <code>@aws-sdk/client-s3</code></p> <h2><a href="https:/aws/aws-sdk-js-v3/compare/v3.620.0...v3.620.1">3.620.1</a> (2024-07-29)</h2> <p><strong>Note:</strong> Version bump only for package <code>@aws-sdk/client-s3</code></p> <h1><a href="https:/aws/aws-sdk-js-v3/compare/v3.619.0...v3.620.0">3.620.0</a> (2024-07-25)</h1> <p><strong>Note:</strong> Version bump only for package <code>@aws-sdk/client-s3</code></p> <h1><a href="https:/aws/aws-sdk-js-v3/compare/v3.616.0...v3.617.0">3.617.0</a> (2024-07-22)</h1> <p><strong>Note:</strong> Version bump only for package <code>@aws-sdk/client-s3</code></p> <h1><a href="https:/aws/aws-sdk-js-v3/compare/v3.615.0...v3.616.0">3.616.0</a> (2024-07-18)</h1> <p><strong>Note:</strong> Version bump only for package <code>@aws-sdk/client-s3</code></p> <h1><a href="https:/aws/aws-sdk-js-v3/compare/v3.613.0...v3.614.0">3.614.0</a> (2024-07-10)</h1> <p><strong>Note:</strong> Version bump only for package <code>@aws-sdk/client-s3</code></p> <h1><a href="https:/aws/aws-sdk-js-v3/compare/v3.612.0...v3.613.0">3.613.0</a> (2024-07-09)</h1> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https:/aws/aws-sdk-js-v3/commit/d8f767af7d8f634f80c98ed1a7e91deb160adc10"><code>d8f767a</code></a> Publish v3.621.0</li> <li><a href="https:/aws/aws-sdk-js-v3/commit/8dd7fb633c5333712bd18eb626fe1eb90939b0a7"><code>8dd7fb6</code></a> chore(codegen): bump smithy package versions (<a href="https:/aws/aws-sdk-js-v3/tree/HEAD/clients/client-s3/issues/6329">#6329</a>)</li> <li><a href="https:/aws/aws-sdk-js-v3/commit/c3dd5111b9d749f1fc92c7d3215646fd3ad844cb"><code>c3dd511</code></a> Publish v3.620.1</li> <li><a href="https:/aws/aws-sdk-js-v3/commit/0220bd055cbe0c8671d6e3afad31f2c22121b8df"><code>0220bd0</code></a> Publish v3.620.0</li> <li><a href="https:/aws/aws-sdk-js-v3/commit/ff30a3e8e4cb165ea8e79203b4228b7d5ce6547b"><code>ff30a3e</code></a> chore(clients): codegen sync for eventstream header fix (<a href="https:/aws/aws-sdk-js-v3/tree/HEAD/clients/client-s3/issues/6310">#6310</a>)</li> <li><a href="https:/aws/aws-sdk-js-v3/commit/ac98acca73a3caf30ab802be9594bcc5ad0a0a8e"><code>ac98acc</code></a> Publish v3.617.0</li> <li><a href="https:/aws/aws-sdk-js-v3/commit/fef3c3394d36614698d46f5a26a5679624e50181"><code>fef3c33</code></a> Publish v3.616.0</li> <li><a href="https:/aws/aws-sdk-js-v3/commit/9119ae6c46a3eece9c25e27142193f03229519f6"><code>9119ae6</code></a> chore(middleware-sdk-s3): update s3 status 200 error handling (<a href="https:/aws/aws-sdk-js-v3/tree/HEAD/clients/client-s3/issues/6232">#6232</a>)</li> <li><a href="https:/aws/aws-sdk-js-v3/commit/2687058e929ed9da4b40d7ef6d85963444f365a6"><code>2687058</code></a> chore(codegen): codegen sync for stream utils (<a href="https:/aws/aws-sdk-js-v3/tree/HEAD/clients/client-s3/issues/6279">#6279</a>)</li> <li><a href="https:/aws/aws-sdk-js-v3/commit/794a37e9795f390d15c9530209e465d099716c86"><code>794a37e</code></a> Publish v3.614.0</li> <li>Additional commits viewable in <a href="https:/aws/aws-sdk-js-v3/commits/v3.621.0/clients/client-s3">compare view</a></li> </ul> </details> <br /> Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https:/aws/aws-cdk/network/alerts). </details>
### Issue # (if applicable) The documentation for [Stack#exportValue](https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.Stack.html#exportwbrvalueexportedvalue-options) contains an “Example” section formatted as an H2 with two H3 sub-sections, whereas the method signature uses an H3. When generating documentation for CDK libraries inheriting from Stack, and jsii duplicates this “Example” section for each stack in the application in the API.md, this formatting issue causes a disruption in the heading hierarchy. This is particularly problematic on constructs.dev, where H3 headings are listed in the sidebar. Examples can be seen at: - https://constructs.dev/packages/@condensetech/cdk-constructs/v/0.1.2?lang=typescript - https://constructs.dev/packages/@cloudcomponents/cdk-temp-stack/v/2.4.0?lang=typescript - https://constructs.dev/packages/@gammarers/aws-lambda-function-invoke-error-notification-stack/v/1.0.49?lang=typescript ### Reason for this change By removing any heading from the method doc, there's no risk of altering the generated markdown hierarchy ### Description of changes I've removed the headings from the method documentation ### Description of how you validated changes N/A ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https:/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https:/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 #30146. ### Reason for this change Runtimes Python 3.11 and NodeJS 18 were missing. ### Description of changes Runtimes Python 3.11 and NodeJS 18 were added. ### Description of how you validated changes No tests were added, as it seems not required for this type of change. ### Checklist - [*] My code adheres to the [CONTRIBUTING GUIDE](https:/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https:/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*
### Reason for this change Amazon Kinesis Data Analytics now supports Apache Flink v1.18 ([LINK](https://aws.amazon.com/about-aws/whats-new/2024/06/amazon-managed-service-apache-flink-1-19/)) This is also supported in Cloudformation ([LINK](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-kinesisanalyticsv2-application.html#aws-resource-kinesisanalyticsv2-application-properties)) ### Description of changes - Added Flink 1.19 to `Runtime` type - Updated Readme to reference Flink 1.19 ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https:/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https:/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*
…x class (#30974) ### Issue # (if applicable) N/A ### Reason for this change Add validation for PlaceIndex description, similar to #30648, #30682, and #30711 . ### Description of changes Add validation and unit tests for description. ### Description of how you validated changes Add unit tests. ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https:/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https:/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 [#30796 .](#30796) ### Reason for this change ### Description of changes ### Description of how you validated changes ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https:/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https:/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*
…rovider (#28810) Export `NatGatewayProvider` for two reasons: to allow instantiation with `new`, and to make docs present it as an implementation of `NatProvider`. Also added a unit test for the same "functionality" for `NatInstanceProvider`, for symmetry with the added test for `NatGatewayProvider`. Unit test and integration test for new functionality added. Closes #28372. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
### Issue # (if applicable) N/A ### Reason for this change The change introduces the `description` property to the `EventBus` ### Description of changes - Add the `description` property for `EventBusProps`, which was missing in the L2 construct. - Add validation for character limit ### Description of how you validated changes I Added a unit test for eventBus and added the `description` property in the integration tests. ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https:/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https:/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*
…anary class (#30556) ### Issue # (if applicable) Closes #9300, #14086, #28152 ### Reason for this change In order to make the properties in the [runConfig](https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_synthetics.CfnCanary.RunConfigProperty.html) of the L1 Construct configurable in the L2 Construct. * [activeTracing](https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_synthetics.CfnCanary.RunConfigProperty.html#activetracing) * [memoryInMb](https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_synthetics.CfnCanary.RunConfigProperty.html#memoryinmb) * [timeoutInSeconds](https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_synthetics.CfnCanary.RunConfigProperty.html#timeoutinseconds) At the moment, the L2 [Canary](https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_synthetics.Canary.html) Class only supports [environmentVariables](https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_synthetics.CfnCanary.RunConfigProperty.html#environmentvariables) in the `runConfig`. ### Description of changes Add missing properties. * `activeTracing` * `memory` * `timeout` Note: The following is stated in #9300, but when tested, it was possible to set only `memoryInMb` (`memory`). > The difficulty is that timeoutInSeconds is required if runConfig is set, so one cannot only specify memoryInMb. Test code is here. ```ts class TestStack extends Stack { constructor(scope: Construct, id: string, props?: StackProps) { super(scope, id, props); new synthetics.Canary(this, 'Canary', { canaryName: 'next', runtime: synthetics.Runtime.SYNTHETICS_NODEJS_PUPPETEER_7_0, test: synthetics.Test.custom({ handler: 'index.handler', code: synthetics.Code.fromInline(` exports.handler = async () => { console.log(\'hello world\'); };`), }), cleanup: synthetics.Cleanup.LAMBDA, memory: Size.mebibytes(2048), }); } } ``` ### Description of how you validated changes Add unit tests and integ tests. ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https:/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https:/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*
aws-cdk-automation
added
auto-approve
pr/no-squash
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
aws-cdk-automation
had a problem deploying
to
test-pipeline
GitHub Actions
Failure
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
|
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). |
|
Comments on closed issues and PRs are hard for our team to see. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See CHANGELOG