AWS credits are promotional or prepaid dollar balances that Amazon Web Services applies against eligible service charges before it bills a payment method. They matter to anyone planning a project on a budget, and they are the defining feature of five of the options listed on the Buy AWS Account page, which run from a $1K balance up to $100K. This article explains how a balance is consumed, what it usually does not cover, and the specific things to confirm before you build a plan around one.
What an AWS credit is, and what it is not
A credit is a draw-down pool attached to a specific account. Each month, AWS totals the eligible usage on that account, subtracts the credit, and bills any remainder to the payment method on file. The balance is not cash, it cannot be withdrawn, and it stays tied to the account it was issued to.
Legitimate credit sources include a Free Tier allocation, an AWS Activate award, a partner program or another promotional grant. Whatever the origin, the balance comes with terms: an issue date, an expiration and a list of eligible services. Those terms travel with the credit and continue to apply after any change of control.
The listed AWS credit options
The marketplace lists five credit-carrying AWS options. The first figure in each name is the credit balance; the price is what the listing costs.
| Listed option | Listed price |
|---|---|
| AWS $1K Credit Account | $220 |
| AWS $5K Credit Account | $950 |
| AWS $10K Credit Account | $2200 |
| AWS $25K Credit Account | $4500 |
| AWS $100K Credit Account | $16500 |
These sit alongside the Free Trail, vCPU and Bedrock options described in AWS account types explained. The credit options are the ones to look at when cash outlay during the first months is the constraint, rather than quota or model access.
How a balance is consumed month by month
Credits apply automatically. You do not choose which charges they cover; AWS applies the balance to every eligible line item on the invoice until the balance reaches zero. EC2 hours, S3 storage, data transfer and Bedrock token usage are all typical eligible charges.
Once the pool is exhausted the account continues under standard pay-as-you-go pricing, provided a valid payment method is attached. If no payment method is present, AWS may restrict resources according to its policies. Plan the transition before it happens rather than after.
What credits typically do not cover
Not every charge is eligible for every credit type. The AWS source material for this marketplace calls out three categories that commonly fall outside coverage:
- AWS Marketplace purchases, such as third-party software subscriptions
- Support plans
- Certain reserved-capacity and specialized capacity products
The exact exclusions depend on the terms attached to the specific balance. If your architecture leans on a Marketplace AMI or a paid support tier, budget for those as cash costs from day one.
Five things to confirm before relying on a balance
A credit account is only as useful as the balance that remains and the time left to use it. Before committing a project timeline to a listed option, confirm the following, ideally with console screenshots or exports rather than a verbal summary:
- Remaining balance and currency. The name of the option describes the original allocation; verify what is actually left.
- Issue date and expiration. Credits expire, and an expiring balance is worth less than a fresh one of the same size.
- Service coverage. Check that the services you plan to run are eligible.
- Paid-plan status. Find out whether the account has already converted to a paid plan and what that means for the credit.
- Spending limits or holds. An active hold can block resource creation regardless of the balance.
Planning spend against a credit balance
Treat the balance as a runway, not as free money. Set an AWS Budget equal to the credit amount, add alerts at sensible thresholds, and review Cost Explorer weekly so you see the burn rate before the balance is gone. The habits in cost control for new cloud accounts apply here without change.
Match the balance size to the workload honestly. A short proof of concept rarely needs the larger tiers, while sustained GPU training or high-volume Bedrock inference can consume a mid-sized balance quickly. If you are weighing AWS against other providers’ credit options, cloud accounts with credits compared lays the listed balances side by side.
Operating within AWS terms
AWS accounts are intended for the party that created them, and the Customer Agreement addresses account transfers. Buyers should read the current terms and understand that AWS can suspend accounts that appear to have changed hands under suspicious circumstances. Ask for confirmation that the account and its credits came from legitimate channels, then secure the account immediately: rotate the root password, enable MFA, review IAM users and roles, and attach your own payment method. For broader guidance on how balances behave across providers, see how cloud credits work across providers and the AWS section of the Cloud FAQ.
