Custom reports disappear after adding account to Billing Conductor group - Bug?

0

For new accounts, we deploy custom usage report using AWS CDK. Recently we started looking into Billing Conductor to manage and keep track of billing.

The issue is that when we add account that already had custom usage report created into existing Billing Conductor group, the custom usage report that we created in this account, will disappear...

As far as I can tell, there is no documentation of such thing happening, and no warning stating this is expected behavior....

Furthermore, even though the custom report disappears from the account, we are not able to recreate the report, as it says the report with name is already used. Even if we destroy the CDK that deployed this report, and then try to redeploy it, it will say that the report is already taken. So report is gone, but not really..

9:28:53 AM | CREATE_FAILED | AWS::CUR::ReportDefinition | xxxcostandusagereporthourly Resource handler returned message: "Resource of type 'AWS::CUR::ReportDefinition' with identifier 'xxx-cost-and-usage-report-hourly' already exists." (RequestToken: 2ad00a17-d6e8-486e-b31b-dd1e24a37c86, HandlerErrorCode: AlreadyExists)

So my questions are:

  1. This looks like a bug, where enabling Billing Conductor will make your existing custom reports disappear. Can anyone confirm?
  2. If it is a "feature" it should be documented. Follow up question is how do we remove the report that does not exist, but somehow exists so we can recreate it with the same name?
  • Hi,

    The behavior you're seeing (shielding member account CURs which reflect non-Billing Conductor-generated billing data) is a feature vs. a bug.

    I agree with your point, we will be update the user guide for Billing Conductor and the Cost and Usage Report to highlight this capability.

    For additional context, the report preference still exists (removing the account from the billing group will show the original member account report preferences to delete and recreate as needed). Hope this helps in the short term and thank you for surfacing.

    Best,

    Matt (Principal PMT, AWS Billing Conductor)

1개 답변
0

Hello,

I'm so sorry to hear about this trouble you're having, this is not the experience we strive for.

I'd recommend reaching out to our AWS CDK team via GitHub to report this concern, you can do so via this link: https://github.com/aws/aws-cdk.

Additionally, our Billing team can assist with any questions related to your bill. You can get help by creating a support case here: http://go.aws/support-center. Or, if you'd prefer you can also request a phone call, check out this article to see how: https://aws.amazon.com/premiumsupport/knowledge-center/aws-phone-support/.

Best regards,

— Aimee K

AWS
전문가
답변함 일 년 전

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인

관련 콘텐츠