Idea: how to avoid many small invoices (one per management account) and how to use credits

[s0enke]

Problem

Since the MAVM creates standalone accounts, AWS will create one invoice / charge per management account / AWS Organization (if tax inheritance is disabled, it might even create one invoice and charge individually per member AWS account). This will spam / DoS the accounting department since they have to process and map each invoice and payment indivudally.

Another issue is that credits cannot be used with many management accounts, since they are per account and only shared within one organization. So with many MAVM accounts being vended and used, credits cannot be used efficiently.

Possible solution

One solution would be - instead of closing the management account after 24 hours - to still suspend it, but before move it to another "landfill / dump" AWS Organization, which has Tax Inheritance enabled, and might also have credits loaded.

• for that, if applicable, an existing AWS Organization in the MAVM-vended account has to be removed
• for that all member AWS accounts have to be removed from this AWS Organization beforehand, MAVM cannot do that because it has no root-access to the member AWS accounts.
• then the AWS Organization of the MAVM-vended AWS account can be closed
• then the "landfill" AWS Organization can invite the MAVM-vended AWS account
• the MAVM-vended AWS account billing runs under the "landfill" AWS organization and it leverages Tax Inheritance settings as well as possible credits.