Operations | Monitoring | ITSM | DevOps | Cloud

In 2020, we started an internal project to price our data center systems to understand what they might cost to run in the AWS or Azure cloud environments. We initially used some of the online pricing tools available from these vendors, but they were slow and difficult to use in bulk. You can find the public cloud tools here: AWS and Azure. We were forced to add individual systems one at a time and pick options for each because of the nature of these tools.

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 in my opinion one of the most annoying features/tasks and recommend some Best practices, Tips, and Tricks to minimize it: working with expressions.

When your organization uses the cutting edge of technology to function, you may feel like it takes all your time and energy to stay on top of emerging trends. How are you supposed to anticipate what the future will hold when you have to balance those considerations with how to best provide for your customers’ needs today? It’s okay if you don’t have your finger on the pulse 100 percent of the time.

This is the second part of our EKS with Terraform series. In Part 1, we talked about Infrastructure as Code and its benefits. We also mentioned the tools we will be using. This time we will actually start using Terraform to create a VPC and EC2 instance.

For SaaS companies, the cloud plays a significant role in product creation and delivery. As one of the top drivers of COGS, cloud costs have a major impact on key financial metrics and can dramatically impact revenue and valuation. However, that creates a scenario ripe for conflict: Engineers make important decisions about features and functionality without clear insight into how those decisions will impact spending—and finance continuously gets surprised by seemingly exorbitant cloud bills.

Introducing OpenID Connect identity tokens in CircleCI jobs! This token enables your CircleCI jobs to authenticate with cloud providers that support OpenID Connect like AWS, Google Cloud Platform, and Vault. In this blog post, we’ll introduce you to OpenID Connect, explain its usefulness in a CI/CD system, and show how it can be used to authenticate with AWS, letting your CircleCI job securely interact with your AWS account, without any static credentials.

Recently we had an interesting use case from our customer for which Serverless360 mapped a perfect solution. We resolved the issue with the new Log Analytics and Application Insights capabilities from Serverless360. This blog will help you better understand the feature set with a real-time use case.