Multi-account
Which AWS accounts should you connect to Reserver?
Connect the accounts that run instances or buy reservations. Leave out the rest. Your plan counts only the accounts you connect.
The rule
Count accounts that run instances or buy reservations.
Reserver plans are priced by connected AWS account. A large AWS organization holds many accounts, and most of them run nothing that a reservation can cover. Count only the accounts below.
1. Accounts that run instances
Connect every account that runs RDS, ElastiCache, or EC2 that you want covered.
2. The account that buys reservations
Connect it even if it runs nothing. Reserver reads each reservation from the account that owns it.
3. Accounts with neither
A Log Archive or Audit account needs no connection. It does not count toward your plan.
Account roles
Why one organization holds so many accounts.
AWS tells teams to keep resources out of the management account.The Organizations guidance says to avoid deploying workloads there. In AWS Control Tower landing zone version 3.3 and earlier, the Security OU holds a Log Archive and an Audit account. Version 4.0 no longer requires that OU. Your organization may have these accounts, or it may not.
| Account role | What it usually holds | Connect it? |
|---|---|---|
| Production workload | The databases, caches, and servers that run your product. | Connect |
| Non-production workload | Staging and test fleets. They often run all year. | Connect |
| Sandbox | Short-lived experiments. Connect it only if instances run there for months. | Usually not |
| Management | Billing and AWS Organizations. AWS says to keep workloads out of it. | Only if it buys reservations or runs instances |
| Log Archive | Stored logs. It runs storage, not databases or servers. | Usually not |
| Audit and security tooling | Read-only access for auditors and security tools. | Usually not |
What it usually holds
- Production workloadThe databases, caches, and servers that run your product.
- Non-production workloadStaging and test fleets. They often run all year.
- SandboxShort-lived experiments. Connect it only if instances run there for months.
- ManagementBilling and AWS Organizations. AWS says to keep workloads out of it.
- Log ArchiveStored logs. It runs storage, not databases or servers.
- Audit and security toolingRead-only access for auditors and security tools.
Connect it?
- Production workloadConnect
- Non-production workloadConnect
- SandboxUsually not
- ManagementOnly if it buys reservations or runs instances
- Log ArchiveUsually not
- Audit and security toolingUsually not
Three example organizations
Your plan depends on the accounts you connect.
These shapes are examples. Your counts will differ. Each plan comes from the live plan catalog, so it matches the pricing page.
A startup with four accounts runs its database in one of them. One connection is enough. A growth team with twelve accounts may run instances in only four. The enterprise runs workloads in most of its accounts, so it connects most of them.
The caveat
An unconnected account that runs instances is invisible.
Reserver reads only the accounts you connect. It cannot see an instance in an account you left out.
Reserver matches a Regional reservation to instances in every connected account. AWS can share a reservation discount across accounts on one consolidated bill. If a shared reservation covers an instance in an account you did not connect, Reserver does not see that instance. The reservation can look unused. Or Reserver can match it to a different instance in a connected account. Either way, the coverage map does not show what AWS bills. Connect every account that runs instances you want covered. Read how discount sharing works to see where AWS applies a shared discount.
What comes next
You connect each account yourself today.
Use the 1-click stack or enter a role by hand. One connection covers one account. Finding every account in an AWS Organization is on the roadmap and is not built.
See the Price check to find your plan. Set the AWS accounts slider to the number you will connect.
Do Log Archive and Audit accounts count toward my plan?
Only if you connect them. A plan counts connected accounts. These two accounts usually run no databases or servers, so most teams leave them out.
Do I need to connect my management account?
Only if it buys reservations or runs instances. AWS says to keep workloads out of the management account. If you buy reservations there, connect it so Reserver can see them.
What happens if I leave out an account that runs instances?
Reserver cannot see those instances. A shared reservation that covers them can look unused. Or Reserver can match it to a different instance in a connected account. Connect every account that runs instances you want covered.
Does every Control Tower landing zone have a Log Archive and an Audit account?
No. AWS says landing zone version 3.3 and earlier creates both accounts. Version 4.0 no longer requires a Security OU, so a newer landing zone can look different.
Will Reserver find my accounts on its own?
Not yet. You connect each account yourself today. Finding every account in an AWS Organization is on the roadmap and is not built.
Sources, fetched and confirmed on 2026-10-25: AWS Control Tower: how it works; AWS Organizations: best practices for the management account; and How billing works with Reserved Instances and consolidated billing.
Stop overpaying for a steady fleet.
Reserver is in early access. Join the list, and we will onboard you when we have capacity. Your first recommendation lands within minutes of connecting.