[AWS Fargate] Add memory hard limit from container metadata and remove usage percentage

[lucian-ioan]

Proposed commit message

Add memory hard limit from container metadata and remove usage percentage.

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Author's Checklist

• [ ]

How to test this PR locally

1. Follow the AWS Fargate blogpost to create to set up the integration and create the resources.

2. Be sure that your resource has cmd execution rights, for example add "enable-execute-command" argument while creating the resource via the AWS CLI:

aws ecs create-service \
    --cluster cluster-name \
    --task-definition task-definition-name \
    --enable-execute-command \
    --service-name service-name \
    --desired-count 1

3. Run the shell via AWS CLI via:

aws ecs execute-command --cluster cluster-name \
    --task task-id \
    --container container-name \
    --interactive \
    --command "/bin/sh"

4. Retrieve ECS_CONTAINER_METADATA_URI_V4 via echo $ECS_CONTAINER_METADATA_URI_V4.

5. Fetch task data via curl:

curl $ECS_CONTAINER_METADATA_URI_V4/task
curl $ECS_CONTAINER_METADATA_URI_V4/task/stats

6. Check data with the one fetched from the agent deployed in AWS (note that the agent needs to be built from the code in this PR).

Related issues

• Closes [AWS Fargate] Add Memory Hard Limit from container metadata #37120

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @lucian-ioan? 🙏.
For such, you'll need to label your PR with:

• The upcoming major version of the Elastic Stack
• The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

[lalit-satapathy]

CC: @agithomas @shmsr to planing the review once the PR is opened.

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-11-30T14:29:49.526+0000

• Duration: 75 min 45 sec

Test stats 🧪

Test	Results
Failed	0
Passed	4698
Skipped	1015
Total	5713

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Duration: 70 min 42 sec

❕ Flaky test report

No test was executed to be analysed.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[gpop63]

@lucian-ioan you were able to get actual container limits while testing this with a custom built agent containing these changes, right?

[lucian-ioan]

@gpop63 yes, tested multiple times and the memory limits line up with what I set in AWS.

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-12-05T20:44:37.193+0000

• Duration: 78 min 33 sec

Test stats 🧪

Test	Results
Failed	0
Passed	4650
Skipped	1015
Total	5665

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)