GET ORGANIZED! - Learn AWS Organizations for Beginners - Billing and RI & Savings Plan Overview
HTML-код
- Опубликовано: 26 сен 2022
- We go through the AWS Organizations foundational concepts, touching on some basic multi-account strategies, then the benefits of using linked accounts from an accounting and cost-savings perspective.
Learn how you can benefit from consolidated billing!
Save money with AWS through volume-based discounts through their tiered pricing model, and learn how to maximize your reserved instances or savings plans by sharing the discounts across multiple accounts.
---
This video is a lesson from a course focused on the AWS Certified Cloud Practitioner exam course, available at cloudvikings.io
If you're looking to start learning about AWS, this course assumes no prior knowledge about AWS and helps you learn the basics of AWS and learn the real-world application of important cloud and AWS concepts.
Use the discount code to get the free course while it's in the beta stage of development -- CCPCourseBetaYT
cloudvikings.io/course/aws-ce...
--
#aws #awscertification #awscloudpractitioner #organizations #cloud #cloudtraining #awstraining #billing #costs 
Наука
Well articulated, thank you.
Very nicely explained. Thanks ❤
Detailed and well presented.
Well Detailed Explanation
Excellent explanation
Glad it was helpful!
Thanks for the insight. Was wondering how to make sure your organization management account shows billing for all accounts. Since in my case, I do not have it working yet. For now, it only shows the costs of its own account, and nothing of the accounts in any of the OU's. (Still on free tier though, not sure if that matters).
Thanks for checking out the video! By default, the consolidated billing features should be enabled for your Organization account structure. I'd suggest ensuring the non-management accounts are properly linked and the consolidated billing (or all) features are enabled.
docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_org_support-all-features.html
docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_accounts_invites.html
If you're using tools like cost explorer, ensure you're not using any Linked Account filters so you get the aggregated view of costs across all accounts.
Note that the "Billing Data", more your AWS invoice details, won't reflect the consolidated costs until the next billing cycle of when new member accounts were added.
docs.aws.amazon.com/cost-management/latest/userguide/differences-billing-data-cost-explorer-data.html
Thanks for the video.
I have one nore scenario other than what you have explained.
Suppose in an organisation there are 10s of member account.
I manage only 2 of them. One is prod another one is non-prod. Who manages other 8 member account I have no clue. So in my 2 member account discount sharing is disabled and I have overcommitted in my Prod account and undercommited on Nob-Prod account. I want to benefit on my Non-Prod account the amount that I have overcommitted in Prod account.
But I do not want to share the discount with other 8 account. I want to keep the sharing between my 2 accounts.
Is there a way to make this solution possible??
Waiting for the response.
Thanks for the question!
In a 10 member account organization structure, where you are the cost owner responsible for prod and non-prod, and the remaining 8 other accounts belong to other owner(s), you can share the Savings Plan (SP), and Reserved Instance (RI) discounts between only your two specific accounts. Essentially RI/SP discount sharing would be only enabled on your two prod and non-prod accounts so any under-utilized commitment amounts from one of those two accounts could be shared with the other.
(docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/ri-turn-off.html)
Now, to extend on your scenario further, the challenge would that what if the owner(s) of the remaining 8 accounts also make an RI/SP commitment and would like to share those discounts across a sub-set of accounts that they are responsible for as well. Discount sharing would need to be enabled on these other accounts, however, now the combined RI/SP discounts would apply across all of the accounts in the AWS Organization that are enabled for discount sharing.
In the real-world, I can't see that this would be an issue. Ultimately the discount benefits the organization as a whole.
If in certain months, the RI/SP from the other 8 accounts is under-utilized a bit, the remaining usage discount would spill over to your prod and non-prod account and you would get further discounts if you happened to to over your committed usage levels. And the reverse, if your prod and non-prod usage was a bit lower in a given month, and you had some RI/SP coverage to spare, that could spill over that usage discount into whatever subset of accounts that are also enabled for discount sharing.
Again, the company/organization as a whole benefits from the overall discounts and the RI/SP investment.
If for some reason the company or cost center owners did NOT want to share any RI/SP discount overages with other accounts in the organization, I don't believe there is a way to do that other than only doing RI/SP purchases within a specific account and not doing any discount sharing at all. I'm not sure why an organization/company would want to have surplus discount potential go to waste rather than share it with other accounts in the company to take advantage of additional savings.
"Hey, I got the approval for this RI/SP commitments for my accounts from my cost center budget, they're for me only, and I don't care if the company could save more money by sharing the left over unused usage commitment and would rather see that go to waste."
If this was the case, it may make sense to look at a multi-AWS organization structure. If cost centers and ownership are this divided at a company, it may make sense in some cases to have multiple AWS organizations if there are specific compliance, security, and cost concerns like in this example, where there are groups within a large enterprise company essentially operating as their own organization silo(s). This way the account/workload owners of specific accounts now have full control/responsibility of their AWS usage and costs. Keeping in mind the additional overhead of managing multiple organization structures in terms of OU, account structures, SCP and other security policies, and you'd have multiple AWS invoices, representing the costs from within the linked member accounts of each separate AWS organization structure.
Another alternative scenario may be to enable RI/SP discount sharing across all accounts in the organization. If you obtain the budget and approvals for an RI/SP commitment(s) on your specific accounts you own, these purchases and resulting discounts can be considered at an internal finance/accounting level in the organization. The organization would let the RI/SP savings get shared everywhere to maximize the discount, however you'd be shifting the charge-back/show-back burden to your finance/accounting teams to determine how much of that discount is applied to your specific accounts. So if you're combined prod and non-prod accounts came to $200k for the month, the accounting teams would then discount those cloud infrastructure costs internally from your overall infrastructure cost budget you're responsible for based on the RI/SP ratios. The finance team would basically be managing how shared RI/SP discount benefits are applied to overall team/department/organization budgets internally rather than AWS calculate this directly into the invoice(s). This isn't horribly difficult to determine each month, especially with good account structures, resource tagging, and cost categories in place. A lot more burden is placed on the finance teams to figure all that out, but just mentioning this as another possible scenario to think about. In this scenario the company as a whole can maximize all the available discounts for their cloud infrastructure investments, but the appropriate RI/SP commitment budgets and discounts are internally attributed back to the proper teams/departments that "own" those RI/SP and respective sub-set of accounts.
@@cloudvikings Thanks for taking time and giving the explanation. I do agree with all of your points.
Rather than giving Admin overhead to finance team. I would rather request AWS to create some kind of boundary line permission/restrictions to enable the feature to restrict Savings plan discount within specific linked accounts.