You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we have billing consolidation across several accounts, it is sometimes best to reserve instances on the parent account, which then apply to all the child accounts.
In this situation we need several access-key pairs - one key to be able to retrieve reservations from the parent, and other keys to get the instances-in-use in the desired child(ren).
I will fork and PR for this use case.
The text was updated successfully, but these errors were encountered:
Sounds good to me! In my professional life, we purchase with in each account for clear delineations on which department/project incurs the cost. Amazon still will spread these across our accounts (we have ~90+) if they go unused still. Interesting to hear how others handle that. I really wish all of our reservations lives under a single account!
I'm happy to talk about what you think your enhancement should look like.
Additionally, please excuse the mess that this project is :) I've gotten so hung up on "doing things the right way" in the past, that I never really publish/finish anything. Feel free to apply any logic/efficiency refactors along the way :)
If we have billing consolidation across several accounts, it is sometimes best to reserve instances on the parent account, which then apply to all the child accounts.
In this situation we need several access-key pairs - one key to be able to retrieve reservations from the parent, and other keys to get the instances-in-use in the desired child(ren).
I will fork and PR for this use case.
The text was updated successfully, but these errors were encountered: