chore(release): 2.129.0 #29193

aws-cdk-automation · 2024-02-21T13:18:29Z

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

### Reason for this change Aurora PostgreSQL 16.1 is available as of January 31, 2024. See https://docs.aws.amazon.com/AmazonRDS/latest/AuroraPostgreSQLReleaseNotes/AuroraPostgreSQL.Updates.html#AuroraPostgreSQL.Updates.20180305.161 for more information. ### Description of changes Add constant for newly available Aurora Postgres cluster engine version 16.1 ### Description of how you validated changes No. Happy to add, if required. ### 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.128.0/CHANGELOG.md)

Closes #29103. I tested the example and it deploys. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*

@pahud

Closes #22645 Closes #27754 Spiritual successor of #27052 Somewhat related to #21181 but that might be another PR down the road. @pahud ✋ Please review. I'm not particularly fond of how `aws-autoscaling` module ([here](https://github.com/aws/aws-cdk/blob/256cca4017a80f8643c5f5a5999a2ce0383eebf0/packages/aws-cdk-lib/aws-autoscaling/lib/scheduled-action.ts#L21)) is not using `cdk.TimeZone` class, hence why used it in this PR instead. I think we should we change `aws-autoscaling` implementation to do the same? It would be a breaking change... and most likely a brand new PR. LMK what you think. ✌️ Also, I may be slightly OCD but I kinda like better `timezone` vs `timeZone`, but I went with latter one to follow what `aws-autoscaling` did. cc-ing @kaizencc for his input too 🙌 ... possibly related to #27105 ### Reason for this change Timezones have been supported in `AWS::ApplicationAutoScaling::ScalableTarget ScheduledAction` for a while now. https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-applicationautoscaling-scalabletarget-scheduledaction.html#cfn-applicationautoscaling-scalabletarget-scheduledaction-timezone ### Description of changes Just added the support for `timezones` in `scalableTarget.scaleOnSchedule` ### Description of how you validated changes Added unit tests for this feature. ### 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 #28990. ### Reason for this change There are cases where a task definition is created to be compatible with both EC2 and Fargate, and then we want to run the task in Fargate. ### Description of changes I created the `launchType` property. The `launchType` is overridden if the property is specified. ### Description of how you validated changes 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*

Closes #29135 ### Reason for this change Surface latest runtime versions in CDK. Older runtimes are being deprecated March 19, 2024 > To ensure uninterrupted canary runs and continued monitoring, AWS recommends customers to update their canaries to the latest Synthetics Runtimes versions: syn-nodejs-puppeteer-6.2 or higher for NodeJS-18, syn-nodejs-puppeteer-5.2 or higher for NodeJS-16, and syn-python-selenium-2.1 or higher for Python [2]. Canaries updated with latest Synthetics runtimes will continue running without interruption and receive future Lambda security updates. ### Description of changes - feat(synthetics): add 5.2, 6.1, 6.2 nodejs runtimes, deprecate 3.x runtimes - feat(synthetics): add syn-python-selenium-2.1 runtime - test(synthetics): update integration tests to cover latest runtimes ### Description of how you validated changes Attempted to run integration tests, but I don't have appropriate account setup ### 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*

### Reason for this change `origins.httpOrigin` requires a trick to specify the Lambda Functions URL. ### Description of changes This eases that pain and simplifies integration. ### Description of how you validated 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*

### Issue # (if applicable) Closes #N/A ### Reason for this change v2.127.0 updated the L1 construct for AWS::ECS::TaskDefinition, adding support for the property ContainerDefinitions.CredentialSpecs, [see](#29053). This PR adds support for CredentialSpecs property in the L2 construct used by `Ec2TaskDefinition.addContainer` method. ### Description of changes Added property in L2 construct, updated unit test and added integration test. ### Description of how you validated changes - [x] Unit test updated and validated - [x] Integration test added and validated ### 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*

remove madeline-k and MrArnoldPalmer from mergify.yml ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*

### Issue # (if applicable) part of #29041, #29039 Closes #<issue number here>. ### Reason for this change The testing hierarchy was disorganized. ### Description of changes Organized test as below. No logical change. ```ts describe('Application Load Balancer', () => { describe('ApplicationLoadBalancedFargateService', () => { ... }) describe('ApplicationMultipleTargetGroupsFargateService', () => { ... }) }) describe('Network Load Balancer', () => { describe('NetworkLoadBalancedFargateService', () => { ... }) describe('NetworkMultipleTargetGroupsFargateService', () => { ... }) }) ``` ### Description of how you validated changes pass unit 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*

…to 2.5.0 (#29159) Bumps [thollander/actions-comment-pull-request](https://github.com/thollander/actions-comment-pull-request) from 2.4.3 to 2.5.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/thollander/actions-comment-pull-request/releases">thollander/actions-comment-pull-request's releases</a>.</em></p> <blockquote> <h2>v2.4.3 : Node 20 version support</h2> <h2>What's Changed</h2> <ul> <li>chore(deps-dev): bump <code>@vercel/ncc</code> from 0.38.0 to 0.38.1 by <a href="https://github.com/dependabot"><code>@dependabot</code></a> in <a href="https://redirect.github.com/thollander/actions-comment-pull-request/pull/304">thollander/actions-comment-pull-request#304</a></li> <li>feat: node 20 version support by <a href="https://github.com/thollander"><code>@thollander</code></a> in <a href="https://redirect.github.com/thollander/actions-comment-pull-request/pull/307">thollander/actions-comment-pull-request#307</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/thollander/actions-comment-pull-request/compare/v2.4.3...v2.5.0">https://github.com/thollander/actions-comment-pull-request/compare/v2.4.3...v2.5.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/thollander/actions-comment-pull-request/commit/fabd468d3a1a0b97feee5f6b9e499eab0dd903f6"><code>fabd468</code></a> Merge pull request <a href="https://redirect.github.com/thollander/actions-comment-pull-request/issues/307">#307</a> from thollander/feat/node-20</li> <li><a href="https://github.com/thollander/actions-comment-pull-request/commit/cb9f4be78695d9811c6ad130dbfc0578ba444415"><code>cb9f4be</code></a> chore: bump to v2.5.0</li> <li><a href="https://github.com/thollander/actions-comment-pull-request/commit/2f6921097b4dc86a5b9fca468fabe581271e7a06"><code>2f69210</code></a> feat: node 20 version support</li> <li><a href="https://github.com/thollander/actions-comment-pull-request/commit/9d67388b9a94966eb262e68d9a3b368497990b77"><code>9d67388</code></a> chore(deps-dev): bump <code>@vercel/ncc</code> from 0.38.0 to 0.38.1 (<a href="https://redirect.github.com/thollander/actions-comment-pull-request/issues/304">#304</a>)</li> <li><a href="https://github.com/thollander/actions-comment-pull-request/commit/88b3c3f072e8cc7eae4b09d1cc62d308a51ca923"><code>88b3c3f</code></a> docs: fix wrong indent</li> <li>See full diff in <a href="https://github.com/thollander/actions-comment-pull-request/compare/1d3973dc4b8e1399c0620d3f2b1aa5e795465308...fabd468d3a1a0b97feee5f6b9e499eab0dd903f6">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=thollander/actions-comment-pull-request&package-manager=github_actions&previous-version=2.4.3&new-version=2.5.0)](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) </details>

This PR adds support for Aurora MySQL 3.05.2. https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.Updates.3052.html ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*

### Issue # (if applicable) part of #29041, #29039 continuation of #29153 Closes #<issue number here>. ### Reason for this change tests in `packages/aws-cdk-lib/aws-ecs-patterns/test/ec2/l3s.test.ts` was disorganized. ### Description of changes - No logical change. - Organized tests in `packages/aws-cdk-lib/aws-ecs-patterns/test/ec2/l3s.test.ts` as below. ```ts describe('ApplicationLoadBalancedEc2Service', () => { ... }) describe('NetworkLoadBalancedEc2Service', () => { ... }) ``` - move tests of `ApplicationLoadBalancedFargateService`, `NetworkLoadBalancedFargateService` in `packages/aws-cdk-lib/aws-ecs-patterns/test/ec2/l3s.test.ts` to `packages/aws-cdk-lib/aws-ecs-patterns/test/fargate/load-balanced-fargate-service.test.ts`. ### Description of how you validated changes Pass unit 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*

Adds a statement to match the document in the [docs](https://docs.aws.amazon.com/sns/latest/dg/sns-security-best-practices.html#enforce-encryption-data-in-transit): ``` { "Id": "ExamplePolicy", "Version": "2012-10-17", "Statement": [ { "Sid": "AllowPublishThroughSSLOnly", "Action": "SNS:Publish", "Effect": "Deny", "Resource": [ "arn:aws:sns:us-east-1:1234567890:test-topic" ], "Condition": { "Bool": { "aws:SecureTransport": "false" } }, "Principal": "*" } ] } ``` Closes #29142. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*

@Beau-Gosse-dev

*Co-authored by*: @Beau-Gosse-dev ### Issue # (if applicable) ### Reason for this change Lambda is launching dotnet8 ### Description of changes new runtime added ### Description of how you validated changes integ tested ### 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*

…e alarm support (#29171) ### Reason for this change Customers could create an alarm of type `IAlarm` where the alarm would be a composite alarm (for ex, when importing composite alarms, they return a type `IAlarm` instead of `CompositeAlarm`. This caused the logic that differentiates a composite alarm to mistakenly categorize the alarm incorrectly. ### Description of changes Add one policy scoped to `*` for any alarm passed to an environment. ### Description of how you validated changes Unit and integration 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*

…on (#28928) This PR adds support to configure IPv6 connectivity for lambda function by adding a single field to the VPC configuration in CDK’s Lambda Console to enable IPv6 dual stack support. The `Ipv6AllowedForDualStack` field is a new property that allows Lambda functions to specify whether the IPv6 traffic should be allowed when using dual-stack VPCs. - Support IPv6 connectivity for Lambda function by setting "ipv6AllowedForDualStack : true". This value will be converted to VpcConfig: {Ipv6AllowedForDualStack: true,} in template. *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-amazonmq │ └ resources │ └[~] resource AWS::AmazonMQ::Broker │ └ attributes │ ├ AmqpEndpoints: (documentation changed) │ ├ IpAddresses: (documentation changed) │ ├ MqttEndpoints: (documentation changed) │ ├ OpenWireEndpoints: (documentation changed) │ ├ StompEndpoints: (documentation changed) │ └ WssEndpoints: (documentation changed) ├[~] service aws-amplify │ └ resources │ └[~] resource AWS::Amplify::Domain │ └ attributes │ └ AutoSubDomainCreationPatterns: (documentation changed) ├[~] service aws-appconfig │ └ resources │ ├[~] resource AWS::AppConfig::Environment │ │ └ attributes │ │ └[-] Id: string │ └[~] resource AWS::AppConfig::HostedConfigurationVersion │ └ attributes │ └[-] Id: string ├[~] service aws-appstream │ └ resources │ ├[~] resource AWS::AppStream::Fleet │ │ ├ properties │ │ │ ├ IdleDisconnectTimeoutInSeconds: (documentation changed) │ │ │ └ MaxSessionsPerInstance: (documentation changed) │ │ └ types │ │ └[~] type ComputeCapacity │ │ └ properties │ │ └ DesiredSessions: (documentation changed) │ └[~] resource AWS::AppStream::Stack │ └ types │ └[~] type UserSetting │ └ properties │ └ MaximumLength: (documentation changed) ├[~] service aws-appsync │ └ resources │ ├[~] resource AWS::AppSync::ApiCache │ │ └ properties │ │ └[+] HealthMetricsConfig: string │ ├[~] resource AWS::AppSync::DataSource │ │ └ properties │ │ └[+] MetricsConfig: string │ ├[~] resource AWS::AppSync::GraphQLApi │ │ ├ properties │ │ │ ├[+] EnhancedMetricsConfig: EnhancedMetricsConfig │ │ │ └ EnvironmentVariables: (documentation changed) │ │ └ types │ │ └[+] type EnhancedMetricsConfig │ │ ├ documentation: Describes an enhanced metrics configuration. │ │ │ name: EnhancedMetricsConfig │ │ └ properties │ │ ├OperationLevelMetricsConfig: string (required) │ │ ├ResolverLevelMetricsBehavior: string (required) │ │ └DataSourceLevelMetricsBehavior: string (required) │ └[~] resource AWS::AppSync::Resolver │ └ properties │ └[+] MetricsConfig: string ├[~] service aws-autoscaling │ └ resources │ ├[~] resource AWS::AutoScaling::AutoScalingGroup │ │ ├ - documentation: The `AWS::AutoScaling::AutoScalingGroup` resource defines an Amazon EC2 Auto Scaling group, which is a collection of Amazon EC2 instances that are treated as a logical grouping for the purposes of automatic scaling and management. │ │ │ For more information about Amazon EC2 Auto Scaling, see the [Amazon EC2 Auto Scaling User Guide](https://docs.aws.amazon.com/autoscaling/ec2/userguide/what-is-amazon-ec2-auto-scaling.html) . │ │ │ > Amazon EC2 Auto Scaling configures instances launched as part of an Auto Scaling group using either a [launch template](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ec2-launchtemplate.html) or a launch configuration. We strongly recommend that you do not use launch configurations. They do not provide full functionality for Amazon EC2 Auto Scaling or Amazon EC2. For more information, see [Launch configurations](https://docs.aws.amazon.com/autoscaling/ec2/userguide/launch-configurations.html) and [Migrate AWS CloudFormation stacks from launch configurations to launch templates](https://docs.aws.amazon.com/autoscaling/ec2/userguide/migrate-launch-configurations-with-cloudformation.html) in the *Amazon EC2 Auto Scaling User Guide* . │ │ │ + documentation: The `AWS::AutoScaling::AutoScalingGroup` resource defines an Amazon EC2 Auto Scaling group, which is a collection of Amazon EC2 instances that are treated as a logical grouping for the purposes of automatic scaling and management. │ │ │ For more information about Amazon EC2 Auto Scaling, see the [Amazon EC2 Auto Scaling User Guide](https://docs.aws.amazon.com/autoscaling/ec2/userguide/what-is-amazon-ec2-auto-scaling.html) . │ │ │ > Amazon EC2 Auto Scaling configures instances launched as part of an Auto Scaling group using either a [launch template](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ec2-launchtemplate.html) or a launch configuration. We strongly recommend that you do not use launch configurations. For more information, see [Launch configurations](https://docs.aws.amazon.com/autoscaling/ec2/userguide/launch-configurations.html) in the *Amazon EC2 Auto Scaling User Guide* . │ │ │ > │ │ │ > For help migrating from launch configurations to launch templates, see [Migrate AWS CloudFormation stacks from launch configurations to launch templates](https://docs.aws.amazon.com/autoscaling/ec2/userguide/migrate-launch-configurations-with-cloudformation.html) in the *Amazon EC2 Auto Scaling User Guide* . │ │ └ types │ │ ├[~] type InstanceRequirements │ │ │ └ - documentation: The attributes for the instance types for a mixed instances policy. Amazon EC2 Auto Scaling uses your specified requirements to identify instance types. Then, it uses your On-Demand and Spot allocation strategies to launch instances from these instance types. │ │ │ When you specify multiple attributes, you get instance types that satisfy all of the specified attributes. If you specify multiple values for an attribute, you get instance types that satisfy any of the specified values. │ │ │ To limit the list of instance types from which Amazon EC2 Auto Scaling can identify matching instance types, you can use one of the following parameters, but not both in the same request: │ │ │ - `AllowedInstanceTypes` - The instance types to include in the list. All other instance types are ignored, even if they match your specified attributes. │ │ │ - `ExcludedInstanceTypes` - The instance types to exclude from the list, even if they match your specified attributes. │ │ │ > You must specify `VCpuCount` and `MemoryMiB` . All other attributes are optional. Any unspecified optional attribute is set to its default. │ │ │ For an example template, see [Auto scaling template snippets](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/quickref-autoscaling.html) . │ │ │ For more information, see [Creating an Auto Scaling group using attribute-based instance type selection](https://docs.aws.amazon.com/autoscaling/ec2/userguide/create-asg-instance-type-requirements.html) in the *Amazon EC2 Auto Scaling User Guide* . For help determining which instance types match your attributes before you apply them to your Auto Scaling group, see [Preview instance types with specified attributes](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-fleet-attribute-based-instance-type-selection.html#ec2fleet-get-instance-types-from-instance-requirements) in the *Amazon EC2 User Guide for Linux Instances* . │ │ │ `InstanceRequirements` is a property of the `LaunchTemplateOverrides` property of the [AWS::AutoScaling::AutoScalingGroup LaunchTemplate](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-autoscaling-autoscalinggroup-launchtemplate.html) property type. │ │ │ + documentation: The attributes for the instance types for a mixed instances policy. Amazon EC2 Auto Scaling uses your specified requirements to identify instance types. Then, it uses your On-Demand and Spot allocation strategies to launch instances from these instance types. │ │ │ When you specify multiple attributes, you get instance types that satisfy all of the specified attributes. If you specify multiple values for an attribute, you get instance types that satisfy any of the specified values. │ │ │ To limit the list of instance types from which Amazon EC2 Auto Scaling can identify matching instance types, you can use one of the following parameters, but not both in the same request: │ │ │ - `AllowedInstanceTypes` - The instance types to include in the list. All other instance types are ignored, even if they match your specified attributes. │ │ │ - `ExcludedInstanceTypes` - The instance types to exclude from the list, even if they match your specified attributes. │ │ │ > You must specify `VCpuCount` and `MemoryMiB` . All other attributes are optional. Any unspecified optional attribute is set to its default. │ │ │ For an example template, see [Configure Amazon EC2 Auto Scaling resources](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/quickref-ec2-auto-scaling.html) . │ │ │ For more information, see [Creating an Auto Scaling group using attribute-based instance type selection](https://docs.aws.amazon.com/autoscaling/ec2/userguide/create-asg-instance-type-requirements.html) in the *Amazon EC2 Auto Scaling User Guide* . For help determining which instance types match your attributes before you apply them to your Auto Scaling group, see [Preview instance types with specified attributes](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-fleet-attribute-based-instance-type-selection.html#ec2fleet-get-instance-types-from-instance-requirements) in the *Amazon EC2 User Guide for Linux Instances* . │ │ │ `InstanceRequirements` is a property of the `LaunchTemplateOverrides` property of the [AWS::AutoScaling::AutoScalingGroup LaunchTemplate](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-autoscaling-autoscalinggroup-launchtemplate.html) property type. │ │ ├[~] type LaunchTemplateSpecification │ │ │ └ - documentation: Specifies a launch template to use when provisioning EC2 instances for an Auto Scaling group. │ │ │ You must specify the following: │ │ │ - The ID or the name of the launch template, but not both. │ │ │ - The version of the launch template. │ │ │ `LaunchTemplateSpecification` is property of the [AWS::AutoScaling::AutoScalingGroup](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-autoscaling-autoscalinggroup.html) resource. It is also a property of the [AWS::AutoScaling::AutoScalingGroup LaunchTemplate](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-autoscaling-autoscalinggroup-launchtemplate.html) and [AWS::AutoScaling::AutoScalingGroup LaunchTemplateOverrides](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-autoscaling-autoscalinggroup-launchtemplateoverrides.html) property types. │ │ │ For information about creating a launch template, see [AWS::EC2::LaunchTemplate](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ec2-launchtemplate.html) and [Create a launch template for an Auto Scaling group](https://docs.aws.amazon.com/autoscaling/ec2/userguide/create-launch-template.html) in the *Amazon EC2 Auto Scaling User Guide* . │ │ │ For examples of launch templates, see [Auto scaling template snippets](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/quickref-autoscaling.html) and the [Examples](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ec2-launchtemplate.html#aws-resource-ec2-launchtemplate--examples) section in the `AWS::EC2::LaunchTemplate` resource. │ │ │ + documentation: Specifies a launch template to use when provisioning EC2 instances for an Auto Scaling group. │ │ │ You must specify the following: │ │ │ - The ID or the name of the launch template, but not both. │ │ │ - The version of the launch template. │ │ │ `LaunchTemplateSpecification` is property of the [AWS::AutoScaling::AutoScalingGroup](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-autoscaling-autoscalinggroup.html) resource. It is also a property of the [AWS::AutoScaling::AutoScalingGroup LaunchTemplate](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-autoscaling-autoscalinggroup-launchtemplate.html) and [AWS::AutoScaling::AutoScalingGroup LaunchTemplateOverrides](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-autoscaling-autoscalinggroup-launchtemplateoverrides.html) property types. │ │ │ For information about creating a launch template, see [AWS::EC2::LaunchTemplate](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ec2-launchtemplate.html) and [Create a launch template for an Auto Scaling group](https://docs.aws.amazon.com/autoscaling/ec2/userguide/create-launch-template.html) in the *Amazon EC2 Auto Scaling User Guide* . │ │ │ For examples of launch templates, see [Create launch templates](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/quickref-ec2-launch-templates.html) . │ │ └[~] type NotificationConfiguration │ │ └ - documentation: A structure that specifies an Amazon SNS notification configuration for the `NotificationConfigurations` property of the [AWS::AutoScaling::AutoScalingGroup](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-autoscaling-autoscalinggroup.html) resource. │ │ For an example template snippet, see [Auto scaling template snippets](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/quickref-autoscaling.html) . │ │ For more information, see [Get Amazon SNS notifications when your Auto Scaling group scales](https://docs.aws.amazon.com/autoscaling/ec2/userguide/ASGettingNotifications.html) in the *Amazon EC2 Auto Scaling User Guide* . │ │ + documentation: A structure that specifies an Amazon SNS notification configuration for the `NotificationConfigurations` property of the [AWS::AutoScaling::AutoScalingGroup](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-autoscaling-autoscalinggroup.html) resource. │ │ For an example template snippet, see [Configure Amazon EC2 Auto Scaling resources](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/quickref-ec2-auto-scaling.html) . │ │ For more information, see [Get Amazon SNS notifications when your Auto Scaling group scales](https://docs.aws.amazon.com/autoscaling/ec2/userguide/ASGettingNotifications.html) in the *Amazon EC2 Auto Scaling User Guide* . │ ├[~] resource AWS::AutoScaling::LaunchConfiguration │ │ └ - documentation: The `AWS::AutoScaling::LaunchConfiguration` resource specifies the launch configuration that can be used by an Auto Scaling group to configure Amazon EC2 instances. │ │ When you update the launch configuration for an Auto Scaling group, CloudFormation deletes that resource and creates a new launch configuration with the updated properties and a new name. Existing instances are not affected. To update existing instances when you update the `AWS::AutoScaling::LaunchConfiguration` resource, you can specify an [UpdatePolicy attribute](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-attribute-updatepolicy.html) for the group. You can find sample update policies for rolling updates in [Auto scaling template snippets](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/quickref-autoscaling.html) . │ │ > Amazon EC2 Auto Scaling configures instances launched as part of an Auto Scaling group using either a [launch template](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ec2-launchtemplate.html) or a launch configuration. We strongly recommend that you do not use launch configurations. They do not provide full functionality for Amazon EC2 Auto Scaling or Amazon EC2. For more information, see [Launch configurations](https://docs.aws.amazon.com/autoscaling/ec2/userguide/launch-configurations.html) and [Migrate AWS CloudFormation stacks from launch configurations to launch templates](https://docs.aws.amazon.com/autoscaling/ec2/userguide/migrate-launch-configurations-with-cloudformation.html) in the *Amazon EC2 Auto Scaling User Guide* . │ │ + documentation: The `AWS::AutoScaling::LaunchConfiguration` resource specifies the launch configuration that can be used by an Auto Scaling group to configure Amazon EC2 instances. │ │ When you update the launch configuration for an Auto Scaling group, CloudFormation deletes that resource and creates a new launch configuration with the updated properties and a new name. Existing instances are not affected. To update existing instances when you update the `AWS::AutoScaling::LaunchConfiguration` resource, you can specify an [UpdatePolicy attribute](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-attribute-updatepolicy.html) for the group. You can find sample update policies for rolling updates in [Configure Amazon EC2 Auto Scaling resources](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/quickref-ec2-auto-scaling.html) . │ │ > Amazon EC2 Auto Scaling configures instances launched as part of an Auto Scaling group using either a [launch template](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ec2-launchtemplate.html) or a launch configuration. We strongly recommend that you do not use launch configurations. For more information, see [Launch configurations](https://docs.aws.amazon.com/autoscaling/ec2/userguide/launch-configurations.html) in the *Amazon EC2 Auto Scaling User Guide* . │ │ > │ │ > For help migrating from launch configurations to launch templates, see [Migrate AWS CloudFormation stacks from launch configurations to launch templates](https://docs.aws.amazon.com/autoscaling/ec2/userguide/migrate-launch-configurations-with-cloudformation.html) in the *Amazon EC2 Auto Scaling User Guide* . │ └[~] resource AWS::AutoScaling::ScheduledAction │ └ - documentation: The `AWS::AutoScaling::ScheduledAction` resource specifies an Amazon EC2 Auto Scaling scheduled action so that the Auto Scaling group can change the number of instances available for your application in response to predictable load changes. │ When you update a stack with an Auto Scaling group and scheduled action, CloudFormation always sets the min size, max size, and desired capacity properties of your group to the values that are defined in the `AWS::AutoScaling::AutoScalingGroup` section of your template. However, you might not want CloudFormation to do that when you have a scheduled action in effect. You can use an [UpdatePolicy attribute](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-attribute-updatepolicy.html) to prevent CloudFormation from changing the min size, max size, or desired capacity property values during a stack update unless you modified the individual values in your template. If you have rolling updates enabled, before you can update the Auto Scaling group, you must suspend scheduled actions by specifying an [UpdatePolicy attribute](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-attribute-updatepolicy.html) for the Auto Scaling group. You can find a sample update policy for rolling updates in [Auto scaling template snippets](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/quickref-autoscaling.html) . │ For more information, see [Scheduled scaling](https://docs.aws.amazon.com/autoscaling/ec2/userguide/schedule_time.html) and [Suspending and resuming scaling processes](https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-suspend-resume-processes.html) in the *Amazon EC2 Auto Scaling User Guide* . │ + documentation: The `AWS::AutoScaling::ScheduledAction` resource specifies an Amazon EC2 Auto Scaling scheduled action so that the Auto Scaling group can change the number of instances available for your application in response to predictable load changes. │ When you update a stack with an Auto Scaling group and scheduled action, CloudFormation always sets the min size, max size, and desired capacity properties of your group to the values that are defined in the `AWS::AutoScaling::AutoScalingGroup` section of your template. However, you might not want CloudFormation to do that when you have a scheduled action in effect. You can use an [UpdatePolicy attribute](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-attribute-updatepolicy.html) to prevent CloudFormation from changing the min size, max size, or desired capacity property values during a stack update unless you modified the individual values in your template. If you have rolling updates enabled, before you can update the Auto Scaling group, you must suspend scheduled actions by specifying an [UpdatePolicy attribute](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-attribute-updatepolicy.html) for the Auto Scaling group. You can find a sample update policy for rolling updates in [Configure Amazon EC2 Auto Scaling resources](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/quickref-ec2-auto-scaling.html) . │ For more information, see [Scheduled scaling](https://docs.aws.amazon.com/autoscaling/ec2/userguide/schedule_time.html) and [Suspending and resuming scaling processes](https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-suspend-resume-processes.html) in the *Amazon EC2 Auto Scaling User Guide* . ├[~] service aws-batch │ └ resources │ └[~] resource AWS::Batch::JobDefinition │ └ types │ ├[~] type ContainerProperties │ │ └ properties │ │ └[+] RepositoryCredentials: RepositoryCredentials │ ├[~] type Metadata │ │ ├ - documentation: undefined │ │ │ + documentation: Metadata about the Kubernetes pod. For more information, see [Understanding Kubernetes Objects](https://docs.aws.amazon.com/https://kubernetes.io/docs/concepts/overview/working-with-objects/kubernetes-objects/) in the *Kubernetes documentation* . │ │ └ properties │ │ └ Labels: (documentation changed) │ ├[~] type PodProperties │ │ ├ - documentation: undefined │ │ │ + documentation: The properties for the pod. │ │ └ properties │ │ ├ Containers: (documentation changed) │ │ ├ DnsPolicy: (documentation changed) │ │ ├ HostNetwork: (documentation changed) │ │ ├ Metadata: (documentation changed) │ │ ├ ServiceAccountName: (documentation changed) │ │ └ Volumes: (documentation changed) │ └[+] type RepositoryCredentials │ ├ documentation: The repository credentials for private registry authentication. │ │ name: RepositoryCredentials │ └ properties │ └CredentialsParameter: string (required) ├[~] service aws-cleanrooms │ └ resources │ └[~] resource AWS::CleanRooms::AnalysisTemplate │ └ attributes │ └ Schema: (documentation changed) ├[~] service aws-cloudformation │ └ resources │ ├[~] resource AWS::CloudFormation::Stack │ │ └ attributes │ │ └ Outputs: (documentation changed) │ └[~] resource AWS::CloudFormation::WaitCondition │ └ attributes │ └ Data: (documentation changed) ├[~] service aws-cloudfront │ └ resources │ ├[~] resource AWS::CloudFront::Distribution │ │ └ types │ │ ├[~] type DistributionConfig │ │ │ └ properties │ │ │ ├ CNAMEs: (documentation changed) │ │ │ ├ CustomOrigin: (documentation changed) │ │ │ ├ S3Origin: (documentation changed) │ │ │ └ WebACLId: (documentation changed) │ │ ├[~] type LegacyCustomOrigin │ │ │ └ properties │ │ │ ├ DNSName: (documentation changed) │ │ │ ├ HTTPPort: (documentation changed) │ │ │ ├ HTTPSPort: (documentation changed) │ │ │ ├ OriginProtocolPolicy: (documentation changed) │ │ │ └ OriginSSLProtocols: (documentation changed) │ │ ├[~] type LegacyS3Origin │ │ │ └ properties │ │ │ ├ DNSName: (documentation changed) │ │ │ └ OriginAccessIdentity: (documentation changed) │ │ └[~] type S3OriginConfig │ │ └ properties │ │ └ OriginAccessIdentity: (documentation changed) │ └[~] resource AWS::CloudFront::Function │ └ attributes │ └ FunctionMetadata.FunctionARN: (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-cloudwatch │ └ resources │ └[~] resource AWS::CloudWatch::AnomalyDetector │ ├ - documentation: The `AWS::CloudWatch::AnomalyDetector` type specifies an anomaly detection band for a certain metric and statistic. The band represents the expected "normal" range for the metric values. Anomaly detection bands can be used for visualization of a metric's expected values, and for alarms. │ │ + documentation: The `AWS::CloudWatch::AnomalyDetector` type specifies an anomaly detection band for a certain metric and statistic. The band represents the expected "normal" range for the metric values. Anomaly detection bands can be used for visualization of a metric's expected values, and for alarms. │ │ For more information see [Using CloudWatch anomaly detection.](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch_Anomaly_Detection.html) . │ └ types │ └[~] type SingleMetricAnomalyDetector │ └ - documentation: Designates the CloudWatch metric and statistic that provides the time series the anomaly detector uses as input. │ + documentation: Designates the CloudWatch metric and statistic that provides the time series the anomaly detector uses as input. If you have enabled unified cross-account observability, and this account is a monitoring account, the metric can be in the same account or a source account. ├[~] service aws-codepipeline │ └ resources │ └[~] resource AWS::CodePipeline::Pipeline │ ├ - documentation: The `AWS::CodePipeline::Pipeline` resource creates a CodePipeline pipeline that describes how software changes go through a release process. For more information, see [What Is CodePipeline?](https://docs.aws.amazon.com/codepipeline/latest/userguide/welcome.html) in the *AWS CodePipeline User Guide* . │ │ + documentation: The `AWS::CodePipeline::Pipeline` resource creates a CodePipeline pipeline that describes how software changes go through a release process. For more information, see [What Is CodePipeline?](https://docs.aws.amazon.com/codepipeline/latest/userguide/welcome.html) in the *CodePipeline User Guide* . │ │ For an example in YAML and JSON that contains the parameters in this reference, see [Examples](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-codepipeline-pipeline.html#aws-resource-codepipeline-pipeline--examples) . │ ├ properties │ │ ├[+] ExecutionMode: string │ │ └ PipelineType: (documentation changed) │ └ types │ ├[~] type ActionDeclaration │ │ └ - documentation: Represents information about an action declaration. │ │ + documentation: Represents information about an action declaration. │ │ > Documentation for the `timeoutInMinutes` parameter in the `ActionDeclaration` is not yet available for CloudFormation and CDK resources in CodePipeline. For more information about the configurable timeout for manual approval actions, see the [ActionDeclaration](https://docs.aws.amazon.com/codepipeline/latest/APIReference/API_ActionDeclaration.html) in the CodePipeline API Reference. │ ├[+] type GitBranchFilterCriteria │ │ ├ documentation: The Git repository branches specified as filter criteria to start the pipeline. │ │ │ name: GitBranchFilterCriteria │ │ └ properties │ │ ├Includes: Array<string> │ │ └Excludes: Array<string> │ ├[~] type GitConfiguration │ │ └ properties │ │ ├[+] PullRequest: Array<GitPullRequestFilter> │ │ └ Push: (documentation changed) │ ├[+] type GitFilePathFilterCriteria │ │ ├ documentation: The Git repository file paths specified as filter criteria to start the pipeline. │ │ │ name: GitFilePathFilterCriteria │ │ └ properties │ │ ├Includes: Array<string> │ │ └Excludes: Array<string> │ ├[+] type GitPullRequestFilter │ │ ├ documentation: The event criteria for the pull request trigger configuration, such as the lists of branches or file paths to include and exclude. │ │ │ name: GitPullRequestFilter │ │ └ properties │ │ ├FilePaths: GitFilePathFilterCriteria │ │ ├Events: Array<string> │ │ └Branches: GitBranchFilterCriteria │ └[~] type GitPushFilter │ └ properties │ ├[+] Branches: GitBranchFilterCriteria │ └[+] FilePaths: GitFilePathFilterCriteria ├[~] service aws-cognito │ └ resources │ └[~] resource AWS::Cognito::UserPoolRiskConfigurationAttachment │ └ attributes │ └[-] Id: string ├[~] service aws-config │ └ resources │ └[~] resource AWS::Config::ConformancePack │ └ types │ └[~] type TemplateSSMDocumentDetails │ └ properties │ └ DocumentName: (documentation changed) ├[~] service aws-connect │ └ resources │ └[~] resource AWS::Connect::User │ └ types │ ├[~] type UserIdentityInfo │ │ └ - documentation: Contains information about the identity of a user. │ │ + documentation: Contains information about the identity of a user. │ │ > For Amazon Connect instances that are created with the `EXISTING_DIRECTORY` identity management type, `FirstName` , `LastName` , and `Email` cannot be updated from within Amazon Connect because they are managed by the directory. │ └[~] type UserPhoneConfig │ └ properties │ └ AfterContactWorkTimeLimit: (documentation changed) ├[~] service aws-controltower │ └ resources │ ├[+] resource AWS::ControlTower::EnabledBaseline │ │ ├ name: EnabledBaseline │ │ │ cloudFormationType: AWS::ControlTower::EnabledBaseline │ │ │ documentation: This resource represents a `Baseline` that has been applied to a target. │ │ │ tagInformation: {"tagPropertyName":"Tags","variant":"standard"} │ │ ├ properties │ │ │ ├BaselineIdentifier: string (required, immutable) │ │ │ ├BaselineVersion: string (required) │ │ │ ├TargetIdentifier: string (required, immutable) │ │ │ ├Parameters: Array<Parameter> │ │ │ └Tags: Array<tag> │ │ ├ attributes │ │ │ └EnabledBaselineIdentifier: string │ │ └ types │ │ └type Parameter │ │ ├ documentation: A key-value parameter to an `EnabledBaseline` resource. │ │ │ name: Parameter │ │ └ properties │ │ ├Key: string │ │ └Value: string | json | number | Array<boolean | number | json | string> | boolean │ ├[~] resource AWS::ControlTower::EnabledControl │ │ ├ - tagInformation: undefined │ │ │ + tagInformation: {"tagPropertyName":"Tags","variant":"standard"} │ │ └ properties │ │ ├ ControlIdentifier: (documentation changed) │ │ └[+] Tags: Array<tag> │ └[~] resource AWS::ControlTower::LandingZone │ ├ properties │ │ └ Manifest: (documentation changed) │ └ attributes │ └ Status: (documentation changed) ├[~] service aws-datasync │ └ resources │ └[~] resource AWS::DataSync::Task │ └ attributes │ ├ DestinationNetworkInterfaceArns: (documentation changed) │ └ SourceNetworkInterfaceArns: (documentation changed) ├[~] service aws-directoryservice │ └ resources │ ├[~] resource AWS::DirectoryService::MicrosoftAD │ │ └ attributes │ │ └ DnsIpAddresses: (documentation changed) │ └[~] resource AWS::DirectoryService::SimpleAD │ └ attributes │ └ DnsIpAddresses: (documentation changed) ├[~] service aws-ec2 │ └ resources │ ├[~] resource AWS::EC2::ClientVpnEndpoint │ │ ├ properties │ │ │ └[-] ClientRouteMonitoringOptions: ClientRouteMonitoringOptions │ │ └ types │ │ └[-] type ClientRouteMonitoringOptions │ │ ├ name: ClientRouteMonitoringOptions │ │ └ properties │ │ └Enabled: boolean │ ├[~] resource AWS::EC2::EC2Fleet │ │ └ types │ │ └[~] type InstanceRequirementsRequest │ │ └ properties │ │ └[+] MaxSpotPriceAsPercentageOfOptimalOnDemandPrice: integer │ ├[~] resource AWS::EC2::LaunchTemplate │ │ └ types │ │ └[~] type MaintenanceOptions │ │ └ properties │ │ └ RebootMigration: (documentation changed) │ ├[~] resource AWS::EC2::NetworkInsightsAnalysis │ │ └ attributes │ │ ├ AlternatePathHints: (documentation changed) │ │ ├ Explanations: (documentation changed) │ │ ├ ForwardPathComponents: (documentation changed) │ │ ├ ReturnPathComponents: (documentation changed) │ │ └ SuggestedAccounts: (documentation changed) │ ├[~] resource AWS::EC2::NetworkInterface │ │ └ attributes │ │ └ SecondaryPrivateIpAddresses: (documentation changed) │ ├[~] resource AWS::EC2::PrefixList │ │ └ properties │ │ └ MaxEntries: - integer (required) │ │ + integer │ ├[~] resource AWS::EC2::SecurityGroupEgress │ │ └ attributes │ │ └ Id: (documentation changed) │ ├[~] resource AWS::EC2::SpotFleet │ │ └ types │ │ └[~] type InstanceRequirementsRequest │ │ └ properties │ │ └[+] MaxSpotPriceAsPercentageOfOptimalOnDemandPrice: integer │ ├[~] resource AWS::EC2::TransitGatewayPeeringAttachment │ │ └ attributes │ │ └ Status: (documentation changed) │ ├[~] resource AWS::EC2::VPC │ │ └ attributes │ │ ├ CidrBlockAssociations: (documentation changed) │ │ └ Ipv6CidrBlocks: (documentation changed) │ └[~] resource AWS::EC2::VPCEndpoint │ └ attributes │ ├ DnsEntries: (documentation changed) │ └ NetworkInterfaceIds: (documentation changed) ├[~] service aws-ecs │ └ resources │ └[~] resource AWS::ECS::TaskDefinition │ └ types │ └[~] type KernelCapabilities │ └ - documentation: The `KernelCapabilities` property specifies the Linux capabilities for the container that are added to or dropped from the default configuration that is provided by Docker. For more information on the default capabilities and the non-default available capabilities, see [Runtime privilege and Linux capabilities](https://docs.aws.amazon.com/https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities) in the *Docker run reference* . For more detailed information on these Linux capabilities, see the [capabilities(7)](https://docs.aws.amazon.com/http://man7.org/linux/man-pages/man7/capabilities.7.html) Linux manual page. │ + documentation: The Linux capabilities to add or remove from the default Docker configuration for a container defined in the task definition. For more information about the default capabilities and the non-default available capabilities, see [Runtime privilege and Linux capabilities](https://docs.aws.amazon.com/https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities) in the *Docker run reference* . For more detailed information about these Linux capabilities, see the [capabilities(7)](https://docs.aws.amazon.com/http://man7.org/linux/man-pages/man7/capabilities.7.html) Linux manual page. ├[~] service aws-eks │ └ resources │ └[~] resource AWS::EKS::Cluster │ └ attributes │ └ KubernetesNetworkConfig.ServiceIpv6Cidr: (documentation changed) ├[~] service aws-elasticache │ └ resources │ ├[~] resource AWS::ElastiCache::CacheCluster │ │ └ properties │ │ └ PreferredMaintenanceWindow: (documentation changed) │ ├[~] resource AWS::ElastiCache::ParameterGroup │ │ └ attributes │ │ └[+] CacheParameterGroupName: string │ ├[~] resource AWS::ElastiCache::ReplicationGroup │ │ └ attributes │ │ ├ ReadEndPoint.Addresses.List: (documentation changed) │ │ └ ReadEndPoint.Ports.List: (documentation changed) │ ├[~] resource AWS::ElastiCache::ServerlessCache │ │ ├ properties │ │ │ ├ Endpoint: (documentation changed) │ │ │ └ ReaderEndpoint: (documentation changed) │ │ └ types │ │ └[~] type Endpoint │ │ └ - documentation: Represents the information required for client programs to connect to a cache node. │ │ + documentation: Represents the information required for client programs to connect to a cache node. This value is read-only. │ └[~] resource AWS::ElastiCache::User │ └ properties │ └ AuthenticationMode: (documentation changed) ├[~] service aws-elasticloadbalancingv2 │ └ resources │ ├[~] resource AWS::ElasticLoadBalancingV2::LoadBalancer │ │ └ attributes │ │ └ SecurityGroups: (documentation changed) │ ├[~] resource AWS::ElasticLoadBalancingV2::TargetGroup │ │ └ attributes │ │ └ LoadBalancerArns: (documentation changed) │ └[~] resource AWS::ElasticLoadBalancingV2::TrustStoreRevocation │ └ attributes │ └ TrustStoreRevocations: (documentation changed) ├[~] service aws-emr │ └ resources │ └[~] resource AWS::EMR::Cluster │ └ types │ └[~] type JobFlowInstancesConfig │ └ properties │ └[+] UnhealthyNodeReplacement: boolean ├[~] service aws-fis │ └ resources │ └[~] resource AWS::FIS::ExperimentTemplate │ └ types │ └[~] type ExperimentTemplateAction │ └ properties │ ├ Parameters: (documentation changed) │ └ Targets: (documentation changed) ├[~] service aws-frauddetector │ └ resources │ └[~] resource AWS::FraudDetector::Detector │ └ attributes │ ├ EventType.Arn: (documentation changed) │ ├ EventType.CreatedTime: (documentation changed) │ └ EventType.LastUpdatedTime: (documentation changed) ├[~] service aws-globalaccelerator │ └ resources │ └[~] resource AWS::GlobalAccelerator::Accelerator │ └ attributes │ ├ Ipv4Addresses: (documentation changed) │ └ Ipv6Addresses: (documentation changed) ├[~] service aws-glue │ └ resources │ ├[~] resource AWS::Glue::Classifier │ │ └ types │ │ └[~] type CsvClassifier │ │ └ properties │ │ ├ ContainsCustomDatatype: (documentation changed) │ │ └ CustomDatatypeConfigured: (documentation changed) │ ├[~] resource AWS::Glue::Crawler │ │ └ types │ │ ├[~] type IcebergTarget │ │ │ ├ - documentation: Specifies an Apache Iceberg data source where Iceberg tables are stored in Amazon S3. │ │ │ │ + documentation: Specifies Apache Iceberg data store targets. │ │ │ └ properties │ │ │ ├ Exclusions: (documentation changed) │ │ │ └ Paths: (documentation changed) │ │ └[~] type Targets │ │ └ properties │ │ └ IcebergTargets: (documentation changed) │ ├[~] resource AWS::Glue::CustomEntityType │ │ └ properties │ │ └ Tags: (documentation changed) │ ├[~] resource AWS::Glue::Database │ │ └ types │ │ └[~] type DatabaseIdentifier │ │ └ properties │ │ └ Region: (documentation changed) │ ├[~] resource AWS::Glue::DataCatalogEncryptionSettings │ │ └ types │ │ └[~] type EncryptionAtRest │ │ └ properties │ │ └[+] CatalogEncryptionServiceRole: string │ ├[~] resource AWS::Glue::Table │ │ ├ properties │ │ │ └ OpenTableFormatInput: (documentation changed) │ │ └ types │ │ ├[~] type IcebergInput │ │ │ ├ - documentation: A structure that defines an Apache Iceberg metadata table to create in the catalog. │ │ │ │ + documentation: Specifies an input structure that defines an Apache Iceberg metadata table. │ │ │ └ properties │ │ │ └ MetadataOperation: (documentation changed) │ │ ├[~] type OpenTableFormatInput │ │ │ └ - documentation: A structure representing an open format table. │ │ │ + documentation: Specifies an `OpenTableFormatInput` structure when creating an open format table. │ │ └[~] type TableIdentifier │ │ └ properties │ │ └ Region: (documentation changed) │ └[~] resource AWS::Glue::TableOptimizer │ ├ - documentation: Resource Type definition for AWS::Glue::TableOptimizer │ │ + documentation: A resource that describes the AWS Glue resource for enabling compaction to improve read performance for open table formats. │ ├ properties │ │ ├ CatalogId: (documentation changed) │ │ └ Type: (documentation changed) │ └ types │ └[~] type TableOptimizerConfiguration │ ├ - documentation: undefined │ │ + documentation: Specifies configuration details of a table optimizer. │ └ properties │ ├ Enabled: - boolean │ │ + boolean (required) │ │ (documentation changed) │ └ RoleArn: - string │ + string (required) │ (documentation changed) ├[~] service aws-groundstation │ └ resources │ └[~] resource AWS::GroundStation::MissionProfile │ └ properties │ ├ ContactPostPassDurationSeconds: (documentation changed) │ └ ContactPrePassDurationSeconds: (documentation changed) ├[~] service aws-guardduty │ └ resources │ ├[~] resource AWS::GuardDuty::Master │ │ └ properties │ │ └ MasterId: (documentation changed) │ └[~] resource AWS::GuardDuty::Member │ └ properties │ ├ DetectorId: - string (required, immutable) │ │ + string (immutable) │ └ MemberId: - string (required, immutable) │ + string (immutable) │ (documentation changed) ├[~] service aws-imagebuilder │ └ resources │ ├[~] resource AWS::ImageBuilder::Image │ │ ├ - documentation: An image build version. An image is a customized, secure, and up-to-date “golden” server image that is pre-installed and pre-configured with software and settings to meet specific IT standards. │ │ │ + documentation: Creates a new image. This request will create a new image along with all of the configured output resources defined in the distribution configuration. You must specify exactly one recipe for your image, using either a ContainerRecipeArn or an ImageRecipeArn. │ │ ├ properties │ │ │ ├ ContainerRecipeArn: (documentation changed) │ │ │ ├ DistributionConfigurationArn: (documentation changed) │ │ │ ├ EnhancedImageMetadataEnabled: (documentation changed) │ │ │ ├ ImageRecipeArn: (documentation changed) │ │ │ ├ ImageTestsConfiguration: (documentation changed) │ │ │ ├ InfrastructureConfigurationArn: (documentation changed) │ │ │ └ Workflows: (documentation changed) │ │ └ attributes │ │ └ ImageUri: (documentation changed) │ ├[~] resource AWS::ImageBuilder::LifecyclePolicy │ │ ├ - documentation: The configuration details for a lifecycle policy resource. │ │ │ + documentation: Create a lifecycle policy resource. │ │ ├ properties │ │ │ ├ ExecutionRole: (documentation changed) │ │ │ ├ Name: (documentation changed) │ │ │ ├ PolicyDetails: (documentation changed) │ │ │ ├ ResourceSelection: (documentation changed) │ │ │ ├ ResourceType: (documentation changed) │ │ │ └ Tags: (documentation changed) │ │ └ types │ │ ├[~] type Action │ │ │ ├ - documentation: The action of the policy detail. │ │ │ │ + documentation: Contains selection criteria for the lifecycle policy. │ │ │ └ properties │ │ │ ├ IncludeResources: (documentation changed) │ │ │ └ Type: (documentation changed) │ │ ├[~] type AmiExclusionRules │ │ │ ├ - documentation: The AMI exclusion rules for the policy detail. │ │ │ │ + documentation: Defines criteria for AMIs that are excluded from lifecycle actions. │ │ │ └ properties │ │ │ ├ IsPublic: (documentation changed) │ │ │ ├ LastLaunched: (documentation changed) │ │ │ ├ Regions: (documentation changed) │ │ │ ├ SharedAccounts: (documentation changed) │ │ │ └ TagMap: (documentation changed) │ │ ├[~] type ExclusionRules │ │ │ ├ - documentation: The exclusion rules to apply of the policy detail. │ │ │ │ + documentation: Specifies resources that lifecycle policy actions should not apply to. │ │ │ └ properties │ │ │ ├ Amis: (documentation changed) │ │ │ └ TagMap: (documentation changed) │ │ ├[~] type Filter │ │ │ ├ - documentation: A filter name and value pair that is used to return a more specific list of results from a list operation. Filters can be used to match a set of resources by specific criteria, such as tags, attributes, or IDs. │ │ │ │ + documentation: Defines filters that the lifecycle policy uses to determine impacted resource. │ │ │ └ properties │ │ │ ├ RetainAtLeast: (documentation changed) │ │ │ ├ Type: (documentation changed) │ │ │ ├ Unit: (documentation changed) │ │ │ └ Value: (documentation changed) │ │ ├[~] type IncludeResources │ │ │ ├ - documentation: The included resources of the policy detail. │ │ │ │ + documentation: Specifies how the lifecycle policy should apply actions to selected resources. │ │ │ └ properties │ │ │ ├ Amis: (documentation changed) │ │ │ ├ Containers: (documentation changed) │ │ │ └ Snapshots: (documentation changed) │ │ ├[~] type LastLaunched │ │ │ ├ - documentation: The last launched time of a resource. │ │ │ │ + documentation: Defines criteria to exclude AMIs from lifecycle actions based on the last time they were used to launch an instance. │ │ │ └ properties │ │ │ ├ Unit: (documentation changed) │ │ │ └ Value: (documentation changed) │ │ ├[~] type PolicyDetail │ │ │ ├ - documentation: The policy detail of the lifecycle policy. │ │ │ │ + documentation: The configuration details for a lifecycle policy resource. │ │ │ └ properties │ │ │ ├ Action: (documentation changed) │ │ │ ├ ExclusionRules: (documentation changed) │ │ │ └ Filter: (documentation changed) │ │ ├[~] type RecipeSelection │ │ │ ├ - documentation: The recipe to apply the lifecycle policy for. │ │ │ │ + documentation: Specifies an Image Builder recipe that the lifecycle policy uses for resource selection. │ │ │ └ properties │ │ │ ├ Name: (documentation changed) │ │ │ └ SemanticVersion: (documentation changed) │ │ └[~] type ResourceSelection │ │ ├ - documentation: The resource selection for the lifecycle policy. │ │ │ + documentation: Resource selection criteria for the lifecycle policy. │ │ └ properties │ │ ├ Recipes: (documentation changed) │ │ └ TagMap: (documentation changed) │ └[~] resource AWS::ImageBuilder::Workflow │ └ properties │ ├ Data: (documentation changed) │ ├ Description: (documentation changed) │ ├ KmsKeyId: (documentation changed) │ ├ Name: (documentation changed) │ ├ Tags: (documentation changed) │ ├ Type: (documentation changed) │ ├ Uri: (documentation changed) │ └ Version: (documentation changed) ├[~] service aws-internetmonitor │ └ resources │ └[~] resource AWS::InternetMonitor::Monitor │ └ types │ ├[~] type InternetMeasurementsLogDelivery │ │ └ properties │ │ └ S3Config: (documentation changed) │ └[~] type S3Config │ ├ - documentation: The configuration for publishing Amazon CloudWatch Internet Monitor internet measurements to Amazon S3. The configuration includes the bucket name and (optionally) prefix for the S3 bucket to store the measurements, and the delivery status. The delivery status is `ENABLED` or `DISABLED` , depending on whether you choose to deliver internet measurements to S3 logs. │ │ + documentation: The configuration for publishing Amazon CloudWatch Internet Monitor internet measurements to Amazon S3. The configuration includes the bucket name and (optionally) bucket prefix for the S3 bucket to store the measurements, and the delivery status. The delivery status is `ENABLED` if you choose to deliver internet measurements to S3 logs, and `DISABLED` otherwise. │ │ The measurements are also published to Amazon CloudWatch Logs. │ └ properties │ ├ BucketName: (documentation changed) │ ├ BucketPrefix: (documentation changed) │ └ LogDeliveryStatus: (documentation changed) ├[~] service aws-iot │ └ resources │ └[~] resource AWS::IoT::DomainConfiguration │ ├ properties │ │ └ ServerCertificateConfig: (documentation changed) │ ├ attributes │ │ └ ServerCertificates: (documentation changed) │ └ types │ └[~] type ServerCertificateConfig │ ├ - documentation: undefined │ │ + documentation: The server certificate configuration. │ │ For more information, see [Configurable endpoints](https://docs.aws.amazon.com//iot/latest/developerguide/iot-custom-endpoints-configurable.html) from the AWS IoT Core Developer Guide. │ └ properties │ └ EnableOCSPCheck: (documentation changed) ├[~] service aws-iotevents │ └ resources │ ├[~] resource AWS::IoTEvents::AlarmModel │ │ └ types │ │ └[~] type Firehose │ │ └ properties │ │ └ Payload: (documentation changed) │ └[~] resource AWS::IoTEvents::DetectorModel │ └ types │ └[~] type Firehose │ └ properties │ └ Payload: (documentation changed) ├[~] service aws-iotfleetwise │ └ resources │ └[~] resource AWS::IoTFleetWise::SignalCatalog │ └ attributes │ ├ NodeCounts.TotalActuators: (documentation changed) │ ├ NodeCounts.TotalAttributes: (documentation changed) │ ├ NodeCounts.TotalBranches: (documentation changed) │ ├ NodeCounts.TotalNodes: (documentation changed) │ └ NodeCounts.TotalSensors: (documentation changed) ├[~] service aws-iottwinmaker │ └ resources │ ├[~] resource AWS::IoTTwinMaker::ComponentType │ │ └ attributes │ │ └ Status: (documentation changed) │ ├[~] resource AWS::IoTTwinMaker::Entity │ │ └ attributes │ │ └ Status: (documentation changed) │ └[~] resource AWS::IoTTwinMaker::Scene │ └ attributes │ └ GeneratedSceneMetadata: (documentation changed) ├[~] service aws-iotwireless │ └ resources │ ├[~] resource AWS::IoTWireless::FuotaTask │ │ └ attributes │ │ └ LoRaWAN.StartTime: (documentation changed) │ ├[~] resource AWS::IoTWireless::MulticastGroup │ │ └ attributes │ │ ├ LoRaWAN.NumberOfDevicesInGroup: (documentation changed) │ │ └ LoRaWAN.NumberOfDevicesRequested: (documentation changed) │ └[~] resource AWS::IoTWireless::ServiceProfile │ └ attributes │ ├ LoRaWAN.ChannelMask: (documentation changed) │ ├ LoRaWAN.DevStatusReqFreq: (documentation changed) │ ├ LoRaWAN.DlBucketSize: (documentation changed) │ ├ LoRaWAN.DlRate: (documentation changed) │ ├ LoRaWAN.DlRatePolicy: (documentation changed) │ ├ LoRaWAN.DrMax: (documentation changed) │ ├ LoRaWAN.DrMin: (documentation changed) │ ├ LoRaWAN.HrAllowed: (documentation changed) │ ├ LoRaWAN.MinGwDiversity: (documentation changed) │ ├ LoRaWAN.NwkGeoLoc: (documentation changed) │ ├ LoRaWAN.ReportDevStatusBattery: (documentation changed) │ ├ LoRaWAN.ReportDevStatusMargin: (documentation changed) │ ├ LoRaWAN.TargetPer: (documentation changed) │ ├ LoRaWAN.UlBucketSize: (documentation changed) │ ├ LoRaWAN.UlRate: (documentation changed) │ └ LoRaWAN.UlRatePolicy: (documentation changed) ├[~] service aws-kendra │ └ resources │ └[~] resource AWS::Kendra::DataSource │ └ types │ ├[~] type DataSourceConfiguration │ │ └ properties │ │ └ S3Configuration: (documentation changed) │ └[~] type S3DataSourceConfiguration │ ├ - documentation: Provides the configuration information to connect to an Amazon S3 bucket. │ │ > `S3DataSourceConfiguration` is deprecated. Amazon VPC is not supported if you configure your Amazon S3 connector with this method. Use [TemplateConfiguration](https://docs.aws.amazon.com/kendra/latest/APIReference/API_TemplateConfiguration.html) to configure your Amazon S3 connector instead. See [Amazon S3 template schema](https://docs.aws.amazon.com/kendra/latest/dg/ds-schemas.html#ds-s3-schema) for more details. │ │ + documentation: Provides the configuration information to connect to an Amazon S3 bucket. │ │ > Amazon Kendra now supports an upgraded Amazon S3 connector. │ │ > │ │ > You must now use the [TemplateConfiguration](https://docs.aws.amazon.com/kendra/latest/APIReference/API_TemplateConfiguration.html) object instead of the `S3DataSourceConfiguration` object to configure your connector. │ │ > │ │ > Connectors configured using the older console and API architecture will continue to function as configured. However, you won't be able to edit or update them. If you want to edit or update your connector configuration, you must create a new connector. │ │ > │ │ > We recommended migrating your connector workflow to the upgraded version. Support for connectors configured using the older architecture is scheduled to end by June 2024. │ └ properties │ ├ ExclusionPatterns: (documentation changed) │ └ InclusionPatterns: (documentation changed) ├[~] service aws-kinesisfirehose │ └ resources │ └[~] resource AWS::KinesisFirehose::DeliveryStream │ ├ properties │ │ └ SnowflakeDestinationConfiguration: (documentation changed) │ └ types │ ├[~] type AmazonOpenSearchServerlessDestinationConfiguration │ │ └ properties │ │ ├ RetryOptions: (documentation changed) │ │ ├ RoleARN: (documentation changed) │ │ └ S3BackupMode: (documentation changed) │ ├[~] type AmazonOpenSearchServerlessRetryOptions │ │ ├ - documentation: Configures retry behavior in case Kinesis Data Firehose is unable to deliver documents to the Serverless offering for Amazon OpenSearch Service. │ │ │ + documentation: Configures retry behavior in case Firehose is unable to deliver documents to the Serverless offering for Amazon OpenSearch Service. │ │ └ properties │ │ └ DurationInSeconds: (documentation changed) │ ├[~] type AmazonopensearchserviceDestinationConfiguration │ │ └ properties │ │ └ DocumentIdOptions: (documentation changed) │ ├[~] type DataFormatConversionConfiguration │ │ └ properties │ │ ├ InputFormatConfiguration: (documentation changed) │ │ └ OutputFormatConfiguration: (documentation changed) │ ├[~] type DeliveryStreamEncryptionConfigurationInput │ │ └ properties │ │ └ KeyARN: (documentation changed) │ ├[~] type Deserializer │ │ └ properties │ │ ├ HiveJsonSerDe: (documentation changed) │ │ └ OpenXJsonSerDe: (documentation changed) │ ├[~] type DocumentIdOptions │ │ ├ - documentation: Indicates the method for setting up document ID. The supported methods are Kinesis Data Firehose generated document ID and OpenSearch Service generated document ID. │ │ │ + documentation: Indicates the method for setting up document ID. The supported methods are Firehose generated document ID and OpenSearch Service generated document ID. │ │ └ properties │ │ └ DefaultDocumentIdFormat: (documentation changed) │ ├[~] type ElasticsearchDestinationConfiguration │ │ └ properties │ │ └ DocumentIdOptions: (documentation changed) │ ├[~] type HiveJsonSerDe │ │ ├ - documentation: The native Hive / HCatalog JsonSerDe. Used by Kinesis Data Firehose for deserializing data, which means converting it from the JSON format in preparation for serializing it to the Parquet or ORC format. This is one of two deserializers you can choose, depending on which one offers the functionality you need. The other option is the OpenX SerDe. │ │ │ + documentation: The native Hive / HCatalog JsonSerDe. Used by Firehose for deserializing data, which means converting it from the JSON format in preparation for serializing it to the Parquet or ORC format. This is one of two deserializers you can choose, depending on which one offers the functionality you need. The other option is the OpenX SerDe. │ │ └ properties │ │ └ TimestampFormats: (documentation changed) │ ├[~] type OpenXJsonSerDe │ │ ├ - documentation: The OpenX SerDe. Used by Kinesis Data Firehose for deserializing data, which means converting it from the JSON format in preparation for serializing it to the Parquet or ORC format. This is one of two deserializers you can choose, depending on which one offers the functionality you need. The other option is the native Hive / HCatalog JsonSerDe. │ │ │ + documentation: The OpenX SerDe. Used by Firehose for deserializing data, which means converting it from the JSON format in preparation for serializing it to the Parquet or ORC format. This is one of two deserializers you can choose, depending on which one offers the functionality you need. The other option is the native Hive / HCatalog JsonSerDe. │ │ └ properties │ │ ├ CaseInsensitive: (documentation changed) │ │ └ ConvertDotsInJsonKeysToUnderscores: (documentation changed) │ ├[~] type OrcSerDe │ │ └ properties │ │ ├ BlockSizeBytes: (documentation changed) │ │ └ BloomFilterColumns: (documentation changed) │ ├[~] type OutputFormatConfiguration │ │ └ - documentation: Specifies the serializer that you want Kinesis Data Firehose to use to convert the format of your data before it writes it to Amazon S3. This parameter is required if `Enabled` is set to true. │ │ + documentation: Specifies the serializer that you want Firehose to use to convert the format of your data before it writes it to Amazon S3. This parameter is required if `Enabled` is set to true. │ ├[~] type ParquetSerDe │ │ └ properties │ │ └ BlockSizeBytes: (documentation changed) │ ├[~] type RedshiftDestinationConfiguration │ │ └ properties │ │ └ RetryOptions: (documentation changed) │ ├[~] type RedshiftRetryOptions │ │ ├ - documentation: Configures retry behavior in case Kinesis Data Firehose is unable to deliver documents to Amazon Redshift. │ │ │ + documentation: Configures retry behavior in case Firehose is unable to deliver documents to Amazon Redshift. │ │ └ properties │ │ └ DurationInSeconds: (documentation changed) │ ├[~] type SchemaConfiguration │ │ ├ - documentation: Specifies the schema to which you want Kinesis Data Firehose to configure your data before it writes it to Amazon S3. This parameter is required if `Enabled` is set to true. │ │ │ + documentation: Specifies the schema to which you want Firehose to configure your data before it writes it to Amazon S3. This parameter is required if `Enabled` is set to true. │ │ └ properties │ │ ├ RoleARN: (documentation changed) │ │ └ VersionId: (documentation changed) │ ├[~] type Serializer │ │ └ - documentation: The serializer that you want Kinesis Data Firehose to use to convert data to the target format before writing it to Amazon S3. Kinesis Data Firehose supports two types of serializers: the [ORC SerDe](https://docs.aws.amazon.com/https://hive.apache.org/javadocs/r1.2.2/api/org/apache/hadoop/hive/ql/io/orc/OrcSerde.html) and the [Parquet SerDe](https://docs.aws.amazon.com/https://hive.apache.org/javadocs/r1.2.2/api/org/apache/hadoop/hive/ql/io/parquet/serde/ParquetHiveSerDe.html) . │ │ + documentation: The serializer that you want Firehose to use to convert data to the target format before writing it to Amazon S3. Firehose supports two types of serializers: the [ORC SerDe](https://docs.aws.amazon.com/https://hive.apache.org/javadocs/r1.2.2/api/org/apache/hadoop/hive/ql/io/orc/OrcSerde.html) and the [Parquet SerDe](https://docs.aws.amazon.com/https://hive.apache.org/javadocs/r1.2.2/api/org/apache/hadoop/hive/ql/io/parquet/serde/ParquetHiveSerDe.html) . │ ├[~] type SnowflakeDestinationConfiguration │ │ ├ - documentation: undefined │ │ │ + documentation: Configure Snowflake destination │ │ └ properties │ │ ├ AccountUrl: (documentation changed) │ │ ├ ContentColumnName: (documentation changed) │ │ ├ Database: (documentation changed) │ │ ├ DataLoadingOption: (documentation changed) │ │ ├ KeyPassphrase: (documentation changed) │ │ ├ MetaDataColumnName: (documentation changed) │ │ ├ PrivateKey: (documentation changed) │ │ ├ RetryOptions: (documentation changed) │ │ ├ RoleARN: (documentation changed) │ │ ├ S3BackupMode: (documentation changed) │ │ ├ Schema: (documentation changed) │ │ ├ SnowflakeRoleConfiguration: (documentation changed) │ │ ├ SnowflakeVpcConfiguration: (documentation changed) │ │ ├ Table: (documentation changed) │ │ └ User: (documentation changed) │ ├[~] type SnowflakeRetryOptions │ │ ├ - documentation: undefined │ │ │ + documentation: Specify how long Firehose retries sending data to the New Relic HTTP endpoint. After sending data, Firehose first waits for an acknowledgment from the HTTP endpoint. If an error occurs or the acknowledgment doesn’t arrive within the acknowledgment timeout period, Firehose starts the retry duration counter. It keeps retrying until the retry duration expires. After that, Firehose considers it a data delivery failure and backs up the data to your Amazon S3 bucket. Every time that Firehose sends data to the HTTP endpoint (either the initial attempt or a retry), it restarts the acknowledgement timeout counter and waits for an acknowledgement from the HTTP endpoint. Even if the retry duration expires, Firehose still waits for the acknowledgment until it receives it or the acknowledgement timeout period is reached. If the acknowledgment times out, Firehose determines whether there's time left in the retry counter. If there is time left, it retries again and repeats the logic until it receives an acknowledgment or determines that the retry time has expired. If you don't want Firehose to retry sending data, set this value to 0. │ │ └ properties │ │ └ DurationInSeconds: (documentation changed) │ ├[~] type SnowflakeRoleConfiguration │ │ ├ - documentation: undefined │ │ │ + documentation: Optionally configure a Snowflake role. Otherwise the default user role will be used. │ │ └ properties │ │ ├ Enabled: (documentation changed) │ │ └ SnowflakeRole: (documentation changed) │ ├[~] type SnowflakeVpcConfiguration │ │ ├ - documentation: undefined │ │ │ + documentation: Configure a Snowflake VPC │ │ └ properties │ │ └ PrivateLinkVpceId: (documentation changed) │ ├[~] type SplunkDestinationConfiguration │ │ └ properties │ │ ├ HECAcknowledgmentTimeoutInSeconds: (documentation changed) │ │ ├ HECEndpoint: (documentation changed) │ │ ├ RetryOptions: (documentation changed) │ │ └ S3BackupMode: (documentation changed) │ └[~] type SplunkRetryOptions │ └ properties │ └ DurationInSeconds: (documentation changed) ├[~] service aws-lambda │ └ resources │ └[~] resource AWS::Lambda::Permission │ └ attributes │ └ Id: (documentation changed) ├[~] service aws-lightsail │ └ resources │ ├[~] resource AWS::Lightsail::Container │ │ ├ properties │ │ │ └ PrivateRegistryAccess: (documentation changed) │ │ ├ attributes │ │ │ └ PrivateRegistryAccess.EcrImagePullerRole.PrincipalArn: (documentation changed) │ │ └ types │ │ └[~] type PrivateRegistryAccess │ │ └ - documentation: Describes the configuration for an Amazon Lightsail container service to access private container image repositories, such a…

aws-cdk-automation · 2024-02-21T13:50:29Z

AWS CodeBuild CI Report

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

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

mergify · 2024-02-21T13:50:51Z

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

aws-cdk-automation and others added 22 commits February 14, 2024 19:22

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

712306d

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

Merge branch 'main' into merge-back/2.128.0

fa183b1

chore(merge-back): 2.128.0 (#29115)

89df42d

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

chore(ec2): correct device name in BastionHostLinux example (#29114)

6fbcce6

Closes #29103. I tested the example and it deploys. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*

chore: mergify.yml cleanup (#29156)

d647eac

remove madeline-k and MrArnoldPalmer from mergify.yml ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*

chore(release): 2.129.0

66b3046

aws-cdk-automation added auto-approve pr/no-squash This PR should be merged instead of squash-merging it labels Feb 21, 2024

github-actions bot approved these changes Feb 21, 2024

View reviewed changes

aws-cdk-automation requested a review from a team February 21, 2024 13:18

github-actions bot added the p2 label Feb 21, 2024

aws-cdk-automation had a problem deploying to test-pipeline February 21, 2024 13:19 — with GitHub Actions Failure

chore: fixup changelog for 2.129.0

7378a63

mrgrain had a problem deploying to test-pipeline February 21, 2024 13:21 — with GitHub Actions Failure

chore: fixup changelog for 2.129.0 pt2

d81ed03

mrgrain had a problem deploying to test-pipeline February 21, 2024 13:24 — with GitHub Actions Failure

mergify bot merged commit d5ab0df into v2-release Feb 21, 2024
11 of 12 checks passed

mergify bot deleted the bump/2.129.0 branch February 21, 2024 13:51

github-actions bot mentioned this pull request Mar 1, 2024

Monthly PR metrics report - Feb 2023 #29328

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(release): 2.129.0 #29193

chore(release): 2.129.0 #29193

aws-cdk-automation commented Feb 21, 2024 •

edited

Loading

aws-cdk-automation commented Feb 21, 2024

mergify bot commented Feb 21, 2024

chore(release): 2.129.0 #29193

chore(release): 2.129.0 #29193

Conversation

aws-cdk-automation commented Feb 21, 2024 • edited Loading

aws-cdk-automation commented Feb 21, 2024

AWS CodeBuild CI Report

mergify bot commented Feb 21, 2024

aws-cdk-automation commented Feb 21, 2024 •

edited

Loading