Adding IPv6 e2e tests to test workflow

[Paramadon]

Description of the issue

Currently we are working on adding EKS IPv6 support for the Cloudwatch Agent, we need to add EKS integration testing to ensure Cloudwatch Agent will work on IPv6 environments

Also have relevant prs that are also included in this change:
Helm Chart: aws-observability/helm-charts#254
Integ test:

Description of changes

We are having all current IPv4 EKS e2e tests that exist to also run for IPv6. How we are doing this is we are making the cluster have ip family IPv6 and using a dualstack subnet vpc. We can not create dualstack vpc on each run as there is a limit of dualstack we can create so we are using an existing subnet for testing.

Here's some info on subnet

Tests

Passing test run: https://github.com/aws/amazon-cloudwatch-agent/actions/runs/19836119811

Subnet Info

Internet traffic for both ipv4 and ipv6

Cluster info being ipv6

Have more testing showcased in helm chart pr: aws-observability/helm-charts#254

To fix the problem, add a permissions key to the workflow file .github/workflows/e2e-test.yml. The permissions block can be placed at the root of the workflow (recommended), just below the name and env blocks and before the on block. This will apply least-privilege permissions (by default, no access to actions, contents, deployments, issues, checks, packages, pull-requests, statuses) for all jobs in the workflow unless overridden or expanded in specific jobs. For jobs that require specific permissions, expand the block accordingly. As a minimal fix, adding permissions: {} will enable the strictest setting (no permissions). If, for example, jobs only need to read repository contents, use permissions: contents: read.

The required change is to add:

permissions: {}

on a new line after the name definition and before env, or just after env before the on block.

---

To fix this problem, add a permissions block specifying the minimum required access for the GITHUB_TOKEN. The best approach is to add this block at the top level of the workflow YAML file (just below name: and above env:), so permissions apply to all jobs by default unless overridden per job. If jobs require only read access to repository contents, specify contents: read. If any job requires additional privileges, you can extend the block accordingly, but a minimal starting point is just contents: read. Since the full requirements of each job aren't known from the snippet, we'll add a safe minimal block:

permissions:
  contents: read

If certain jobs require greater permissions, you could add per-job overrides later. For now, insert the block after the name: field.

---

To fix this issue, add an explicit permissions: block to the workflow file, specifying the minimal privileges needed.

• The best way is to apply the permissions block at the root of the workflow, affecting all jobs that do not override it. This ensures the GITHUB_TOKEN used by all steps/given jobs does not have excessive permissions (such as unnecessary write access).
• For an e2e testing workflow, typically only contents: read is necessary. If jobs require more (e.g., to update PRs), you can add those types with write access.
• The change should be placed immediately after the name: field and before any trigger or environment blocks for readability and best practice.

No other methods or imports are required; this is a purely YAML configuration change within .github/workflows/e2e-test.yml.

---

To fix the problem, an explicit permissions block must be added either at the workflow root (applies to all jobs) or specifically to the job flagged by CodeQL. The minimal and safest starting point is to set permissions: {} to grant no default permissions, considering fine-tuned scopes can be added as needed later.

Single best fix:
Add a permissions: {} block at the top of the workflow, after the name: field, but before or after env: (both are valid, but after name: and before any top-level keys like env: is standard). This ensures all jobs run with the least privileges unless individual jobs override this explicitly.

Region/lines to change:
Insert the following lines in .github/workflows/e2e-test.yml after the name: Run E2E Tests line (line 4). No imports, definitions, or other methods are needed; only the YAML is updated.

---