Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for AWS Lightsail resource #3869

Open
weibeu opened this issue Apr 29, 2024 · 1 comment · May be fixed by #3919
Open

Add support for AWS Lightsail resource #3869

weibeu opened this issue Apr 29, 2024 · 1 comment · May be fixed by #3919
Assignees
Labels
feature-request New feature request for Prowler. provider/aws Issues/PRs related with the AWS provider severity/informational Cosmetic or nice-to-have.

Comments

@weibeu
Copy link

weibeu commented Apr 29, 2024

New feature motivation

It would be great if Prowler starts supporting AWS Lightsail as this as well is a common service used by several teams.

Solution Proposed

Support AWS Lightsail instance scanning for things like:

  • Open ports
  • Static IPs
  • Snapshots
  • Disk usage

Describe alternatives you've considered

NA

Additional context

No response

@weibeu weibeu added feature-request New feature request for Prowler. status/needs-triage Issue pending triage labels Apr 29, 2024
@sergargar
Copy link
Member

sergargar commented Apr 30, 2024

Hi @weibeu , thanks for the feedback!
We have included in our roadmap to do the following LightSail checks, let us know what you think:

  • lightsail_instance_public

Ensures no LightSail instances are unnecessarily exposed to the internet by having a public IP address and open ports.

  • lightsail_instance_automated_snapshots

Check if instances have automated snapshots enabled

  • lightsail_static_ip_unused

Audits for static IPs that are allocated but unused.

  • lightsail_database_public

Check if the database has the public mode.

@sergargar sergargar self-assigned this Apr 30, 2024
@sergargar sergargar added provider/aws Issues/PRs related with the AWS provider severity/informational Cosmetic or nice-to-have. and removed status/needs-triage Issue pending triage labels Apr 30, 2024
@sergargar sergargar linked a pull request May 6, 2024 that will close this issue
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request New feature request for Prowler. provider/aws Issues/PRs related with the AWS provider severity/informational Cosmetic or nice-to-have.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants