Skip to content

Conversation

@kagahd
Copy link
Contributor

@kagahd kagahd commented Jan 22, 2026

Context

This feature request offers a new AWS check rds_instance_extended_support.
It checks whether Amazon RDS DB instances are enrolled in Amazon RDS Extended Support. If the instance reports EngineLifecycleSupport as open-source-rds-extended-support, it is enrolled and the check fails. Otherwise, the check passes.

Description

DB instances enrolled in RDS Extended Support can incur additional charges after the end of standard support for the running database major version. Remaining on older major versions can also delay necessary upgrades, increasing operational and security risk.
The check is covered by unit-tests.

Checklist

SDK/CLI

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

UI

  • All issue/task requirements work as expected on the UI
  • Screenshots/Video of the functionality flow (if applicable) - Mobile (X < 640px)
  • Screenshots/Video of the functionality flow (if applicable) - Table (640px > X < 1024px)
  • Screenshots/Video of the functionality flow (if applicable) - Desktop (X > 1024px)
  • Ensure new entries are added to CHANGELOG.md, if applicable.

API

  • All issue/task requirements work as expected on the API
  • Endpoint response output (if applicable)
  • EXPLAIN ANALYZE output for new/modified queries or indexes (if applicable)
  • Performance test results (if applicable)
  • Any other relevant evidence of the implementation (if applicable)
  • Verify if API specs need to be regenerated.
  • Check if version updates are required (e.g., specs, Poetry, etc.).
  • Ensure new entries are added to CHANGELOG.md, if applicable.

License

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

@kagahd kagahd requested review from a team as code owners January 22, 2026 15:39
@github-actions github-actions bot added provider/aws Issues/PRs related with the AWS provider metadata-review community Opened by the Community labels Jan 22, 2026
@github-actions
Copy link
Contributor

github-actions bot commented Jan 22, 2026

Conflict Markers Resolved

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

@codecov
Copy link

codecov bot commented Jan 22, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 8.67%. Comparing base (91e3c01) to head (4259a32).

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #9865       +/-   ##
==========================================
- Coverage   92.07%   8.67%   -83.40%     
==========================================
  Files         180     832      +652     
  Lines       24833   23496     -1337     
==========================================
- Hits        22864    2039    -20825     
- Misses       1969   21457    +19488     
Flag Coverage Δ
api ?
prowler-py3.10-aws 8.60% <100.00%> (?)
prowler-py3.11-aws 8.60% <100.00%> (?)
prowler-py3.12-aws 8.67% <100.00%> (?)
prowler-py3.9-aws 8.63% <100.00%> (?)

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

Components Coverage Δ
prowler 8.67% <100.00%> (∅)
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.

@kagahd kagahd force-pushed the rds_instance_extended_support branch from fd57551 to c66fc61 Compare January 22, 2026 17:55
@kagahd kagahd requested a review from a team as a code owner January 22, 2026 18:03
@kagahd
Copy link
Contributor Author

kagahd commented Jan 22, 2026

codecov/patch is green (“all modified lines are covered”), so this PR itself does not reduce test coverage.

The large drop in codecov/project (92% → ~9%, +600 files) strongly suggests a Codecov upload/configuration issue, not missing tests in this PR.

In particular, the API workflow generates coverage.xml in the repo root, but the Codecov upload does not explicitly reference the file. This can result in incomplete or missing project coverage data.

I believe the project coverage regression should be fixed in the CI/Codecov setup rather than in this PR.

Copy link
Member

@danibarranqueroo danibarranqueroo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this great contribution! Please review this requested changes.

{
"Provider": "aws",
"CheckID": "rds_instance_extended_support",
"CheckTitle": "RDS instances are not enrolled in RDS Extended Support",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"CheckTitle": "RDS instances are not enrolled in RDS Extended Support",
"CheckTitle": "RDS instance is not enrolled in RDS Extended Support",

"Severity": "medium",
"ResourceType": "AwsRdsDbInstance",
"ResourceGroup": "database",
"Description": "Checks whether Amazon RDS DB instances are enrolled in Amazon RDS Extended Support. If the instance reports `EngineLifecycleSupport` as `open-source-rds-extended-support`, it is enrolled and the check fails. Otherwise, the check passes.",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"Description": "Checks whether Amazon RDS DB instances are enrolled in Amazon RDS Extended Support. If the instance reports `EngineLifecycleSupport` as `open-source-rds-extended-support`, it is enrolled and the check fails. Otherwise, the check passes.",
"Description": "**RDS DB instances** are evaluated for enrollment in Amazon RDS Extended Support. The check fails if `EngineLifecycleSupportis` set to `open-source-rds-extended-support`, indicating the instance will incur additional charges after standard support ends.",

"ResourceGroup": "database",
"Description": "Checks whether Amazon RDS DB instances are enrolled in Amazon RDS Extended Support. If the instance reports `EngineLifecycleSupport` as `open-source-rds-extended-support`, it is enrolled and the check fails. Otherwise, the check passes.",
"Risk": "DB instances enrolled in RDS Extended Support can incur additional charges after the end of standard support for the running database major version. Remaining on older major versions can also delay necessary upgrades, increasing operational and security risk.",
"RelatedUrl": "https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/extended-support.html",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"RelatedUrl": "https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/extended-support.html",
"RelatedUrl": "",

},
"Recommendation": {
"Text": "Upgrade enrolled DB instances to an engine version covered under standard support to stop Extended Support charges. For new DB instances and restores created via automation, explicitly set the engine lifecycle support option to avoid unintended enrollment in RDS Extended Support when that is your policy.",
"Url": "https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/extended-support-charges.html"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"Url": "https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/extended-support-charges.html"
"Url": "https://hub.prowler.com/check/rds_instance_extended_support"

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please, move it to the current UNRELEASED version and follow the same style as other new checks in the Added section

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please, remove this changes. Don't worry about codecov since it's not a blocker for merging PRs, I'll talk with the team about this to see if there is a problem with the current settings.

@danibarranqueroo
Copy link
Member

I've tested the check and it works as expected 🚀

Captura de pantalla 2026-01-26 a las 13 48 26

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

community Opened by the Community metadata-review provider/aws Issues/PRs related with the AWS provider

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants