Measuring your entire server architecture involves many things from software versions provided by the package maintainer (Ubuntu/Debian, RHEL/CentOS, custom, etc), memory capacity of your machines, disk allocation, and so forth.
Changes to this server architecture -- anything and everything -- should be managed in a controlled environment.
AWS Config provides insight into this, notifying you of when any changes occur.
They provide you with a constant stream of changes occurring, like getting Tweets whenever anything changes.
Amazon already has AWS CloudWatch, this takes it a step further than monitoring performance, resource utilization, and operational health. It delves into what happens before performance thresholds are breached and operational health is diminished.
Comments
Measuring your entire server architecture involves many things from software versions provided by the package maintainer (Ubuntu/Debian, RHEL/CentOS, custom, etc), memory capacity of your machines, disk allocation, and so forth.
Changes to this server architecture -- anything and everything -- should be managed in a controlled environment.
AWS Config provides insight into this, notifying you of when any changes occur.
They provide you with a constant stream of changes occurring, like getting Tweets whenever anything changes.
Amazon already has AWS CloudWatch, this takes it a step further than monitoring performance, resource utilization, and operational health. It delves into what happens before performance thresholds are breached and operational health is diminished.
It's an auditing tool, basically.