Operations | Monitoring | ITSM | DevOps | Cloud

Adopting AWS as your cloud infrastructure seems to be a common choice for most growing companies, but it is not as easy as it looks. Choosing the right services, configuration, and management of these services needs skills and experience. At Qovery, we've heard hundreds of stories about the mistakes made by startups on AWS, and here are the biggest ones. Make sure you take care of these pitfalls when you start your journey on AWS, which will help you successfully migrate and set up on AWS.

Site reliability engineering (SRE) is fast becoming an essential aspect of modern IT operations, particularly in highly scaled, big data environments. As businesses and industries shift to the digital and embrace new IT infrastructures and technologies to remain operational and competitive, the need for a new approach for IT teams to find and manage the balance between launching new systems and features and ensuring these are intuitive, reliable, and friendly for end users has intensified as well.

Building new applications is a lot of fun, but troubleshooting and fixing the crashes that can come with app development is not. While many organizations are fast adopting the DevOps model, there are still some legacy frameworks where developers and operations teams are separate. Developers build and submit apps to their ops team, who in turn deploy and maintain the production stack. A common issue that arises due to this workflow is the time it takes to find and resolve crashes.

We’re excited to announce that Upsun now offers OpenSearch as a service available and included on all plans. OpenSearch is a distributed RESTful search and analytics engine you can use for log analytics, a search backend, clickstream analytics, and more. With the recent move by ElasticSearch to switch to a licensing model, it was important for us to propose a strong open source alternative. And OpenSearch is completely open source, so you could run and manage it on your own.

Industry analysts do primary research and two of the best, IDC and EMA (Enterprise Management Associates), have recently published some great insights for enterprises in 3 areas.

Investors have fallen back in love with profitability. This followed an almost two decade love affair with top-line revenue growth. The growth-at-all-costs paradigm enabled what I call cost-agnostic innovation: If it brings in more customers and revenue, build it — no matter how much it costs. When cash is abundant, investors can afford long-term risk, and cost-agnostic innovation works.

When IT operators and architects begin their journey with Google Cloud, Day 0 observability needs tend to focus on infrastructure and aim to address questions about resource needs, a plan for scaling, and similar considerations. During this phase, developers and DevOps engineers also make a plan for how to get deep observability into the performance of third-party and open-source applications running on their Compute Engine VMs.

Amazon Web Services (AWS) offers Cost Categories and tagging to help its customers track cloud usage and associated costs. But AWS customers still struggled to connect cloud costs with the products or people who build them despite endless tagging and defining Cost Categories. So, AWS announced Split Charges. This post walks you through what AWS Split Charges are, how they're configured, and how Split Charge rules work.