Operations | Monitoring | ITSM | DevOps | Cloud

Here on the CircleCI Insights team we don’t just develop stuff for CircleCI users, we are CircleCI users. Really, there’s no better way to get to know your product than to use it, and the Insights team is no exception. A few months ago, we realized that our pipeline configuration for the Insights UI left much to be desired.

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.

Developers strive to produce efficient code. Many times, developers will add code to their repositories and test it to make sure it works, but they are forgetting one very important step: benchmarking! Benchmarking allows developers to see the performance impact on their code output. If properly integrated into a CI/CD pipeline, it could prevent catastrophic drops in performance before any code is shipped/deployed at all.

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.

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.