Use AWS Config the Right Way for Successful Compliance
It’s well-known that AWS Config is a powerful service for monitoring all changes across your resources. As AWS Config has constantly evolved and improved over the years, it has transformed into a true powerhouse for monitoring your deployment’s compliance. Monitoring for compliance — whether for HIPAA, CIS, internal auditors, etc. — is a detailed and complicated process, and it’s of utmost importance to provide a clear history of all actions so that auditors can easily assess and approve your organization. With that in mind, let’s check out the following three best practices to use AWS Config for Compliance.
Joe Nemer posted a great blog about Compliance best practices on AWS config. Read his blog article here for more info and details.
The “big three” public cloud providers are turning their sights to legacy workloads. It will be interesting to see how customers adopt and deploy VMware on AWS, Azure Stack and, now, Google Nested Virtualization.
One knock on public clouds from Google, Amazon, and even Microsoft is that they are terrific for brand-new software built to take advantage of their resources, but not so great for existing, older business software developed and deployed before the cloud era kicked off 10 years ago.
The cloud players are working to address that issue. Many companies don’t necessarily want to rebuild applications that run just fine so they can move to someone else’s cloud data centers.
Always looking for good info and tools for my daily work, I happened to find a website where clouds were compared. I found it so interesting that I found it useful and also want to share it through my blog. The maker have certainly done a good job. Thanks to Jess Panni for sharing this.