If you’ve been reading my blogs for the past two years, you know that the automotive industry is probably the most innovative one today. As a matter of fact, some of the biggest company valuations revolve around electric vehicles (EVs), autonomous driving (AD) and artificial intelligence (AI). As with any revolution, this one comes with its set of challenges.

Regular patching is essential for maintaining a secure environment, but there is no one-size fits all approach for keeping your Linux estate safe. So how do you balance the frequency of updates with operational stability? There are strategies for enabling security patching automations in a compliant and safe way, for even the most restrictive and regulated environments.

Earlier this year at Mobile World Congress (MWC) 2024 in Barcelona, Canonical announced the availability of Real-time Ubuntu on Amazon Elastic Kubernetes Services Anywhere (EKS Anywhere). With this technology enablement, a telecom operator can confidently run its Open Radio Access Network (RAN) software workloads on Amazon EKS Anywhere, thanks to the necessary support for ultra low-latency data processing with high reliability in Real-time Ubuntu.

The automotive industry is a vast and complex sector that includes all companies and activities involved in manufacturing vehicles or their components (such as engines, electronic control units (ECUs) and bodies). However, this sector is growing even more, as it experiences a technological revolution driven by new technologies like artificial intelligence, machine learning, and big data analytics.

On 1 July 2024 we released a fix for the high-impact CVE-2024-6387 vulnerability, nicknamed regreSSHion, as part of the coordinated release date (CRD). Discovered and responsibly disclosed by Qualys, the unauthenticated, network-exploitable remote code execution flaw affects the OpenSSH server daemon (sshd) starting with version 8.5p1 and before 9.8p1.

Canonical’s Managed Solutions team is proud to announce Firefighting Support, a new service for organisations that manage their infrastructure by themselves but need experts on call for troubleshooting needs. Firefighting Support provides managed-service-level support to customers who graduate away from fully managed services or are under security regulations too stringent to grant environment access to a third-party.

This article explains how to show cron jobs for all users and the current user on a Linux system. It covers ways to list cron jobs as a root user, view system-wide cron jobs, and check user-specific cron tasks. The article also explains how to read cron job formats and gives examples of common cron job setups.

In the first part of this blog journey (I’d call it a post, but it’s actually two posts) we explored what operational excellence looks like in public cloud deployments. And while I do not want to spoil it for you, the main takeaway was that it is not easy and can become resource-intensive. With this in mind, you might should be wondering what you can do to achieve excellence without focusing all your resources on operations.

You might be tempted to think that running an app on a public cloud means you don’t need to maintain it. While that would be wonderful, it would require help from the public cloud providers and app developers themselves, and possibly a range of mythological creatures with magic powers. This is because any app, regardless of the infrastructure on which it runs or its output, requires maintenance in order to yield accurate and reliable outputs.