Over the weekend, I visited one of my favorite grocery stores to pick up one item, my favorite fruit e.g star fruit. Because of the location, the grocery star started to implement parking validation so folks would not abuse their free parking deck for extended periods of time. As I just had a handful of star fruits, I decided to use the self-checkout. This was my first time buying produce via self-checkout.

Leading organizations around the world are adopting cloud-native technologies to build next-generation products because cloud native gives them the agility that they need to stay ahead of their competition. Although cloud native and Kubernetes are very disruptive technologies, there is another technology that is probably the most disruptive technology of our generation, and that is artificial intelligence (AI) and its subset, machine learning (ML).

Up until now notification center policies were managed at the account level. Editing a notification policy required first switching to the desired account and then making changes there. Having to move between multiple accounts could present a bit of a hassle when trying to find the right policy to edit.

In order to manage the impact that every entity has on your IT environment, an accurate Configuration Management Database (CMDB) is essential. This tool provides the visibility you need to quickly execute tasks like daily management, determining how to fix an outage, and planning major initiatives like cloud migrations or application changes. To create and maintain an accurate CMDB, automated dependency and discovery mapping (DDM) is key.

Site reliability engineering (SRE) is a set of principles that incorporates aspects of software engineering into IT operations. It takes tasks that would typically have been done manually by operations teams and gives them to engineers to solve using software and automation. This helps to create a bridge between development and operations teams. The concept of SRE was created by Google back in 2003. Since then, it has been adopted by thousands of organizations all over the world.

The Twelve-Factor methodology is a set of best practices for developing microservices applications. These practices are segregated into twelve different areas of application development. Twelve-factor is the standard architectural pattern to develop SaaS-based modern and scalable cloud applications. It is highly recommended by AWS if you are building containerized microservices. In this article, we will guide you on how to develop applications that will use microservices deployed on containers in AWS.

We are often asked about areas where customers overspend on Amazon Web Services (AWS). NAT gateway costs are high due to misplaced data transfers and are definitely near the top of our list. This article will walk you through five steps you can take to find out which data transfers you’re overspending on and how you can eliminate those excess charges.