As networks expand across on-premises and cloud environments, many organizations find themselves struggling with scattered, unstructured networks. Often, networks grow in silos, with subnets being created independently in AWS, Azure, and other environments over time, leading to a messy and hard-to-manage structure. This is especially true for enterprises undergoing mergers and acquisitions, where integrating entirely separate network systems can quickly turn into an administrative headache.

Platform.sh teams are always striving to ensure a safe space for all developers within our product. And this consistent diligence led to the Platform.sh Engineering team discovering a security vulnerability in the golang.org/x/crypto/ssh package on 5 September 2024. Upon investigating an unexpected Panic: runtime error: invalid memory address or nil pointer dereference message in our edge proxy, the engineers discovered a misimplementation of the PublicKeyCallback function.

If you manage applications running on cloud platforms, you likely depend on multiple cloud vendors and services. These could be infrastructure providers like AWS, GCP or Azure. A vulnerability in any of these services could potentially impact your applications and your users. A cloud platform has many moving parts, many of which are dependent on other third-party providers.

With the nearly unmatched reliability and scalability offered by the 12-factor application design pattern, microservice-based designs have become a fundamental architectural pattern for modern applications. A whole industry of cloud providers has sprung up to offer management of the sophisticated middleware and infrastructure services that make this possible. Amazon Web Services (AWS) is among the largest of them.

AWS Elastic Container Service for Kubernetes (EKS) is a managed service ideal for large clusters of nodes running heavy and variable workloads. Because of how account permissions work in AWS, EKS's architecture is unusual and creates slight differences in your monitoring strategy. Overall, it's still the same Kubernetes you know and love.

We all know that testing new ideas on physical IT infrastructure requires a massive upfront cost. That's why businesses adopt cloud infrastructure setups. These setups offer on-demand resources, which allow you to start new projects and pay for only what you use. This eliminates the need for expensive hardware and maintenance, enabling flexibility that organizations require.

At Uptime.com, we’re committed to helping you monitor and manage the uptime and reliability of your websites and critical infrastructure. Based on your feedback, we’ve enhanced Cloud Status to deliver even more powerful insights into third-party dependencies and improve your experience. Here’s what’s new and what’s coming next!