Bump github.com/aws/aws-sdk-go-v2/service/ec2 from 1.165.1 to 1.177.3

[dependabot]

Bumps github.com/aws/aws-sdk-go-v2/service/ec2 from 1.165.1 to 1.177.3.

Commits

• 09f0452 Release 2024-09-10
• 6b06ab7 Regenerated Clients
• bc16d20 Update endpoints model
• 8da8496 Update API model
• 786e8a6 Release 2024-09-09
• a32bbb3 Regenerated Clients
• 4700ce3 Update endpoints model
• 57ad596 Update API model
• 827d25d Release 2024-09-06
• 62ee855 Regenerated Clients
• 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)

[cit-pr-commenter]

Go Package Import Differences

Baseline: f78e4b2
Comparison: f106c94

binary	os	arch	change
process-agent	linux	amd64	+0, -1 -github.com/jmespath/go-jmespath
process-agent	linux	arm64	+0, -1 -github.com/jmespath/go-jmespath
process-agent	windows	amd64	+0, -1 -github.com/jmespath/go-jmespath
process-agent	darwin	amd64	+0, -1 -github.com/jmespath/go-jmespath
process-agent	darwin	arm64	+0, -1 -github.com/jmespath/go-jmespath

[pr-commenter]

Regression Detector

Regression Detector Results

Run ID: 0a6dc263-abe0-4256-90b5-4ccaae8815e1 Metrics dashboard Target profiles

Baseline: f78e4b2
Comparison: f106c94

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
➖	basic_py_check	% cpu utilization	+2.06	[-0.81, +4.93]	1	Logs
➖	pycheck_lots_of_tags	% cpu utilization	+0.88	[-1.79, +3.55]	1	Logs
➖	idle	memory utilization	+0.59	[+0.55, +0.64]	1	Logs
➖	file_tree	memory utilization	+0.39	[+0.28, +0.50]	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
➖	uds_dogstatsd_to_api_cpu	% cpu utilization	-0.07	[-0.84, +0.70]	1	Logs
➖	tcp_syslog_to_blackhole	ingress throughput	-0.56	[-0.61, -0.51]	1	Logs
➖	otel_to_otel_logs	ingress throughput	-0.63	[-1.45, +0.19]	1	Logs

Bounds Checks

perf	experiment	bounds_check_name	replicates_passed
✅	idle	memory_usage	10/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]

Superseded by #29525.