When you are monitoring your AWS infrastructure for security alerts, not all security signals can be remediated automatically. Large or complex environments can generate multiple security flags (repeatedly) that need to be manually investigated in detail.  This requires access to sometimes complex metadata to thoroughly investigate which may place a strain on your in-house security skills or may even require you to find the budget for a dedicated security expert.

Security is possibly the most important consideration for any organization storing data or hosting applications on public cloud infrastructure.

When you are responsible for the delivery and maintenance of critical or complex applications built on cloud infrastructure, the chances are you are relying on multiple in house engineers or teams of engineers, devops and external consultants to keep your network and applications operating at peak performance for your end users.

When moving your data and applications to AWS or developing a solution from scratch, you are most likely going to be faced with the challenge of selecting the most appropriate of the multitude of database options offered by AWS.

No one needs network documentation, until they do. 

The best and most perfect cloud architecture is next to useless if no one in your organisation understands it. What maybe even worse is if everyone misunderstands it, which is why we believe accurate documentation is an essential step in network architecture design and implementation.

We've put together what we believe is the most comprehensive glossary of cloud computing terminology available. 

Base Image source: AWS Marketplace https://aws.amazon.com/marketplace/solutions/devops#