Check ID:
Provider: AWS
Service:
Severity: LOW
Categories:
Resource type:
lightsail_static_ip_unusedProvider: AWS
Service:
lightsailSeverity: LOW
Categories:
resilienceResource type:
OtherWhat this check verifies
Amazon Lightsail static IPs detected as not associated with any instance, indicating reserved but unused addresses. The evaluation focuses on the association state of each static IP to highlight potential leftovers.Risk
Unattached static IPs incur ongoing charges and indicate asset drift. If DNS or apps still reference the address, requests are blackholed, impacting availability. Later attaching the same IP to an unintended host can expose services and data, affecting confidentiality and integrity.Recommendation
Release unused static IPs or attach them to the intended instance. Apply least privilege for IP allocation, enforce tagging and ownership, and run periodic audits with alerts for unattached addresses. If reservation is required, document purpose and set a time limit to prevent drift and cost.Remediation
- CLI
- Terraform
- Native IaC
- Dashboard steps
aws lightsail attach-static-ip —static-ip-name <example_resource_name> —instance-name <example_resource_name>
References
- https://docs.aws.amazon.com/lightsail/latest/userguide/understanding-public-ip-and-private-ip-addresses-in-amazon-lightsail.html
- https://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/Lightsail.html
Where this check fires
This check runs on every scheduled scan against your AWS account. Findings appear at Cloud Security → Findings filterable byCheck ID = lightsail_static_ip_unused. To re-evaluate after a fix, hit Run now on the account’s schedule under Cloud Security → Schedules — the next scan re-checks this control and marks the finding fixed or keeps it persistent.
← Back to AWS checks