Every Lambda function comes with 512MB of ephemeral storage in the shape of a /tmp directory. This storage space can be reused across multiple invocations for the same instance of a Lambda function. Each instance of a function has its own /tmp directory and data is not shared amongst different instances of a function.

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.

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.

Welcome once again to another Logic App Best practices, Tips, and Tricks. 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 that is often overlooked: learning from failures.

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.

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.

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.

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.

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.