Access to CUR and Billing Info

While AWS Enterprise Account Representatives can provide valuable assistance and guidance, they typically do not have direct access to your Cost and Usage Report (CUR) or detailed billing information. This data is considered sensitive and is generally only accessible through your AWS account or organization.

For larger enterprises with multiple affiliates and separate AWS organizations, there are a few approaches to consider:

1. Centralized CUR: You can generate a centralized Cost and Usage Report (CUR) for all accounts under an AWS Organization from the management account. This allows for comprehensive cost analysis across the entire organization from a single point. However, this capability is only available for the management account, not for member accounts, even if they have delegated admin status.

2. AWS Organizations: If you're using AWS Organizations to manage multiple accounts, you can use the AWS Organizations APIs to retrieve information about linked accounts, payment methods, and invoices. This can help in consolidating some billing information across your enterprise.

3. Cost and Usage Report (CUR): While not directly accessible by your Account Rep, you can set up the CUR to deliver detailed cost and usage data at the account level to an Amazon S3 bucket. This data can then be analyzed using tools like Amazon Athena or exported for use in your FinOps activities.

4. AWS Billing Reports: You can utilize AWS Billing reports to download historical payment information. These reports can be scheduled for automatic generation and downloaded in various formats for further analysis.

For FinOps activities and EDP negotiations, you would typically need to gather and analyze this data internally, as AWS Account Reps don't have direct access to your detailed billing information. However, your Account Rep can certainly assist in interpreting the data, providing insights on cost optimization, and helping to structure an EDP that aligns with your organization's needs based on the information you provide.

Remember, while consolidating access to billing information is beneficial, it's crucial to maintain the balance with account/organization autonomy as you've mentioned. Proper IAM policies and access controls should be in place to ensure that sensitive billing data is only accessible to authorized personnel within your organization.
Sources
CUR report for Organisation | AWS re:Post
AWS managed policies - AWS Billing
Billing and Payments | AWS re:Post