AWS provides an invoice structure that accountants understand how to navigate. Open Source mostly doesn't.
I know this is why some of the "contribution bundling" approaches seem to have good merit for big Enterprise that treat Open Source a bit like a "stock portfolio" and bundle a number of open source sponsorships into a single invoice that you can present to upper management as "IT says we need to pay this bill each month because it somehow helps keep all the software lights on" without needing to get into the specifics of which software does what or how much you rely on it (or the complexity of your dependency trees).
I've heard it's a priority for parts of GitHub to make such "automated open source sponsorship bundles" easier to sell to upper management and smarter in how they manage their funds for the good of the open source community and wish them luck in those endeavors.
I know this is why some of the "contribution bundling" approaches seem to have good merit for big Enterprise that treat Open Source a bit like a "stock portfolio" and bundle a number of open source sponsorships into a single invoice that you can present to upper management as "IT says we need to pay this bill each month because it somehow helps keep all the software lights on" without needing to get into the specifics of which software does what or how much you rely on it (or the complexity of your dependency trees).
I've heard it's a priority for parts of GitHub to make such "automated open source sponsorship bundles" easier to sell to upper management and smarter in how they manage their funds for the good of the open source community and wish them luck in those endeavors.