Backport prebaked Debian 11 E2E AMI

[KevinFairise2]

What does this PR do?

Backports the prebaked Debian 11 E2E AMI change from #55986 to 7.83.x.

• Runs Debian 11 x86_64 E2E jobs on the 11-e2e AMI.
• Skips runtime installation of dependencies already baked into that image.
• Keeps the accompanying descriptor parsing and IoT package cleanup changes from the upstream commit.

Motivation

Debian 11 reached EOL, so its bullseye-security repository metadata expired and repeatedly broke the DDOT Debian E2E job before the test assertions ran. Main was fixed by #55986; the release branch still used the old image and remained affected by IR-60343.

Describe how you validated your changes

Confirmed the cherry-pick applies cleanly after preserving two files already deleted from 7.83.x. Tests were not run at the request of the reporter. An initial compile-only dda inv test attempt could not start because Go 1.26.7 is not installed in the environment.

Additional Notes

This is a backport of commit 1a25b6d4968f193ac4790ba9f67c9c35a7458963 from #55986.

---

PR by Bits - View session in Datadog

Comment @DataDog to request changes

[datadog-datadog-prod-us1-2]

View session in Datadog

Bits Code status: ✅ Done

Comment @DataDog to request changes

[datadog-datadog-prod-us1-2]

I can only run on private repositories.

[temporal-github-worker-1]

Backport evaluation: View Slack thread

[dd-octo-sts]

Gitlab CI Configuration Changes

Updated: .gitlab-ci.yml

⚠️ Diff too large to display on Github.

Changes Summary

Removed	Modified	Added	Renamed
1	76	4	0

Updated: .gitlab/distribution.yml

⚠️ Diff too large to display on Github.

Changes Summary

Removed	Modified	Added	Renamed
3	0	0	0

ℹ️ Diff available in the job log.

[datadog-datadog-prod-us1-2]

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 52.17% (-0.10%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 5dc6c5a | Docs | View more details | Give us feedback!}

[dd-octo-sts]

Files inventory check summary

File checks results against ancestor 285e6c51:

Results for datadog-agent_7.83.1.git.7.5dc6c5a.pipeline.136717887-1_amd64.deb:

No change detected

Results for datadog-iot-agent_7.83.1.git.7.5dc6c5a.pipeline.136717887-1_amd64.deb:

No change detected

[cit-pr-commenter-54b7da]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Job ID: 2b304d96-5c31-4625-8197-e999083cf335

Baseline: 285e6c5
Comparison: 5dc6c5a
Diff

Optimization Goals: ✅ No significant changes detected

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	quality_gate_logs	% cpu utilization	+2.45	[+1.56, +3.33]	1	Logs bounds checks dashboard
➖	quality_gate_metrics_logs	memory utilization	+1.17	[+0.92, +1.42]	1	Logs bounds checks dashboard
➖	quality_gate_security_mean_fs_load	memory utilization	-0.01	[-0.08, +0.06]	1	Logs bounds checks dashboard
➖	quality_gate_private_action_runner	memory utilization	-0.05	[-0.17, +0.07]	1	Logs bounds checks dashboard
➖	quality_gate_idle	memory utilization	-0.11	[-0.22, +0.01]	1	Logs bounds checks dashboard
➖	quality_gate_idle_all_features	memory utilization	-0.11	[-0.15, -0.07]	1	Logs bounds checks dashboard
➖	quality_gate_security_no_fs_load	memory utilization	-0.18	[-0.33, -0.04]	1	Logs bounds checks dashboard
➖	quality_gate_security_idle	memory utilization	-0.23	[-0.34, -0.13]	1	Logs bounds checks dashboard

Bounds Checks: ❌ Failed

perf	experiment	bounds_check_name	replicates_passed	observed_value	links
✅	quality_gate_idle	intake_connections	10/10	4 = 4	bounds checks dashboard
❌	quality_gate_idle	memory_usage	0/10	172.00MiB > 154MiB	bounds checks dashboard
✅	quality_gate_idle	total_bytes_received	10/10	746.15KiB ≤ 819.20KiB	bounds checks dashboard
✅	quality_gate_idle_all_features	intake_connections	10/10	4 = 4	bounds checks dashboard
❌	quality_gate_idle_all_features	memory_usage	8/10	516.58MiB > 512MiB	bounds checks dashboard
✅	quality_gate_idle_all_features	total_bytes_received	10/10	1.13MiB ≤ 1.25MiB	bounds checks dashboard
✅	quality_gate_logs	intake_connections	10/10	4 ≤ 6	bounds checks dashboard
❌	quality_gate_logs	memory_usage	4/10	201.44MiB > 195MiB	bounds checks dashboard
✅	quality_gate_logs	missed_bytes	10/10	0B = 0B	bounds checks dashboard
✅	quality_gate_logs	total_bytes_received	10/10	263.98MiB ≤ 292MiB	bounds checks dashboard
✅	quality_gate_metrics_logs	cpu_usage	10/10	377.25 ≤ 2000	bounds checks dashboard
✅	quality_gate_metrics_logs	intake_connections	10/10	4 ≤ 6	bounds checks dashboard
✅	quality_gate_metrics_logs	memory_usage	10/10	406.98MiB ≤ 430MiB	bounds checks dashboard
✅	quality_gate_metrics_logs	missed_bytes	10/10	0B = 0B	bounds checks dashboard
✅	quality_gate_metrics_logs	total_bytes_received	10/10	0.94GiB ≤ 1.04GiB	bounds checks dashboard
✅	quality_gate_private_action_runner	memory_usage	10/10	70.65MiB ≤ 75MiB	bounds checks dashboard
✅	quality_gate_security_idle	cpu_usage	10/10	32.90 ≤ 100	bounds checks dashboard
✅	quality_gate_security_idle	memory_usage	10/10	328.40MiB ≤ 330MiB	bounds checks dashboard
✅	quality_gate_security_mean_fs_load	cpu_usage	10/10	61.15 ≤ 200	bounds checks dashboard
✅	quality_gate_security_mean_fs_load	memory_usage	10/10	299.34MiB ≤ 310MiB	bounds checks dashboard
✅	quality_gate_security_no_fs_load	cpu_usage	10/10	20.81 ≤ 100	bounds checks dashboard
✅	quality_gate_security_no_fs_load	memory_usage	10/10	311.94MiB ≤ 320MiB	bounds checks dashboard

Explanation

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

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

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

CI Pass/Fail Decision

❌ Failed. Some Quality Gates were violated.

• quality_gate_security_no_fs_load, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
• quality_gate_security_no_fs_load, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_idle_all_features, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_idle_all_features, bounds check total_bytes_received: 10/10 replicas passed. Gate passed.
• quality_gate_idle_all_features, bounds check memory_usage: 8/10 replicas passed. Failed 2 which is > 0. Gate FAILED.
• quality_gate_idle, bounds check total_bytes_received: 10/10 replicas passed. Gate passed.
• quality_gate_idle, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_idle, bounds check memory_usage: 0/10 replicas passed. Failed 10 which is > 0. Gate FAILED.
• quality_gate_private_action_runner, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_security_mean_fs_load, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_security_mean_fs_load, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check memory_usage: 4/10 replicas passed. Failed 6 which is > 0. Gate FAILED.
• quality_gate_logs, bounds check missed_bytes: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check total_bytes_received: 10/10 replicas passed. Gate passed.
• quality_gate_security_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_security_idle, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check missed_bytes: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check total_bytes_received: 10/10 replicas passed. Gate passed.