AWS-ZachErdman

> Great work! I've added few comments inline. Also I see that PermissionsBoundary parameter and policy property excluded compare to current version. Is this intentional? > > https://github.com/aws-samples/aws-cudos-framework-deployment/blob/02aec4cdda9e2e86e2b67b0e0ae315384a49be2a/cfn-templates/cid-cfn.yml#L211 @yprikhodko I...

@yprikhodko and @iakov-aws have you seen this error before? I'm getting it when trying to run the CFN template outside of us-east-1 All other resources besides SourceS3 seem to be...

Are there any specific use cases these columns would help? I'm concerned whether the value of these columns are worth increasing the schema size.

Sharing this closed issue related to discounts as I had a solution I'd like folks to consider: https://github.com/FinOps-Open-Cost-and-Usage-Spec/FOCUS_Spec/issues/338

I support putting the version number in the manifest for each delivery. If appending different versions of data, a practitioner should be able to add the column to show this,...

@mike-finopsorg Yup, agreed that it's impossible to have a 1:1 matching for all providers categories which makes this a tricky task. @flanakin Thanks for sharing the principles for choosing categories....

> Should `Numeric Format` be updated? I don't think that's needed since it's not a column in FOCUS, so it wouldn't appear as NumericFormat.

I see - when the column is being referenced in a requirement, it's supposed to not have a space.

1st column draft: https://github.com/FinOps-Open-Cost-and-Usage-Spec/FOCUS_Spec/tree/capacity_reservations sample data: https://docs.google.com/spreadsheets/d/1LdgZCBuV6TDehgykQ4m6AluOLE_TjX9kFxKXymXn8I4/edit?gid=1124060342#gid=1124060342

> I like this idea. We could introduce a fictitious provider or maybe a couple different types of providers to support this. Let's just make sure the example values are...