[AWS Metrics] Enable agentless mode for AWS metrics Integrations #19283

Activity

1. MichaelKatsoulis

   self-assigned this

   on May 29, 2026
2. github-actions commented on May 29, 2026

   

   github-actionsBot

   on May 29, 2026 – with GitHub Actions

   Contributor

   More actions

   tl;dr: packages/aws/manifest.yml still has many aws/metrics policy templates without deployment_modes.agentless, so AWS metrics agentless enablement is only partial today; the next step is to finish manifest parity across the remaining metrics templates, then update docs/changelog in the same PR.

   Recommendation

   Implement agentless enablement as a manifest-completion pass across remaining AWS metrics policy templates, not as a one-off per stream. The strongest blocker is missing deployment_modes.agentless on multiple metrics templates (for example cloudwatch, ebs, ec2, etc.), while other metrics templates already follow the expected pattern.

   Findings

   1. Mixed state in packages/aws/manifest.yml: some metrics templates are agentless-enabled, others are not.

      • packages/aws/manifest.yml:252-259 (dynamodb) includes:
        • deployment_modes.default.enabled: true
        • deployment_modes.agentless.enabled: true
      • packages/aws/manifest.yml:270-283 (ebs) has input: aws/metrics but no deployment_modes block.
      • packages/aws/manifest.yml:185-203 (cloudwatch) includes aws/metrics input but no deployment_modes (next template starts at :208).

   2. I enumerated all aws/metrics templates from packages/aws/manifest.yml; current state is partially enabled:

      • agentless=yes: awshealth, billing, dynamodb, elb, lambda, rds, sns, sqs, transitgateway
      • agentless=no: cloudwatch, ebs, ec2, ecs, natgateway, firewall, s3, s3_storage_lens, usage, vpn, redshift, kinesis, apigateway, emr, kafka

   3. Prior PRs and changelog entries show the intended pattern is exactly “enable agentless per metrics template” in manifest.yml + docs/changelog updates.

      • packages/aws/changelog.yml:42-85 references a sequence of prior enables (RDS/DynamoDB/SNS/Transitgateway/Billing/Health/SQS/ELB/Lambda).
      • Example implementation pattern visible in PR #18584 (RDS): added deployment_modes.agentless for the RDS metrics template plus docs/changelog updates.

   4. Context limitation: issue body/comments were not readable in this runner, so this triage is based on the issue title and repository evidence.

   Verification

   I verified directly in the workspace with targeted commands:

   $ nl -ba packages/aws/manifest.yml | sed -n '180,220p;240,290p'
   ... cloudwatch has aws/metrics input (199-202) and no deployment_modes before next template ...
   ... dynamodb has deployment_modes with agentless (252-259) ...
   ... ebs has aws/metrics input (279-282) and no deployment_modes ...
   
   $ python - <<'PY'
   import yaml
   obj=yaml.safe_load(open('packages/aws/manifest.yml'))
   for pt in obj['policy_templates']:
       if any(i.get('type')=='aws/metrics' for i in pt.get('inputs',[])):
           dm=pt.get('deployment_modes',{}) or {}
           print(pt['name'], ((dm.get('agentless') or {}).get('enabled')==True))
   PY
   # Output confirmed partial coverage (9 enabled, 15 not enabled)
   

   Detailed Action Plan

   1. Complete manifest agentless coverage for remaining metrics templates in packages/aws/manifest.yml by adding the same deployment_modes structure used by already-enabled metrics templates (e.g., dynamodb at :252-259, elb at :364-371).
   2. Keep scope explicitly to metrics templates (input: aws/metrics) still missing agentless (cloudwatch, ebs, ec2, ecs, natgateway, firewall, s3, s3_storage_lens, usage, vpn, redshift, kinesis, apigateway, emr, kafka).
   3. Update corresponding AWS docs pages in packages/aws/docs/*.md for newly-enabled metric services, matching wording used in already-enabled pages (for example packages/aws/docs/billing.md:45-49, packages/aws/docs/rds.md:34-42).
   4. Add a changelog entry in packages/aws/changelog.yml following the existing convention (Enable agentless deployment for AWS <service> metrics.).
   5. Run package docs build/tests used by the repo for AWS package changes to confirm generated docs and package validation are clean before merge.

   Related Items

   Type	Link	Relevance
   Issue	#19283	Current triage target
   File	packages/aws/manifest.yml:185-203	cloudwatch has metrics input without agentless deployment mode
   File	packages/aws/manifest.yml:270-283	ebs has metrics input without agentless deployment mode
   File	packages/aws/manifest.yml:252-259	dynamodb shows the expected agentless pattern
   File	packages/aws/changelog.yml:42-85	History of prior AWS metrics agentless enablement
   PR	#18584	Example of adding agentless deployment for one AWS metrics template (RDS)
   PR	#18583	DynamoDB metrics agentless enablement precedent
   PR	#18364	ELB metrics agentless enablement precedent
   PR	#18363	Billing metrics agentless enablement precedent

   Note

   🔒 Integrity filter blocked 67 items

   The following items were blocked because they don't meet the GitHub integrity level.

   • #19283 issue_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
   • #19266 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
   • #19191 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
   • #19090 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
   • #19036 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
   • #19037 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
   • #19219 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
   • #19062 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
   • #18552 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
   • #19185 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
   • #18227 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
   • #19283 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
   • #19093 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
   • #19231 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
   • #19094 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
   • #19092 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
   • ... and 51 more items

   To allow these resources, lower min-integrity in your GitHub frontmatter:

   tools:
     github:
       min-integrity: approved  # merged | approved | unapproved | none

   ---

   What is this? | From workflow: Issue Triage

   Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.
3. MichaelKatsoulis commented on Jun 16, 2026

   

   MichaelKatsoulis

   on Jun 16, 2026

   ContributorAuthor

   More actions

   Closing as #19339 was merged
4. MichaelKatsoulis

   closed this as completedon Jun 16, 2026