As an AWS partner since 2010, we’ve seen a number of products rolled out over the years. These have helped AWS users with their cloud environments in countless ways, and it really is a testament to Amazon’s willingness to listen and adapt to its customers needs.

Many businesses are choosing to migrate, or natively build their infrastructure in the cloud; doing so helps them realize a myriad of benefits. Among these benefits is the ability to lower costs by “right-sizing” infrastructure

In this blog post, we’d like to share some details around one of our most recent – and largest - big-data projects we’ve worked on; a project with our client, Milliman, to build a machine-learning platform on Amazon Web Services.

We’d all like to believe that everyone accessing content will use it appropriately. Unfortunately, we can’t always assume the best, and being proactive in dealing with bad actors will reduce security threats to your infrastructure and apps.

A look at the CIS AWS Foundations Benchmark, the result of a partnership between the CIS and Amazon Web Services. These best practices, which are accepted throughout the industry, give concise, step-by-step instructions for AWS users.

It was a little tough to scrape together all of the details from the various sources I could find online, so I thought I’d bring together the end-to-end process for how to set up SSH and Ansible for using bastion hosts to access instances that don’t have a public address.

Experts estimate there are more than 14,000 attacks on networks and systems every day, with new vulnerabilities in critical software increasing by 50% annually. These are alarming stats for any IT organization, but especially those in sensitive industries like banking.