I’ve been writing about continuous cloud optimization for a while now, and recently, I’ve spoken with several organizations to understand any challenges they’re currently facing in their automation journey. Their insights would help us understand how we can improve our technology to better support them. I discovered two fundamental themes behind their challenges.

Just like countless other business functions, cloud delivery has now shifted entirely to remote working for now and perhaps longer term. Canonical has been a remote-first company for some time, so we thought we’d take this opportunity to share some of the best practices we’ve learned along the way. Communication Effective communication between customers, engineers, and project managers is the most critical element of successful cloud delivery.

While the secret of change is to focus all your energy not on fighting the old, but on building the new, adaptability is about the powerful difference between adapting to cope and adapting to win. Enterprises that overlook modernization are sure to fail in fulfilling critical compliance and security problems thus, endangering both, their businesses and customers.

This is a hands-on course on how to deploy a fully Serverless web app using the AWS CDK. You can use the resources declared in this demo application as a starting point to mix and adapt to your own architectures later, which should save you quite some time.

A while back I talked about how big companies have started using serverless in production and how this is a clear sign that we will see more implementation of the serverless infrastructure in the near future. I’d like to take some time today and talk about one of the companies that are using serverless in production: Coca-cola.

Many of the organizations use AWS as their cloud infrastructure, and in general they have multiple AWS accounts for production, staging, and development. Inevitably, this would result in losing track of various experimental AWS resources instantiated by your developers. Eventually, you will be paying AWS bills for resources which could have been identified and deleted in time. So, how should you go about identifying and deleting such unnecessary resources? aws-nuke to the rescue.

A video chat with the developers who bring right-sized cloud costing information in real-time. It all started with a casual conversation about the cloud and infrastructure monitoring among the team at Galileo and our parent company, The ATS Group. From there, it quickly evolved into a discussion on how we can alleviate a source of frustration for many of our customers.