Operations | Monitoring | ITSM | DevOps | Cloud

Since its emergence in the mid-2000s, the cloud computing market has evolved significantly. The benefits of reliability, scalability, and reduced set-up costs have created a demand to fuel an ever-growing range of “as-a-service” offerings, resulting in an option to suit most requirements. But despite the advantages, the question of cloud or on-premise remains valid.

It is always helpful to know which version you are running of some software, even more so when running development versions. So it’s good if software is able to tell you its version, for example by calling it with --version. For release versions, maintaining this information by hand is feasible, but in order for development versions to show exact revision information, you need some automation, otherwise updating it will be forgotten, leaving you with wrong information.

AWS Cost Explorer is one of the core pillars of AWS cloud financial management. It helps collect resource consumption data and associated cost information across multiple AWS services. Cost Explorer then helps visualize all of this data in one dashboard to ease cost management. You can then analyze, understand, and share cloud cost data with various parties. Cost Explorer is also ideal for companies that have simple cloud billing — and it's free with an AWS subscription.

Today at swampUP, our annual DevOps conference, JFrog CTO Yoav Landman unveiled the next step toward making the Liquid Software vision of continuous, secure updates a truly universal reality. We’ve introduced JFrog Connect, a new solution designed to help developers update, manage, monitor, and secure remote Linux & Internet of Things (IoT) devices at scale.

Canonical’s UA and Pro customers can now fully benefit from their subscriptions directly in containerised environments and pipelines. The new UA client release (27.7+) makes it easier to enable FIPS mode in Ubuntu containers. It also automatically signs up CI/CD builds for 10-year security updates to never worry about production container images getting timely patches for high and critical CVEs.

At a going away party from a job I was leaving a few years back, my VP of engineering told a story I didn’t even remember but that I know subconsciously shaped how I viewed my role on that team: Toward the end of my very first day at the company, there was some internal system issue, and with pretty much zero context, I pulled out my laptop, figured out what was going on, and helped fix the issue.

Cloud 66 offers a range of deployment options for Rails applications, each offering different benefits and trade-offs.

I work on the Solutions Architects team here at Puppet. We are sometimes the first line of defense in solving some of our customers' most challenging or unique problems, and every so often, we see trends in problems that we'd previously considered to be edge cases. For example, cCustomers often ask us two questions: How can we connect external configuration data to Puppet? How can we speed up changing their own configuration for service owners without onboarding them to Git approval processes?