Initiating Amazon Web Services (AWS) appears simple enough: Create an account, spin up a few compute instances and let the magic and speed of AWS take care of the rest. Moving past this initial phase, however, is not necessarily straightforward. Even if the primary use for AWS is for non-production use—whether that be for testing or research and development—once embedded into an organization, challenges will arise around billing, scaling limits and resource control. Segregation of infrastructure, resources and services is necessary for AWS to be integrated for technical, financial and business process purposes.
Here’s the bottom line: a single account for any size organization is not going to work. Virtual resources, developers and products will eventually get muddled together, causing an administrative burden to track and maintain. Further, one department’s decisions could negatively affect another or, worse, bring down a live production application.
- Dealing with soft limits
- Simplified billing
- Consolidated billing features
- Cross-account access
- Cross-account services
The creation and use of multiple accounts on AWS is a supported and logical design pattern that can help your organization create, deploy and support a variety of internal and external cloud products. The tools are available – the next step is up to you! Discover more about managing multiple AWS accounts today.