AWS-ZachErdman

Aggregation CFN template for Data Exports

3

This commit adds a new cloudformation template to support CUR 2.0 in Data Exports with the same functionality as `cur-aggregation.yaml` By submitting this pull request, I confirm that you can...

Update to allowed ServiceCategory values

13

### Type > Type of issue Dimension > Normalized? Yes ### Description The list of service categories currently does not meet AWS's needs. We would like to add service category...

How to represent ODCRs in FOCUS

9

### Description On-Demand Capacity Reservations (ODCRs) ([AWS](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-capacity-reservations.html), [Azure](https://learn.microsoft.com/en-us/azure/virtual-machines/capacity-reservation-overview)) are an important service to many AWS customers. Currently, FOCUS does not have any native fields for indicating when an ODCR was...

[EDITORIAL] Column doc link formatting fix

4

We inconsistently wrote the names of columns in the links that link to columns throughout the spec. Sometimes they would have a space between words and sometimes not. I adjusted...

[Content Suggestion] FOCUS line item examples

3

### Description There are a few columns in which readers may interpret the column definition in different ways. This could cause cloud providers to populate columns differently or for cloud...

[Proposal] Add support for describing different types of usage of a single product.

8

### Type Type of issue: Dimension Normalized? No ### Description Cloud providers often charge customers for multiple types of operations for the same service (e.g., data transfer and data storage...

[Content Suggestion] Clarify what is included in FOCUS "Amortization"

6

### Description The FOCUS spec often refers to Amortization in a number of places and each time it provides a description of what Amortization is, but the exact definition has...

[DISCUSSION]: Formally document the backwards compatibility process for FOCUS

6

### Description FOCUS has been receiving some backwards incompatible changes in 1.1. We need to: 1. Document our definition of backwards incompatibility 2. Document our process for validating and merging...

If we don't force Unused commitment line items to be null for ConsumedQuantity, this is no longer a breaking change between FOCUS 1.0 and FOCUS 1.1. Making it 0 accomplishes...