Reference Architecture for AWS
Designed under optimal configs for the most popular modern web and mobile applications needs. Its design is fully based on AWS Well Architected Framework.
Don't reinvent the wheel. AUTOMATE.
Save time and effort by leveraging existing solutions
What is Leverage?
Our focus is on creating reusable, high-quality AWS Cloud Infrastructure code
Leverage is a significant amount of knowledge, acquired through several years of experience, turned into an ecosystem of code, tools and workflows that let you build your AWS Apps infrastructure quickly and securely.
Infrastructure as Code Library
Enables you to safely and predictably create, change, and improve your cloud infrastructure 100% as code.
Leverage CLI
Run one consistent workflow — initialize, configure and orchestrate every AWS account and layer — from your terminal.
- leverage project init
- leverage project create
- leverage tofu apply
Reference Architecture for AWS
Well-Architected from day one
IaC Library
battle-tested OpenTofu · Helm modules
Leverage CLI
one workflow from your terminal
AWS accounts
- management✓ deployed
- security✓ deployed
- shared✓ deployed
- apps-devstg✓ deployed
- apps-prd✓ deployed
- network✓ deployed
⚡ up to 10× faster — weeks, not months
Your apps in AWS
your apps · SaaS · AI agents — live on AWS
you're ready to build, launch and scale
- 1 Initialize
- 2 Configure
- 3 Orchestrate
1. Create your Leverage AWS Environment project
- Create your AWS Management account
- Create an Admin user for the management account
- Generate programmatic access keys for the Admin user
- Install Leverage CLI
- Create the project directory
- Initialize the Leverage project
pip3 install leverage mkdir leverage-demo-aws cd leverage-demo-aws/ leverage project init [12:28:28.015] INFO No Leverage config directory found in user's home. Creating. [12:28:28.030] INFO No project template found. Cloning template. [12:28:29.052] INFO Finished cloning template. [12:28:29.054] INFO Initializing git repository in project directory. [12:28:29.068] INFO No project configuration file found. Dropping configuration template project.yaml. [12:28:29.070] INFO Project initialization finished.
2. Configure and create your AWS Reference Architecture stack
- Fill in the project.yaml configuration file
- Set Up the bootstrap credentials
- Create the configured project
ls project.yaml vim project.yaml leverage credentials create leverage project create [10:59:20.871] INFO Creating project directory structure. [10:59:20.910] INFO Setting up common base files. [10:59:20.918] INFO Account: Setting up management. [10:59:20.919] INFO Layer: Setting up config. [10:59:20.923] INFO Layer: Setting up base-identities. [10:59:20.944] INFO Layer: Setting up organizations. [10:59:20.953] INFO Layer: Setting up base-tf-backend. [10:59:20.955] INFO Layer: Setting up security-base. [10:59:20.956] INFO Account: Setting up security. ... [10:59:20.981] INFO Account: Setting up shared. ... [10:59:25.052] INFO Finished setting up project.
project.yaml
project_name: leveragedemo short_name: ld primary_region: us-east-1 secondary_region: us-west-2 organization: accounts: - name: management email: leveragedemo-aws@example.com - name: security email: leveragedemo-aws+security@example.com - name: shared email: leveragedemo-aws+shared@example.com organizational_units: - name: security policy: - aws_organizations_policy.default accounts: - security - name: shared policy: - aws_organizations_policy.standard accounts: - shared accounts: management: groups: - name: admins users: - kit.walker policies: - '"arn:aws:iam::aws:policy/AdministratorAccess"' security: groups: - name: devops users: - natasha.romanoff - john.wick policies: - aws_iam_policy.assume_devops_role.arn shared: networks: - cidr_block: "172.18.0.0/20" availability_zones: [a,b] private_subnets_cidr: "172.18.0.0/21" private_subnets: - "172.18.0.0/23" - "172.18.2.0/23" public_subnets_cidr: "172.18.8.0/21" public_subnets: - "172.18.8.0/23" - "172.18.10.0/23"
Terraform directory layout for AWS Accounts
. ├── build.env ├── config │ └── common.tfvars ├── management │ ├── config │ │ ├── account.tfvars │ │ └── backend.tfvars │ ├── global │ │ ├── base-identities │ │ └── organizations │ └── us-east-1 │ ├── base-tf-backend │ └── security-base ├── project.yaml ├── security │ ├── config │ │ ├── account.tfvars │ │ └── backend.tfvars │ ├── global │ │ └── base-identities │ └── us-east-1 │ ├── base-tf-backend │ └── security-base └── shared ├── config │ ├── account.tfvars │ └── backend.tfvars ├── global │ └── base-identities └── us-east-1 ├── base-network ├── base-tf-backend └── security-base
3. Orchestrate your AWS Reference Architecture stack
- Deploy the Management account's layers
- Terraform backend layer
- Identities layer
- Organizations layer
- Security layer
- Update the bootstrap credentials
- Deploy the Security account's layers
- Terraform backend layer
- Identities layer
- Security layer
- Deploy the Shared account's layers
- Terraform backend layer
- Identities layer
- Security layer
- Network layer
cd management/us-east-1/base-tf-backend leverage tofu init leverage tofu apply cd ../../global/base-identities leverage tofu init leverage tofu apply cd ../../organizations leverage tofu init leverage tofu apply ... cd shared/us-east-1/network leverage tofu init leverage tofu apply
Cloud Native App infrastructure in a few weeks
If you implement our Reference Architecture for AWS and the Infra as Code (IaC) Library via Leverage CLI, you will get your entire Cloud Native Application Infra in few weeks.
Best practices baked in the code
Get components based on the best recommended practices mainly following the AWS Well-Architected Framework, granting you ownership to implement, reuse and scale your production workloads faster.
There is no vendor lock-in. You own the solution
Leverage will solve your entire infrastructure and will grant you complete control of the source code, and of course you'll be able to run it without us.
Don't reinvent the wheel
On top of code that is thoroughly documented, tested, and has been proven in production at dozens of other project deployments by our Engineering Support Team.
Why Leverage?
Because all the code and modules are already built, we can get your project up and running on AWS up to 10x faster 🚀 than a consulting company (✅ typically in just a few weeks!).
