In today’s fast-evolving digital landscape, the importance of robust and scalable cloud storage solutions cannot be overstated. Enterprises across the globe are increasingly leveraging cloud technologies to drive innovation, streamline operations, and reduce costs. Microsoft Azure, as a leading provider of cloud services, continues to enhance its storage solutions to meet the diverse and growing needs of its users.

Access to critical business data, such as cloud cost data, is both incredibly important for finance, engineering, and DevOps teams, but also a privilege that should be managed carefully. This month, our engineering teams put a major focus on developing industry-leading capabilities related to access control, while also making it easier for people who require certain kinds of data to get it where it needs to be.

After watching part one and part two of our FinOps Automation Series, hopefully you’re chomping at the bit to adopt your first automation solution. In part three below, our experts — Erik Peterson (CTO and Founder of CloudZero), Alan Hand (Founder and CEO of Xosphere), Steven O’Dwyer (Senior FinOps Specialist at ProsperOps), and Mike Fuller (CTO of the FinOps Foundation) — are going to walk you through what you need to know before you take any concrete steps.

Mattermost has embarked on a transformative journey in cloud optimization. This journey is marked by strategic initiatives, innovative approaches, and valuable lessons, all aimed at enhancing efficiency and reducing costs. This blog post explores the successful strategies that have guided our cloud optimization efforts. It also highlights our future direction with an emphasis on ARM/Graviton workloads and shares insights from our experiences, particularly regarding spot instances.

One significant challenge that every dynamic, fast-paced business in the cloud faces is efficiently managing their clusters’ workloads while minimizing unnecessary expenses. But it’s not just overages that these businesses must worry about. Especially common is the underutilization of resources, which can lead to unnecessary costs and inefficiencies.

When Google Cloud welcomed StackState to offer our full-stack observability solution to their network of customers, we were thrilled. Our excitement only grew when Google invited us to join other partners this week at Google Cloud Next ’24 at the Mandalay Bay Convention Center in Las Vegas.

Document libraries are the backbone of document management within SharePoint Online. They provide a centralized location for storing, sharing, and collaborating on files. These libraries offer features like version control, access control, and easy searchability, making them a powerful tool for businesses of all sizes. However, even with their many benefits, users might encounter occasional issues with document libraries.

CloudTrail logs are a type of log generated by Amazon Web Services (AWS) as part of its CloudTrail service. AWS CloudTrail records API calls made within an AWS account, providing a history of activity including actions taken through the AWS Management Console, AWS Command Line Interface (CLI), and AWS SDKs. For example, CloudTrail events are generated for actions such as EC2 instances start/stop, S3 bucket read/write and IAM user creation/deletion.

In parts one and two of this series, we covered how to limit deployments to Platform.sh when a tag is pushed or created. Focusing first on using GitHub and the GitHub Actions platform, and then progressing onto Gitlab and pipelines to accomplish this goal. But in the spirit of being a polyglot PaaS, let’s look at how we can accomplish the same goal—limiting deployment to Platform.sh only when adding a git tag—using Bitbucket and their CI/CD system.