Amazon Lightsail Instance
Does ZopNight manage Amazon Lightsail Instance?
Lightsail bundles compute, storage, and networking into one flat monthly price per instance, billed for as long as the instance exists, stopped or running. ZopNight discovers instances on its 6-hour cycle, attributes bundle cost from Cost Explorer or CUR 2.0, and can stop and start them on schedule to shrink exposure; deleting the instance is what ends the charge.
Rules that fire on Amazon Lightsail Instance
No active rule family targets Amazon Lightsail Instance today. Rules that used to are retired, and retired rules publish no pages and fire no findings. Scheduling and permissions coverage are unaffected.
At a glance
| Field | Value |
|---|---|
| Scheduling notes | instance stopped and started via the Lightsail API on schedule. |
Amazon Lightsail offers simplified virtual private servers with bundled compute, storage, and networking at a flat monthly price. Because the bundle price accrues for as long as the instance exists, stopping a server does not lower the bill; deleting it does.
One price, everything included
Lightsail inverts the usual AWS pricing model: instead of separate meters for compute, EBS, and data transfer, each instance carries a single bundle price covering a fixed allocation of vCPU, memory, SSD storage, and a transfer allowance. Predictability is the product. The flip side is that the bundle accrues as a unit. No per-component saving comes from using less storage or less transfer, and the only meaningful cost levers are whether the instance exists and which bundle size it runs at. Databases, container services, and load balancers in Lightsail follow the same flat-bundle logic with their own price tiers.
Simple servers, simple schedules
ZopNight discovers Lightsail instances automatically on the 6-hour cycle, with per-resource cost attributed from Cost Explorer or CUR 2.0. Instances are schedulable: the Lightsail API stops them on the configured schedule and starts them again for working hours. That shrinks the hours a server is reachable rather than the bill, which still suits the workloads Lightsail attracts: dev servers, internal tools, demo boxes, WordPress staging. No recommendation rule covers Lightsail, so the instances nobody needs at all are found by review and deleted.
Where flat pricing hides waste
Lightsail’s fixed price removes the cost feedback that nags people about idle EC2: the number never spikes, so the forgotten instance never draws attention. Typical leaks are demo servers from concluded sales cycles, tutorial instances from someone’s learning weekend, and side-project boxes provisioned because the entry bundles cost less than lunch. Each one is trivial; together they are a steady drip. Oversized bundles are the other form: a static site on a bundle sized for a database.
The Lightsail console view
Lightsail lives in its own console, deliberately apart from EC2, listing instances with bundle size and state per region. The instance metrics tab shows CPU and network history, enough to sort the genuinely used from the merely running before applying a schedule or a deletion.