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.

For most companies it’s difficult to organize cloud spend because it relies on manual effort, like tagging. At CloudZero, we’re dedicated to helping customers make sense of their cloud investment without manual and repetitive work. Our code-driven approach to cost allocation makes it easy for customers to organize spend even if they have poor tagging, shared resources, or containerized infrastructure. Quite simply, we organize cloud spend better than anyone else in the world.

The past two years have seen erratic cloud spend thanks to the upheaval caused by the global pandemic. Looking ahead to 2022, business is beginning to normalize. Within that “new normal,” there is no question that cloud is more popular than ever, and Kubernetes is at an all-time high. Some companies are continuing to operate remote, or find that they are thriving thanks to an investment in the cloud.

Making better decisions doesn’t always require more data. Finding the right data and making sure the right people have it at the right time does. This is particularly important for companies that use the cloud. Using cloud financial planning solutions is an excellent way to automate, extend, and align goals with business outcomes in light of the cloud’s complexity. The solution can also help eliminate cumbersome, error-prone manual processes.

Knowing only how much you spent on your AWS bill each month isn’t enough to provide the cost visibility you need to make cost-aware engineering and business decisions. It's why AWS introduced tags. Tags enable AWS users to label their resources to track cost and usage in the vast AWS infrastructure. The goal of tagging is to help you understand who, what, and why your cloud spend is changing.

As a framework for goal-setting, the Objectives and Key Results (OKRs) methodology is an incredibly useful tool when implemented properly. It can help your engineering team better plan and stay aligned toward common objectives through the duration of the development process. On an individual level, OKRs can also encourage each team member to make personal progress toward their own goals or common team goals that would benefit the company.

AWS currently offers over 200 services. Some of those make up the AWS Cost Management suite. This group comprises AWS Cost and Usage Report (CUR), AWS Budgets, AWS Cost Explorer, AWS Cost Categories, and AWS Cost Anomaly Detection. Budgets and Cost Explorer are an excellent pair of complementary tools in this group. They have similarities that cause users to wonder if they need both and, if so, why. Here is a brief overview of the differences between AWS Budgets and Cost Explorer.

Self service analytics are becoming increasingly popular and essential in this data-driven world. For many businesses, there is a growing need for their internal departments to access their data and business intelligence and harness its power themselves. Traditionally, business intelligence processes are the purview of IT teams and data specialists.

The Snowflake data cloud offers powerful data warehousing, analytics, and processing tools. The platform can handle many data workloads on one platform, helping organizations turn data into actionable insight across teams, departments, and regions. Snowflake’s architecture is also unique. Compute and storage are completely independent and both are highly elastic. Yet, Snowflake's per-second billing and highly elastic compute model demand frequent usage and cost monitoring.