…into otaviomhuijbers/ref-interfaces-l2s

…s/ref-interfaces-usage

…s/ref-interfaces-usage

…ws-cdk into otaviomhuijbers/ref-interfaces-l2s

…s/ref-interfaces-usage

### Issue # (if applicable)

None

### Reason for this change

AWS RDS now supports for retaining automated backups when cluster is deleted.
https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.Managing.Backups.Retaining.html

### Description of changes

- Add `deleteAutomatedBackups` prop  to `ClusterBaseProps`.

### Describe any new or updated permissions being added

None

### Description of how you validated changes

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*

### Issue # (if applicable)

Closes #35093.

### Reason for this change

Improve doc string to clarity what inputs are accepted for `contentType`.

### Description of changes

Simple documentation additions.

### Describe any new or updated permissions being added

None


### Description of how you validated changes

None, only documentation changes.

### 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*

It is mysteriously broken on PR builds, but not on my own machine.

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*

…licy (#35308)

### Issue # (if applicable)

None

### Reason for this change

When creating a `ResponseHeadersPolicy`, if we set `accessControlAllowCredentials` to true in the CORS configuration and include a string containing `*` in `accessControlAllowHeaders`, it causes a deployment error. I added validation to prevent this in advance.

```console
10:57:02 PM | CREATE_FAILED        | AWS::CloudFront::ResponseHeadersPolicy      | Dev-PriCo
ach/MainS...ponseHeadersPolicy
Resource handler returned message: "Invalid request provided: AWS::CloudFront::ResponseHeade
rsPolicy: The parameter Access-Control-Allow-Headers cannot contain * when allowCredentials
is true. (Service: CloudFront, Status Code: 400, Request ID: 9298af67-dfb6-4ddc-9cd6-b301e8f
eed3e) (SDK Attempt Count: 1)" (RequestToken: 2cbce7b6-8501-7bf8-aeb8-6781277473a0, HandlerE
rrorCode: InvalidRequest)
```

### Description of changes

Add validation for `ResponseHeadersPolicy`.

### Describe any new or updated permissions being added

None

### Description of how you validated changes

Add unit test

### 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*

…5309)

### Issue # (if applicable)

None

### Reason for this change

The `targets.AwsApi()` method enables us to call AWS API from EventBridge directly but there is no documentation about this feature.

### Description of changes

Update README.md

### Describe any new or updated permissions being added

None

### Description of how you validated changes

None

### 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*

…on (#35370)

### Issue # (if applicable)

Closes #35353.

### Reason for this change

Currently you are unable to specify the NodeJS 22 Runtime directly in the EvaluateExpression construct. When users try to use `Runtime.NODEJS_22_X`, they receive an error that this runtime is not supported. 

### Description of changes

- Added Node.js 22 runtime mapping to the `nodeJsGuids` object in `evaluate-expression.ts` with UUID `'b64e1fb8-9c89-4f7d-8a34-2e2a1c5f6d7e'`
- Added unit test coverage for Node.js 22 runtime in `evaluate-expression.test.ts`

The changes follow the exact same pattern as existing Node.js runtime support (Node.js 20, 18, etc.). No alternatives were considered as this is a straightforward addition to the existing runtime mapping system. The UUID was generated to ensure uniqueness for the singleton Lambda function pattern used by EvaluateExpression.

### Describe any new or updated permissions being added

No new or updated IAM permissions are required. This change only adds support for an additional Lambda runtime version.

### Description of how you validated changes

- Added unit test that verifies EvaluateExpression creates a Lambda function with `nodejs22.x` runtime
- All existing tests continue to pass (5/5 tests passing)
- Manually tested by creating a CDK app, synthesizing CloudFormation template, and deploying to AWS
- Verified the deployed Lambda function uses Node.js 22 runtime and executes successfully and returns 

### 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)
None

### Reason for this change
https://aws.amazon.com/about-aws/whats-new/2025/08/amazon-ec2-m8i-and-m8i-flex-instances-generally-available/
https://aws.amazon.com/about-aws/whats-new/2025/08/memory-optimized-amazon-ec2-r8i-r8i-flex-instances/

### Description of changes
Add m8i, m8i-flex, r8i, r8i-flex instance class

### Description of how you validated changes
```console
$ aws ec2 describe-instance-types | grep -e m8i -e r8i
            "InstanceType": "r8i.48xlarge",
            "InstanceType": "r8i-flex.8xlarge",
            "InstanceType": "m8i.16xlarge",
            "InstanceType": "m8i-flex.2xlarge",
```

### 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)

None

### Reason for this change

Neptune had released engine version 1.4.5.1.

- Docs
  - https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases-1.4.5.1.html
- Version confirmed via CLI
  - `aws neptune describe-db-engine-versions --engine neptune --engine-version 1.4.5.1 --region us-east-1
{
    "DBEngineVersions": [
        {
            "Engine": "neptune",
            "EngineVersion": "1.4.5.1",
            "DBParameterGroupFamily": "neptune1.4",
            "DBEngineDescription": "neptune",
            "DBEngineVersionDescription": "Neptune 1.4.5.1.R1",
            "ValidUpgradeTarget": [],
            "ExportableLogTypes": [
                "audit",
                "slowquery"
            ],
            "SupportsLogExportsToCloudwatchLogs": true,
            "SupportsReadReplica": false,
            "SupportsGlobalDatabases": true
        }
    ]
}`

### Description of changes

Added `V1_4_5_1` to EngineVersion class


### Description of how you validated changes

None

### 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*

In this test, the platform specified to bundle the asset is `linux/amd64`. But the image used doesn't specify any platform. This is causing the `integ.assets.bundling.docker-opts.ts` to fail with the message:

>Unable to find image 'cdk-66687611b68d3de0f92ed971e4c457e4828f2e0c877c8b1f5fab42ac3d2772ec:latest' locally
>docker: Error response from daemon: pull access denied for cdk-66687611b68d3de0f92ed971e4c457e4828f2e0c877c8b1f5fab42ac3d2772ec, repository does not exist or may require 'docker login'
>
>Run 'docker run --help' for more information

Add the platform to the build parameters of the Docker image.

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*

…nterfaces-usage