Knowing only how much you spent on your AWS bill each month isn’t enough to provide the cost visibility you need to make cost-aware engineering and business decisions. It's why AWS introduced tags. Tags enable AWS users to label their resources to track cost and usage in the vast AWS infrastructure. The goal of tagging is to help you understand who, what, and why your cloud spend is changing.

Life before containerization was a sore spot for developers. The satisfaction of writing code was constantly overshadowed by the frustration of attempting to force code into production. For many, deployments meant hours of reconfiguring libraries and dependencies for each environment. It was a tedious process prone to error, and it led to a lot of rework. Today, developers can deploy code using new technology such as cloud computing, containers, and container orchestration.

In my previous blog posts, I talked about some of the most essential best practices you should have while working with the Azure Logic App: And some tips and tricks: Today I’m going to speak about another critical Best practice, Tips, and Tricks: implementing Error handling inside Logic Apps.

The cloud offers unparalleled flexibility. However, that flexibility comes at a cost. The amount of moving pieces increases. The environment becomes more heterogeneous. So, if you want to stay on top of things, you need a more comprehensive view of your cloud infrastructure. After all, you don’t want your customers to realize that something has gone awry before your people do. In this post, I’m going to talk about cloud monitoring.

Rightsizing is about finding the optimal cloud configuration options to ensure that you get the performance you need—within any given constraints you are operating under—at the lowest possible cost. This is a simple proposition, but deceptively so. For one thing, business requirements are constantly changing, meaning that your workloads must adapt to support them, which in turn changes their operating parameters.

We’ve got some outstanding news to share in the arena of security partnerships: Logz.io® Cloud-based SIEM has officially achieved Amazon Web Services (AWS) Security Competency! This designation within the Logging, Monitoring, SIEM, Threat Detection, and Analytics category further demonstrates Logz.io’s proven commitment to delivering best-in-class security.

Welcome to the second post in a series of “How to Scale your AWS Infrastructure”. In the first post, we talked about horizontal scaling, autoscaling, CI/CD, infrastructure automation, containerization, etc. In this post, we will continue the discussion around databases, loose coupling, caching, CDN, etc. Let’s start the discussion with database scaling.

As we push more data to the cloud, avoidable mistakes are hampering migration. The biggest culprit: messy data with inadequate security and integration.Data transfers seem to be the easiest part of cloud migration. After all, migrating applications is the biggest pain in the neck. Data replication and migration should be simple, something that’s done during the last step of the application and data migration process. Right?

If you have worked in any part of the application delivery lifecycle long enough, there’s a very good chance you have directly used or been a consumer of Nagios. For a period of time in the early 2000s, it was the go-to solution for basic server monitoring and alerts. Fast forward 20 years and you might be surprised how many organizations still rely on Nagios for mission critical workloads — although not without a fair amount of duct tape and super glue challenges.