Operations | Monitoring | ITSM | DevOps | Cloud

The Securities & Exchange Commission (SEC) wants to increase transparency on a company’s carbon footprint, which ultimately would impact valuations. In late March, the SEC released a proposed rule that would force companies to release climate-related disclosures, including information about their carbon footprint and their risk exposure. The goal is to add tangible value to the impact and risks of climate on a company’s operations.

When I co-founded CloudZero, I set out to change the way the world thinks about cloud cost optimization and management. For too long, I had watched cloud cost optimization vendors neglect to help companies build better, more cost-effective software. Instead, everything focused on buying better, by optimizing prices and discounts.

While Financial Operations (FinOps) isn’t a new concept, it is becoming more prevalent in companies that have started seeing increases in their cloud spend. Historically, when engineers needed to set up infrastructure to complete a project, they had to go through a long process of procuring servers, finding space in a data center, and getting financial approval. This process could take two months or more, so it allowed plenty of time for oversight by the financial department.

Businesses both small and large use cloud services to help maintain their data. But managing cloud services — and making sure you stay within your budget — can be a challenge. To maximize your money, you need to focus on one thing: efficiency. If you can be efficient with your time and finances, getting your cloud services up and running will be a breeze.

Cloud costs are a daily concern for companies running applications on Amazon Web Services (AWS). This makes sense because many organizations struggle with unexpected AWS charges. Although many organizations have a cloud budget in place, accurately controlling costs is difficult. Real-time cost remediation is often difficult for many, leading to inflated AWS costs every billing cycle. No matter where you are on your cloud journey, reducing AWS costs is something you’ll want to do continuously.

When your organization uses the cutting edge of technology to function, you may feel like it takes all your time and energy to stay on top of emerging trends. How are you supposed to anticipate what the future will hold when you have to balance those considerations with how to best provide for your customers’ needs today? It’s okay if you don’t have your finger on the pulse 100 percent of the time.

For SaaS companies, the cloud plays a significant role in product creation and delivery. As one of the top drivers of COGS, cloud costs have a major impact on key financial metrics and can dramatically impact revenue and valuation. However, that creates a scenario ripe for conflict: Engineers make important decisions about features and functionality without clear insight into how those decisions will impact spending—and finance continuously gets surprised by seemingly exorbitant cloud bills.

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.

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.

Amazon Web Services (AWS) provides over 200 fully-featured services, that aim to make the cloud affordable and cost-efficient for the companies that use the popular cloud provider. Yet, the average AWS customer wastes 30% to 35% of their cloud budget on unnecessary costs. But why? Many organizations running on AWS report challenges managing their infrastructure — and some engineers feel their native tools simply do not cut it for managing their enterprise applications.