fix(sdk): update Trend Micro URLs in AWS metadata files

[HugoPBrito]

Context

Trend Micro CloudOne Conformity will reach End-of-Life (EOL) in July 2026. The platform is being replaced by Trend Micro Vision One Cloud Risk Management. All CloudOne Conformity URLs in AWS check metadata files are being updated to point to the new Vision One platform to ensure users have access to current security guidance.

Description

This PR updates 221 AWS metadata files to replace deprecated Trend Micro CloudOne Conformity URLs with the new Trend Micro Vision One Cloud Risk Management URLs.

Key Changes:

• URL Migration: CloudOne Conformity → Vision One Cloud Risk Management
  • Old: https://www.trendmicro.com/cloudoneconformity/knowledge-base/aws/...
  • New: https://www.trendmicro.com/trendaivisiononecloudriskmanagement/knowledge-base/aws/...
• URL Verification: All 221 new Vision One URLs verified to return HTTP 200 OK
• Comprehensive Coverage: Updated metadata for 53 AWS services (accessanalyzer, account, acm, apigateway, autoscaling, awslambda, backup, bedrock, cloudformation, cloudfront, cloudtrail, cloudwatch, dlm, dms, documentdb, dynamodb, ec2, ecr, ecs, eks, elasticache, elasticbeanstalk, elb, elbv2, emr, eventbridge, firehose, glue, guardduty, iam, inspector2, kafka, kinesis, kms, mq, neptune, networkfirewall, opensearch, rds, redshift, route53, s3, sagemaker, sns, sqs, storagegateway, trustedadvisor, vpc, wafv2, wellarchitected, workspaces)

Why This Matters:

• Ensures users can access up-to-date security guidance from Trend Micro's active platform
• Prevents broken links when CloudOne Conformity is sunset in July 2026
• Maintains alignment with Trend Micro's current cloud security best practices

Related Work:

• Similar updates completed for GCP services: chore(gcp): enhance metadata for dns service #9643 (DNS), chore(gcp): enhance metadata for gcr service #9644 (GCR), chore(gcp): enhance metadata for gke service #9645 (GKE), chore(gcp): enhance metadata for iam service #9646 (IAM), chore(gcp): enhance metadata for kms service #9647 (KMS), chore(gcp): enhance metadata for logging service #9648 (Logging)

Steps to review

1. Verify URL pattern replacement:

   git diff master...HEAD | grep -E "(cloudoneconformity|trendaivisiononecloudriskmanagement)"

   • Confirm all cloudoneconformity → trendaivisiononecloudriskmanagement replacements

2. Spot-check URL validity (sample 5-10 random files):

   # Example: Check KMS metadata
   cat prowler/providers/aws/services/kms/kms_key_not_publicly_accessible/kms_key_not_publicly_accessible.metadata.json | grep RelatedUrl
   # Verify URL returns 200 OK
   curl -I https://www.trendmicro.com/trendaivisiononecloudriskmanagement/knowledge-base/aws/KMS/kms-key-not-publicly-accessible.html

3. Validate JSON integrity:

   # Ensure all metadata files are valid JSON
   find prowler/providers/aws/services/ -name "*.metadata.json" -exec python3 -m json.tool {} \; > /dev/null

4. Check service coverage - Verify 53 AWS services updated:

   git diff --name-only master...HEAD | cut -d'/' -f5 | sort -u | wc -l

Checklist

Community Checklist

• This feature/issue is listed in here or roadmap.prowler.com
• Is it assigned to me, if not, request it via the issue/feature in here or Prowler Community Slack

• Are there new checks included in this PR? No
  • If so, do we need to update permissions for the provider? N/A
• Review if the code is being covered by tests. (No code changes, only metadata URLs)
• Review if code is being documented following https://github.com/google/styleguide/blob/gh-pages/pyguide.md#38-comments-and-docstrings (No code changes)
• Review if backport is needed. (No - metadata update only)
• Review if is needed to change the Readme.md (No)
• Ensure new entries are added to CHANGELOG.md, if applicable. (Pending - will add)

SDK/CLI

• Are there new checks included in this PR? No
  • If so, do we need to update permissions for the provider? N/A

UI (if applicable)

• N/A - SDK-only changes

API (if applicable)

• N/A - SDK-only changes

License

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[github-actions]

✅ All necessary CHANGELOG.md files have been updated.

[github-actions]

✅ Conflict Markers Resolved

All conflict markers have been successfully resolved in this pull request.

[github-actions]

🔒 Container Security Scan

Image: prowler:b02bbb3
Last scan: 2026-02-13 16:04:00 UTC

📊 Vulnerability Summary

Severity	Count
🔴 Critical	4
Total	4

4 package(s) affected

⚠️ Action Required

Critical severity vulnerabilities detected. These should be addressed before merging:

• Review the detailed scan results
• Update affected packages to patched versions
• Consider using a different base image if updates are unavailable

---

📋 Resources:

• Download full report (see artifacts)
• View in Security tab
• Scanned with Trivy

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 77.42%. Comparing base (75ee07c) to head (b082f9b).

❗ There is a different number of reports uploaded between BASE (75ee07c) and HEAD (b082f9b). Click for more details.

HEAD has 2 uploads less than BASE

Flag	BASE (75ee07c)	HEAD (b082f9b)
prowler-py3.12-gcp	1	0
prowler-py3.9-gcp	1	0

Additional details and impacted files

@@             Coverage Diff             @@
##           master   #10068       +/-   ##
===========================================
- Coverage   92.85%   77.42%   -15.44%     
===========================================
  Files         137      835      +698     
  Lines        3387    23633    +20246     
===========================================
+ Hits         3145    18297    +15152     
- Misses        242     5336     +5094     

Flag	Coverage Δ
prowler-py3.10-aws	77.37% <ø> (?)
prowler-py3.11-aws	77.37% <ø> (?)
prowler-py3.12-aws	77.36% <ø> (?)
prowler-py3.12-gcp	?
prowler-py3.9-aws	77.38% <ø> (?)
prowler-py3.9-gcp	?

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
prowler	77.42% <ø> (-15.44%)	⬇️
api	∅ <ø> (∅)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.