top of page
Leverage

Don't reinventthe wheel.AUTOMATE.

binbash-for-startups.png

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.

Reference Architecture

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.

AWS
Infrastructure as Code

Infrastructure as Code Library

Enable you to safely and predictably create, change, and improve your cloud infrastructure 100% as code.

Leverage CLI

Leverage CLI

Get automated deployment, scaling, and management of your containerized applications with Kubernetes.

Anchor 1
Leverage Path

1. Create your Leverage AWS Environment project

  1. Create your AWS Management account

  2. Create an Admin user for the management account

  3. Generate programmatic access keys for the Admin user

  4. Install Leverage CLI

  5. Create the project directory

  6. Initialize the Leverage project

macbook

$ 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.

ā€‹

Anchor 1

2. Configure and create your AWS 
Reference Architecture
 stack

  1. Fill in the project.yaml configuration file

  2. Set Up the bootstrap credentials

  3. Create the configured project

Leverage Setup

$ 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.

ā€‹

Leverage Setup

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

  1. Deploy the Management account's layers

    • ā€‹Terraform backend layer

    • Identities layer

    • Organizations layer

    • Security layer

  2. ā€‹Update the bootstrap credentials

  3. ā€‹Deploy the Security account's layers

    • ā€‹Terraform backend layer

    • Identities layer

    • Security layer

  4. Deploy the Shared account's layers

    • ā€‹Terraform backend layer

    • Identities layer

    • Security layer

    • Network layer

Leverage Reference Architecture

$ cd management/us-east-1/base-tf-backend

$ leverage terraform init

$ leverage terraform apply

ā€‹

cd ../../global/base-identities

$ leverage terraform init

$ leverage terraform apply

ā€‹

cd ../../organizations

$ leverage terraform init

$ leverage terraform apply

...

cd shared/us-east-1/network

$ leverage terraform init

$ leverage terraform apply

AWS EKS

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.

AWS Well-Architected

Best practices baked in the code

Get components based on the best recommended practices mainly following the AWS Well-Archiected Framework, granting you ownership to implement, reuse and scale your production workloads faster.

Open Source

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.

AWS Organization

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!).

binbash Leverage
bottom of page