Bump github.com/aws/aws-sdk-go-v2/service/rds from 1.80.1 to 1.83.0

[dependabot[bot]]

Bumps github.com/aws/aws-sdk-go-v2/service/rds from 1.80.1 to 1.83.0.

Changelog

Sourced from github.com/aws/aws-sdk-go-v2/service/rds's changelog.

Release (2023-01-31)

Module Highlights

• github.com/aws/aws-sdk-go-v2/service/appsync: v1.19.0
  • Feature: This release introduces the feature to support EventBridge as AppSync data source.
• github.com/aws/aws-sdk-go-v2/service/cloudtrail: v1.23.0
  • Feature: Add new "Channel" APIs to enable users to manage channels used for CloudTrail Lake integrations, and "Resource Policy" APIs to enable users to manage the resource-based permissions policy attached to a channel.
• github.com/aws/aws-sdk-go-v2/service/cloudtraildata: v1.0.0
  • Release: New AWS service client module
  • Feature: Add CloudTrail Data Service to enable users to ingest activity events from non-AWS sources into CloudTrail Lake.
• github.com/aws/aws-sdk-go-v2/service/codeartifact: v1.16.0
  • Feature: This release introduces a new DeletePackage API, which enables deletion of a package and all of its versions from a repository.
• github.com/aws/aws-sdk-go-v2/service/ec2: v1.83.0
  • Feature: This launch allows customers to associate up to 8 IP addresses to their NAT Gateways to increase the limit on concurrent connections to a single destination by eight times from 55K to 440K.
• github.com/aws/aws-sdk-go-v2/service/groundstation: v1.17.0
  • Feature: DigIF Expansion changes to the Customer APIs.
• github.com/aws/aws-sdk-go-v2/service/iot: v1.34.0
  • Feature: Added support for IoT Rules Engine Cloudwatch Logs action batch mode.
• github.com/aws/aws-sdk-go-v2/service/opensearch: v1.14.0
  • Feature: Amazon OpenSearch Service adds the option for a VPC endpoint connection between two domains when the local domain uses OpenSearch version 1.3 or 2.3. You can now use remote reindex to copy indices from one VPC domain to another without a reverse proxy.
• github.com/aws/aws-sdk-go-v2/service/polly: v1.24.0
  • Feature: Amazon Polly adds two new neural American English voices - Ruth, Stephen
• github.com/aws/aws-sdk-go-v2/service/sagemaker: v1.67.0
  • Feature: Amazon SageMaker Automatic Model Tuning now supports more completion criteria for Hyperparameter Optimization.
• github.com/aws/aws-sdk-go-v2/service/securityhub: v1.28.0
  • Feature: New fields have been added to the AWS Security Finding Format. Compliance.SecurityControlId is a unique identifier for a security control across standards. Compliance.AssociatedStandards contains all enabled standards in which a security control is enabled.

Release (2023-01-30)

Module Highlights

• github.com/aws/aws-sdk-go-v2/service/cloudformation: v1.26.0
  • Feature: This feature provides a method of obtaining which regions a stackset has stack instances deployed in.
• github.com/aws/aws-sdk-go-v2/service/ec2: v1.82.0
  • Feature: We add Prefix Lists as a new route destination option for LocalGatewayRoutes. This will allow customers to create routes to Prefix Lists. Prefix List routes will allow customers to group individual CIDR routes with the same target into a single route.

Release (2023-01-27)

Module Highlights

• github.com/aws/aws-sdk-go-v2/service/appstream: v1.20.0
  • Feature: Fixing the issue where Appstream waiters hang for fleet_started and fleet_stopped.
• github.com/aws/aws-sdk-go-v2/service/mediatailor: v1.21.0
  • Feature: This release introduces the As Run logging type, along with API and documentation updates.
• github.com/aws/aws-sdk-go-v2/service/outposts: v1.26.0
  • Feature: Adding support for payment term in GetOrder, CreateOrder responses.
• github.com/aws/aws-sdk-go-v2/service/sagemaker: v1.66.0
  • Feature: This release supports running SageMaker Training jobs with container images that are in a private Docker registry.
• github.com/aws/aws-sdk-go-v2/service/sagemakerruntime: v1.18.0
  • Feature: Amazon SageMaker Runtime which supports InvokeEndpointAsync asynchronously can now invoke endpoints with custom timeout values. Asynchronous invocations support longer processing times.

Release (2023-01-26)

... (truncated)

Commits

• 51207f8 Release 2023-01-31
• c588861 Regenerated Clients
• f52d51e Update endpoints model
• 2678f5f Update API model
• 968965a Release 2023-01-30
• b8f57f4 Regenerated Clients
• 2e72b02 Update API model
• 28e7ef8 Release 2023-01-27
• fc79bb2 Regenerated Clients
• f17b1d5 Update API model
• 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 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)

[pr-commenter[bot]]

Regression Detector

Regression Detector Results

Run ID: f025bb93-6ef1-49ec-ac95-d14a96adeb77 Metrics dashboard Target profiles

Baseline: 8599a94b76a9968510da2783080bd3ce076e086b Comparison: 555dc7dc5996ebf507b5c7c3cabec5ecebb9eb08

Performance changes are noted in the perf column of each table:

• ✅ = significantly better comparison variant performance
• ❌ = significantly worse comparison variant performance
• ➖ = no significant change in performance

No significant changes in experiment optimization goals

Confidence level: 90.00% Effect size tolerance: |Δ mean %| ≥ 5.00%

There were no significant changes in experiment optimization goals at this confidence level and effect size tolerance.

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	pycheck_lots_of_tags	% cpu utilization	+1.88	[-0.83, +4.59]	1	Logs
➖	basic_py_check	% cpu utilization	+0.49	[-2.28, +3.26]	1	Logs
➖	uds_dogstatsd_to_api	ingress throughput	-0.00	[-0.00, +0.00]	1	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	-0.00	[-0.01, +0.01]	1	Logs
➖	file_tree	memory utilization	-0.08	[-0.19, +0.04]	1	Logs
➖	idle	memory utilization	-0.41	[-0.46, -0.35]	1	Logs
➖	uds_dogstatsd_to_api_cpu	% cpu utilization	-0.86	[-1.61, -0.11]	1	Logs
➖	otel_to_otel_logs	ingress throughput	-0.92	[-1.74, -0.10]	1	Logs
➖	tcp_syslog_to_blackhole	ingress throughput	-1.05	[-1.10, -1.00]	1	Logs

Bounds Checks

perf	experiment	bounds_check_name	replicates_passed
❌	idle	memory_usage	7/10

Explanation

A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".

For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:

1. Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.

2. Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.

3. Its configuration does not mark it "erratic".

[dependabot[bot]]

Superseded by #29524.