Watch the AWS resources your product runs on — instances, load balancers, databases — and get one clear alert when something degrades, instead of digging through CloudWatch.
Running on AWS does not mean AWS watches your application for you. CloudWatch collects plenty of numbers, but turning them into a clear answer — is production healthy right now? — takes alarms, dashboards and a person who knows where everything is.
AWS Infrastructure Monitoring will read the state of your resources and combine it with checks from outside AWS, so an alert says what is wrong and whether your users can feel it.
The plan for the first release. Every check will be stored in a full log, like all Upzilla monitors.
State, status checks and resource use.
Healthy and unhealthy targets, errors and latency.
RDS availability, CPU, storage and connections.
The public endpoints, checked from locations outside AWS.
Uptime, HTTP and TCP monitors can already check every public endpoint you run on AWS.
Set up like every other Upzilla monitor, in a few minutes.
Read-only access to the account and regions you choose.
Production only, or everything that matters.
In plain words, in the channel your team uses.
One view of production without living in the console.
Sensible alerts without building CloudWatch alarms.
Monitor clients' AWS setups side by side.
Spot idle and overloaded resources.
The same alert channels as every Upzilla monitor, as many as you like.
We are building it now, along with Google Cloud and Azure monitoring and many other new checks arriving before the new year. Create a free account to hear first.
Read-only access to the AWS account. It will not be able to change anything.
Uptime, HTTP, TCP and SSL monitors can already check every public endpoint and server you run on AWS, from outside AWS.
No — it uses the data AWS already has and turns it into clear alerts, together with checks from the outside.
Start with 10 free monitors today — we will tell you the moment this one is ready.