POL-1401 - New Template: Shared Cost Reallocation - AWS Support

[bryankaraffa]

Description

This policy template reallocates AWS Support costs (OCBPremiumSupport, AWSEnterpriseSupport, AWSSupportBusiness, AWSSupportEnterprise) to the AWS Linked Accounts within the AWS Organization. Costs are allocated to each AWS Linked Account based on the percentage of total that account consumed in the bill period.

To reallocate the costs, the policy template uses Flexera's "Common Bill Ingest" (CBI) capability to negate the original cost allocated to the AWS Master Payer Account with negative cost line items, and write the reallocation portional costs as new line items.

Issues Resolved

https://flexera.atlassian.net/browse/POL-1401

Link to Example Applied Policy

• Advanced Demo Org Dashboard with original shared cost totaling $0
• Advanced Demo Org Dashboard with reallocated costs (totally the same as original shared cost for each month)
• Advanced Demo Org Applied Policy search "AWS Support"

Contribution Check List

• New functionality includes testing.
• New functionality has been documented in the README if applicable
• New functionality has been documented in CHANGELOG.MD

[github-actions]

	1 Error
🚫	operational/aws/shared_cost_reallocation/aws_support/shared_cost_reallocation_aws_support.pt Policy Template has console.log() statements. These are used for debugging and should not be present in catalog policy templates: Line 655 Line 665 Line 739 Line 749 Line 783 Line 784 Line 785 Line 874 Line 884 Line 958 Line 968

	2 Warnings
⚠️	Important Files Modified Please make sure these modifications were intentional and have been tested. These files are necessary for configuring the Github repository and managing automation. .spellignore
⚠️	operational/aws/shared_cost_reallocation/aws_support/shared_cost_reallocation_aws_support.pt Detected new request datasource(s) in Policy Template file. Please verify the README.md has any new permissions that may be required.

Generated by 🚫 Danger

[bryankaraffa]

Policy Template has console.log() statements. These are used for debugging and should not be present in catalog policy templates

These are false positives from logSample usage... we may want to sync how we want to move forward on this as I think it's something we will want to use in other PTs

[bryankaraffa]

We have 2 customers so far who have deployed this, validated the outcome, and are moving forward with backfilling historical cost data.

Biggest issue we are encountering is policy execution timeout limits (30m) in some of the larger tenants we are testing in. Could be mitigated/prevented by increasing policy timeout limit globally or per-org.

[nia-vf1]

LGTM

[nia-vf1]

Adding "DO-NOT-MERGE" label as per Bryan's comment above. We want to do some more testing potentially on a smaller customer at daily granularity

Other than that, the PR looks good. We may want to consider removing console.logs from the policy template when we are happy and ready to publish to the Catalog