As your cloud footprint grows, so does your deviation from best practices. Governance is the glue that keeps all your multiple accounts (and resources therein) from flying apart and becoming shadow I.T. centers in the cloud.

Some questions faced by larger cloud footprints include (this list is AWS specific – although most of it works for Azure as well)

  1. Multiple Account Management – Governance around Automated AWS , azure Account Provisioning
  2. Cost Enforcement Governance – Actual Spend vs. Projection, Automation and Metering Governance on AWS, azure
  3. Automation of Compliance on AWS (Security, Data) — Security – Dynamic Policies — Data – PCI, PII, HIPAA
  4. AWS Service Catalog (azure dev test labs) Templated Approach vs. Manual, Flexible provisioning approach
  5. Tools for monitoring and enforcing compliance on AWS / azure – Trusted Advisor, CloudCheckr, CloudHealth
  6. List of Best Practices , AWS Native cost saving tips (EBS, Spot Instances, Volume discounts, RIs…)

Anuj holds professional certifications in Google Cloud, AWS as well as certifications in Docker and App Performance Tools such as New Relic. He specializes in Cloud Security, Data Encryption and Container Technologies.

Initial Consultation

Anuj Varma – who has written posts on Anuj Varma, Hands-On Technology Architect, Clean Air Activist.

 Twitter Linkedin