Skip to content

AWS Free Tier credits expiration after joining AWS Organization

-3

I recently set up an AWS Organization for my startup (the recommended approach for any serious multi-account setup), and discovered after the fact that my Free Tier credits expired immediately upon joining, of course with no warning, no confirmation dialog, and no email notification.

I only found out when I contacted support. The agent confirmed it was expected behavior per the Free Tier FAQ. I understand the policy exists, what I'm pushing back on is the complete absence of any user-facing warning at the moment it happens.

The AWS Organizations join flow has no mention of credit expiration. No email is sent when credits expire for this reason. New founders following best-practice multi-account guidance are penalized without being told, and the behavior is documented but buried in an FAQ rather than surfaced at the point of action.

This is a straightforward UX fix: a single warning banner or confirmation step in the org join flow would prevent this from catching every new founder off guard. The policy itself may be intentional, the silent execution is not defensible.

Has anyone else run into this? And is there an official channel to submit product feedback on billing UX?

3 Answers
8

Q6. What happens when my account creates or joins an AWS Organization?

https://aws.amazon.com/free/free-tier-faqs/

PS: I think this has been shared here a few times already, e.g. -> https://repost.aws/questions/QUqw-vLvrJQEeW_n8INbFpSA/free-tier-and-aws-organizations-is-free-tier-consolidated-or-only-for-first-aws-account-under-organization ... so it might be familiar to a lot of people in the community, but no need to open this addition thread ...

EXPERT
answered a month ago
1

I understand your frustration with the lack of warning about Free Tier credit expiration when joining an AWS Organization. While I can't speak to the specific organizational join flow experience you described, I can address the general Free Tier expiration process.

The AWS Free Tier eligibility expires 12 months after you first activate your AWS account and cannot be extended. As the expiration date approaches, AWS recommends shutting down or deleting any resources you don't need to avoid charges at standard billing rates after eligibility ends.

For product feedback and feature requests related to AWS services, including billing UX improvements, I'd recommend:

  1. AWS Support - Since you've already contacted them, you can continue that conversation to escalate feedback
  2. AWS re:Post - AWS's community-driven Q&A service where you can share feedback and connect with AWS experts
  3. Your AWS account team - If you have a dedicated account manager or solutions architect, they can channel feedback internally
  4. AWS Feedback forms - Available within various AWS console services

Your point about needing clearer warnings at critical decision points is valid user feedback. The gap between documented policy and user experience at the moment of action is exactly the kind of input that helps improve AWS services. I'd encourage you to submit this through the official channels mentioned above, as product teams do review and prioritize customer feedback for UX improvements.
Sources
Avoiding unexpected charges after Free Tier - AWS Billing

answered a month ago
AWS
EXPERT
reviewed a month ago
  • this is 100% accurate and also 100% useless reply, because I am on the re:Post already.

  • This is not going to happen your failure got you into this, if your developing a business on free-tier you're already doing it wrong.

0

You can send feedback on the FAQ page - https://aws.amazon.com/free/free-tier-faqs/ . Click on the star at the right side of the page. For Free Tier, think of having 1 free tier per billing entity.

EXPERT
answered a month ago
EXPERT
reviewed a month ago
  • I think you misunderstanding the problem - they immediatly expired all credits for all accounts who joined AWS organizations, with no warning at all. What is this have to do with 1 free tier per billing entity statement?

  • Yes, because the root/main account in your Organisation is the billing entity/account. That account had the free tier when it started the created. When you add new accounts to the Organisation, the main account remains the main billing entity.

  • You failed to read the the T&Cs and teh FAQ and it's AWS problem. Nope.

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.