1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
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
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 10 Monaten
- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor 4 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
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)