Removing Amazon LightSail VMs properly without billing leakage

Removing Amazon LightSail VMs properly without billing leakage

Creating and tearing down a Virtual Private Server on Amazon LightSail involves not only the server but also its related resources like public IP, DNS zones, containers, storages, and databases to avoid additional charges. Users should methodically delete instances, containers, databases, static IP, and DNS zones to prevent unexpected costs and clean up the environment.
getting started with observability

Getting started with observability

This tutorial explains monitoring cloud infrastructure using eG Innovations' SaaS, detailing steps from signing up for a trial to monitoring AWS cloud instances. The process, utilizing a remote agent, covers discovering cloud resources, installing agents for converged monitoring (Metrics, Events, Logs, Traces), and receiving alerts for anomalies. Observability without writing scripts through Metrics-Events-Logs-Traces (MELT) is emphasized, with the promise to later discuss different monitoring methods.
5-steps-to-monitor-Amazon-LightSail-VM-with-AWS-CloudWatch

5 Steps to Monitor Lightsail VM using Amazon Cloud Watch

Amazon Cloud Watch and Azure Monitor are native cloud monitoring tools that can be bundled with cloud subscriptions, sparking debate over their sufficiency for full observability and SRE MELT goals. The post details a five-step process for monitoring AWS Lightsail VMs using Amazon Cloud Watch, covering installation and configuration of the AWS CLI and CloudWatch agent. This process is vital as Lightsail VMs do not natively include AWS CloudWatch agents. Additional metrics, such as memory and network consumption, can also be monitored, though troubleshooting may be necessary for some metrics to appear.