Bump github.com/aws/aws-sdk-go-v2/service/ssm from 1.44.1 to 1.49.1 in /test/new-e2e

[dependabot]

Bumps github.com/aws/aws-sdk-go-v2/service/ssm from 1.44.1 to 1.49.1.

Changelog

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

Release (2022-07-18)

Module Highlights

• github.com/aws/aws-sdk-go-v2/service/applicationdiscoveryservice: v1.14.0
  • Feature: Add AWS Agentless Collector details to the GetDiscoverySummary API response
• github.com/aws/aws-sdk-go-v2/service/ec2: v1.49.1
  • Documentation: Documentation updates for Amazon EC2.
• github.com/aws/aws-sdk-go-v2/service/elasticache: v1.22.0
  • Feature: Adding AutoMinorVersionUpgrade in the DescribeReplicationGroups API
• github.com/aws/aws-sdk-go-v2/service/kms: v1.18.0
  • Feature: Added support for the SM2 KeySpec in China Partition Regions
• github.com/aws/aws-sdk-go-v2/service/mediapackage: v1.17.0
  • Feature: This release adds "IncludeIframeOnlyStream" for Dash endpoints and increases the number of supported video and audio encryption presets for Speke v2
• github.com/aws/aws-sdk-go-v2/service/sagemaker: v1.37.0
  • Feature: Amazon SageMaker Edge Manager provides lightweight model deployment feature to deploy machine learning models on requested devices.
• github.com/aws/aws-sdk-go-v2/service/ssoadmin: v1.15.0
  • Feature: AWS SSO now supports attaching customer managed policies and a permissions boundary to your permission sets. This release adds new API operations to manage and view the customer managed policies and the permissions boundary for a given permission set.

Release (2022-07-15)

Module Highlights

• github.com/aws/aws-sdk-go-v2/service/datasync: v1.18.3
  • Documentation: Documentation updates for AWS DataSync regarding configuring Amazon FSx for ONTAP location security groups and SMB user permissions.
• github.com/aws/aws-sdk-go-v2/service/drs: v1.7.0
  • Feature: Changed existing APIs to allow choosing a dynamic volume type for replicating volumes, to reduce costs for customers.
• github.com/aws/aws-sdk-go-v2/service/evidently: v1.8.0
  • Feature: This release adds support for the new segmentation feature.
• github.com/aws/aws-sdk-go-v2/service/wafv2: v1.21.0
  • Feature: This SDK release provide customers ability to add sensitivity level for WAF SQLI Match Statements.

Release (2022-07-14)

Module Highlights

• github.com/aws/aws-sdk-go-v2/service/athena: v1.17.0
  • Feature: This release updates data types that contain either QueryExecutionId, NamedQueryId or ExpectedBucketOwner. Ids must be between 1 and 128 characters and contain only non-whitespace characters. ExpectedBucketOwner must be 12-digit string.
• github.com/aws/aws-sdk-go-v2/service/codeartifact: v1.13.0
  • Feature: This release introduces Package Origin Controls, a mechanism used to counteract Dependency Confusion attacks. Adds two new APIs, PutPackageOriginConfiguration and DescribePackage, and updates the ListPackage, DescribePackageVersion and ListPackageVersion APIs in support of the feature.
• github.com/aws/aws-sdk-go-v2/service/configservice: v1.22.0
  • Feature: Update ResourceType enum with values for Route53Resolver, Batch, DMS, Workspaces, Stepfunctions, SageMaker, ElasticLoadBalancingV2, MSK types
• github.com/aws/aws-sdk-go-v2/service/ec2: v1.49.0
  • Feature: This release adds flow logs for Transit Gateway to allow customers to gain deeper visibility and insights into network traffic through their Transit Gateways.
• github.com/aws/aws-sdk-go-v2/service/fms: v1.18.0
  • Feature: Adds support for strict ordering in stateful rule groups in Network Firewall policies.
• github.com/aws/aws-sdk-go-v2/service/glue: v1.28.0
  • Feature: This release adds an additional worker type for Glue Streaming jobs.
• github.com/aws/aws-sdk-go-v2/service/inspector2: v1.7.0
  • Feature: This release adds support for Inspector V2 scan configurations through the get and update configuration APIs. Currently this allows configuring ECR automated re-scan duration to lifetime or 180 days or 30 days.
• github.com/aws/aws-sdk-go-v2/service/kendra: v1.30.0
  • Feature: This release adds AccessControlConfigurations which allow you to redefine your document level access control without the need for content re-indexing.
• github.com/aws/aws-sdk-go-v2/service/nimble: v1.13.0

... (truncated)

Commits

• 565f0a4 Release 2022-07-18
• aa18c98 Regenerated Clients
• 117b93d Update endpoints model
• 4bf303b Update API model
• 6fb212b Release 2022-07-15
• ead7556 Regenerated Clients
• 2a87efc Update endpoints model
• b66beb9 Update API model
• 583c59b Fix codegen bug for header-only events (#1766)
• ff04207 Release 2022-07-14
• Additional commits viewable in compare view

You can trigger a rebase of this PR 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)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[pr-commenter]

Bloop Bleep... Dogbot Here

Regression Detector Results

Run ID: 44f1bbf-2e86-455c-8f2f-c7fd3f6c080b
Baseline: e45cfd9
Comparison: ed9302c

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

Experiments with missing or malformed data

• basic_py_check

Usually, this warning means that there is no usable optimization goal data for that experiment, which could be a result of misconfiguration.

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.

Experiments ignored for regressions

Regressions in experiments with settings containing erratic: true are ignored.

perf	experiment	goal	Δ mean %	Δ mean % CI
➖	file_to_blackhole	% cpu utilization	+1.25	[-5.32, +7.81]

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI
➖	uds_dogstatsd_to_api_cpu	% cpu utilization	+1.46	[+0.03, +2.89]
➖	file_to_blackhole	% cpu utilization	+1.25	[-5.32, +7.81]
➖	file_tree	memory utilization	+0.48	[+0.37, +0.59]
➖	trace_agent_msgpack	ingress throughput	+0.03	[+0.01, +0.04]
➖	tcp_dd_logs_filter_exclude	ingress throughput	+0.00	[-0.00, +0.00]
➖	uds_dogstatsd_to_api	ingress throughput	+0.00	[-0.00, +0.00]
➖	trace_agent_json	ingress throughput	-0.00	[-0.03, +0.03]
➖	process_agent_standard_check_with_stats	memory utilization	-0.07	[-0.10, -0.04]
➖	process_agent_real_time_mode	memory utilization	-0.15	[-0.20, -0.10]
➖	tcp_syslog_to_blackhole	ingress throughput	-0.25	[-0.30, -0.19]
➖	otel_to_otel_logs	ingress throughput	-0.49	[-1.12, +0.14]
➖	idle	memory utilization	-0.87	[-0.93, -0.82]
➖	process_agent_standard_check	memory utilization	-1.18	[-1.21, -1.14]

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

[paulcacheux]

@dependabot rebase

[pr-commenter]

Regression Detector

Regression Detector Results

Run ID: 6672cec5-9cd5-409a-ae19-04fcb5047b7d Metrics dashboard Target profiles

Baseline: 6a6c459
Comparison: 04ab35e

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	links
➖	tcp_syslog_to_blackhole	ingress throughput	+4.54	[-8.80, +17.87]	Logs
➖	uds_dogstatsd_to_api_cpu	% cpu utilization	+0.99	[+0.08, +1.89]	Logs
➖	file_tree	memory utilization	+0.57	[+0.48, +0.66]	Logs
➖	pycheck_1000_100byte_tags	% cpu utilization	+0.57	[-4.27, +5.40]	Logs
➖	basic_py_check	% cpu utilization	+0.10	[-2.58, +2.77]	Logs
➖	uds_dogstatsd_to_api	ingress throughput	+0.00	[-0.00, +0.00]	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	-0.00	[-0.01, +0.01]	Logs
➖	idle	memory utilization	-0.02	[-0.07, +0.03]	Logs
➖	otel_to_otel_logs	ingress throughput	-0.90	[-1.70, -0.09]	Logs

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