Got AWS saving plan negation for monthly costs for AWS lambda but no saving plans purchased

0

Hi community members, My team just noticed a saving plan negation on AWS lambda for around 40% of the total lambda costs, but we did not purchase any saving plans nor did the saving plan overview and history imply. The negation is mostly applied to June only. This is weird. Does anybody know why is this happening? Thanks in advance.

1 Answer
2
Accepted Answer

Hello.

Is your AWS account managed by something like AWS Organizations?
If it is managed by AWS Organizations, it is possible that you purchased Savings Plans with another member AWS account and the remaining commitments are shared.
https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/ri-turn-off.html

If your account is not managed by AWS Organizations and you have never purchased SavingsPlans, I recommend that you open a case with AWS Support under "Account and billing".
Inquiries under "Account and billing" can be made free of charge.
https://docs.aws.amazon.com/awssupport/latest/user/case-management.html

profile picture
EXPERT
answered 2 months ago
profile picture
EXPERT
reviewed 2 months ago
profile pictureAWS
EXPERT
reviewed 2 months ago
  • Yeah, you are right. we are under an organization with shared saving plan preference enabled. Still, it was hard to diagnose the root cause when the saving plan overview did not show anything and we did not have enough permissions to see across the resources shared among the accounts.

    Anyway, thanks a lot for the answer.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions