There's a pattern that plays out at almost every company that's been on AWS for more than a year or two.
It starts with one AWS account. Everything's visible, manageable, and in one place. Then you separate production from staging. Then a new product team needs its own account for isolation. Then compliance says the data team needs a dedicated account. Then you acquire a company with three accounts of their own.
Suddenly you have six AWS accounts, and nobody has a clear picture of what's running where.
For compute (EC2, ECS, Lambda), this is annoying. For databases (RDS, Aurora, Redshift), it's actively dangerous. Missing a database instance means missing a security patch, an expiring certificate, a slow query eating your IOPS, or a dev instance that got promoted to prod and forgotten.
TL;DR
Managing RDS across multiple AWS accounts is painful because AWS has no native cross-account database inventory. We built 1DataCloud to solve this — connect multiple AWS accounts and see all your RDS, Aurora, Redshift, DynamoDB, and other instances in one unified view. Try it free →
Why AWS Doesn't Solve This Natively
AWS Organizations gives you billing consolidation and policy management, but it doesn't give you a unified database inventory.
AWS Resource Explorer gets closer — it lets you search for resources across accounts and regions — but it's designed for broad resource discovery, not database-specific visibility. You can't easily see instance engine versions, connection configurations, or schema metadata from Resource Explorer.
For RDS specifically, the native experience requires:
- Logging into each account individually (or assuming a role)
- Navigating to RDS in each region you care about
- Manually noting instance class, engine version, multi-AZ status, backup retention, etc.
- Repeating for Redshift, Aurora, DynamoDB, ElastiCache...
If you have 4 accounts × 3 regions × 5 services, that's 60 console views to get a complete picture. Nobody does that. Which means nobody actually has a complete picture.
The Real Operational Risks
Here's what happens when you don't have a unified view:
Forgotten instances
Dev databases created for a sprint that never got terminated. They're still running, still incurring costs, potentially still accessible. You don't know they exist until you see the bill — or until a security audit finds them.
Inconsistent configurations
Production RDS with Multi-AZ enabled. Staging without it. A new engineer copies the staging config to set up a new "prod-like" environment and skips Multi-AZ because they didn't know it was supposed to be on. This is invisible without a cross-account view.
Missed engine upgrades
MySQL 5.7 end-of-life hit a lot of teams hard. If you don't know which account has which engine version, you can't prioritize upgrades. You find out when AWS forces the upgrade for you — often at a bad time.
Shadow databases
Engineers with enough permissions create databases for testing and never clean them up. These accumulate across accounts. Some of them have real data in them.
Onboarding friction
Every new engineer needs a "tour" of which databases exist, what they're for, and how to connect. This knowledge lives in someone's head or in a wiki that's always out of date.
How Multi-Account RDS Management Should Work
The ideal state is simple: one view that shows every database instance across every AWS account, with enough metadata to make decisions without digging further.
That means:
- Account name/ID
- Region
- Instance identifier
- Engine and version
- Instance class
- Status (running, stopped, rebooting)
- Multi-AZ enabled?
- Publicly accessible?
- Storage size and type
- Connection endpoint
And ideally, with one more click: the schema — tables, columns, types — so you can understand what the database actually contains.
What We Built
1DataCloud connects to multiple AWS accounts and gives you exactly this.
Connecting an account takes about 2 minutes:
- Create a read-only IAM role in each AWS account (or use an existing access key with read permissions)
- Add the credentials to 1DataCloud
- The platform discovers all supported instances across all connected regions automatically
What gets discovered:
- Amazon RDS (MySQL, PostgreSQL, MariaDB, Oracle, SQL Server)
- Aurora
- Amazon Redshift
- Amazon DynamoDB
- Amazon ElastiCache
- Amazon DocumentDB
- Amazon Neptune
What you see:
A unified inventory — all instances, across all connected accounts, in one table. Filter by account, region, provider, or status. No more switching tabs.
Schema exploration:
Click any RDS or Redshift instance and browse its tables, columns, data types, and indexes — fetched read-only through the AWS API. Useful when you need to understand what a database contains before connecting a new tool to it, or when you're onboarding a new engineer.
The IAM Setup
Since I know this is the question DevOps teams always ask first: yes, you can connect with least-privilege read-only permissions.
You need read access to:
rds:DescribeDBInstancesrds:DescribeDBClustersredshift:DescribeClusters-
dynamodb:ListTables,dynamodb:DescribeTable - And the equivalent for other services you want to inventory
1DataCloud never writes to your AWS resources. All operations are read-only. Credentials are Fernet-encrypted at rest and never exposed in the UI or logs.
What This Solves in Practice
Runbook: "What databases are we running in eu-west-1?"
Before: open AWS Console in each account, navigate to RDS in eu-west-1, repeat.
After: filter the 1DataCloud inventory by region = eu-west-1. Done.
Runbook: "Which instances are still on MySQL 5.7?"
Before: navigate to RDS in every account and region, export, aggregate in a spreadsheet.
After: open the 1DataCloud inventory — engine and version show as plain columns on every row, so it's one table to scan instead of sixty console views.
Onboarding: "Show the new engineer what databases we have"
Before: a 30-minute walkthrough across multiple consoles.
After: share the 1DataCloud dashboard link.
What's Coming
Cross-account visibility is already in the unified view. The next step — currently in development — is cross-database querying: asking a single natural-language question that spans multiple instances and merging the results. Think: "How many users were created in the last 30 days across all our regional databases?" — one question, aggregated answer.
Try It
If you're managing RDS across more than one AWS account and want a single inventory without building internal tooling, 1DataCloud is worth trying.
Free plan: connect up to 3 instances across any cloud. No credit card.
Top comments (0)