chore(deps): bump awscli from 1.25.70 to 1.27.27 in /packages/@aws-cdk/lambda-layer-awscli

[dependabot]

Bumps awscli from 1.25.70 to 1.27.27.

Changelog

Sourced from awscli's changelog.

1.27.27

• api-change:iotfleetwise: Deprecated assignedValue property for actuators and attributes. Added a message to invalid nodes and invalid decoder manifest exceptions.
• api-change:logs: Doc-only update for CloudWatch Logs, for Tagging Permissions clarifications
• api-change:medialive: Link devices now support buffer size (latency) configuration. A higher latency value means a longer delay in transmitting from the device to MediaLive, but improved resiliency. A lower latency value means a shorter delay, but less resiliency.
• api-change:mediapackage-vod: This release provides the approximate number of assets in a packaging group.

1.27.26

• api-change:autoscaling: Adds support for metric math for target tracking scaling policies, saving you the cost and effort of publishing a custom metric to CloudWatch. Also adds support for VPC Lattice by adding the Attach/Detach/DescribeTrafficSources APIs and a new health check type to the CreateAutoScalingGroup API.
• api-change:iottwinmaker: This release adds the following new features: 1) New APIs for managing a continuous sync of assets and asset models from AWS IoT SiteWise. 2) Support user friendly names for component types (ComponentTypeName) and properties (DisplayName).
• api-change:migrationhubstrategy: This release adds known application filtering, server selection for assessments, support for potential recommendations, and indications for configuration and assessment status. For more information, see the AWS Migration Hub documentation at https://docs.aws.amazon.com/migrationhub/index.html

1.27.25

• api-change:ce: This release adds the LinkedAccountName field to the GetAnomalies API response under RootCause
• api-change:cloudfront: Introducing UpdateDistributionWithStagingConfig that can be used to promote the staging configuration to the production.
• api-change:eks: Adds support for EKS add-ons configurationValues fields and DescribeAddonConfiguration function
• api-change:kms: Updated examples and exceptions for External Key Store (XKS).

1.27.24

• api-change:billingconductor: This release adds the Tiering Pricing Rule feature.
• api-change:connect: This release provides APIs that enable you to programmatically manage rules for Contact Lens conversational analytics and third party applications. For more information, see https://docs.aws.amazon.com/connect/latest/APIReference/rules-api.html
• api-change:dynamodb: Endpoint Ruleset update: Use http instead of https for the "local" region.
• api-change:dynamodbstreams: Update dynamodbstreams command to latest version
• api-change:rds: This release adds the BlueGreenDeploymentNotFoundFault to the AddTagsToResource, ListTagsForResource, and RemoveTagsFromResource operations.
• api-change:sagemaker-featurestore-runtime: For online + offline Feature Groups, added ability to target PutRecord and DeleteRecord actions to only online store, or only offline store. If target store parameter is not specified, actions will apply to both stores.

1.27.23

• bugfix:codeartifact login: Ignore always-auth errors for CodeArtifact login command; fixes [#7434](https://github.com/aws/aws-cli/issues/7434) <https://github.com/aws/aws-cli/issues/7434>__
• api-change:ce: This release introduces two new APIs that offer a 1-click experience to refresh Savings Plans recommendations. The two APIs are StartSavingsPlansPurchaseRecommendationGeneration and ListSavingsPlansPurchaseRecommendationGeneration.
• api-change:ec2: Documentation updates for EC2.
• api-change:ivschat: Adds PendingVerification error type to messaging APIs to block the resource usage for accounts identified as being fraudulent.
• api-change:rds: This release adds the InvalidDBInstanceStateFault to the RestoreDBClusterFromSnapshot operation.
• api-change:transcribe: Amazon Transcribe now supports creating custom language models in the following languages: Japanese (ja-JP) and German (de-DE).

1.27.22

... (truncated)

Commits

• 5f499c1 Merge branch 'release-1.27.27'
• 1c99eaf Bumping version to 1.27.27
• 4d9095d Update changelog based on model updates
• 1047b04 Merge branch 'release-1.27.26'
• c89dec4 Merge branch 'release-1.27.26' into develop
• 8247826 Bumping version to 1.27.26
• f957975 Update changelog based on model updates
• 36b3360 Added deprecation notice for debugging tool in help text (#7510)
• 006e1a2 Merge branch 'release-1.27.25'
• 3f5758b Merge branch 'release-1.27.25' into develop
• Additional commits viewable in compare view

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 commands and options

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

[dependabot]

The following labels could not be found: auto-approve.

[dependabot]

Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting @dependabot rebase.