Getting Started - Deploying MapR in AWS

Several options are available for getting started with MapR in AWS, with varying levels of effort and customizability

Deployment Option Good for Users or Organizations Who Are/Have Simplicity Customizability Licensing
AWS Marketplace New to AWS or MapR
Full Access to AWS Account
Need Hourly Billing for Enterprise MapR Features
Highest Lowest Integrated or Bring-Your-Own
Customized Pre-defined Example Extensive Experience with AWS or MapR
Complex AWS Security Policy and Roles
Low High Bring-Your-Own
Manual Deployment Learning How MapR Deploys on AWS
Using Other Automation Tools Like Terraform or Ansible
Medium High Bring-Your-Own
Pre-defined Example Some Experience with AWS or MapR
Some Limits to AWS Access
High Medium Bring-Your-Own

About Deployment

Installation Architecture

There are two stages to deploying MapR in AWS:

  1. Deploying the AWS cloud environment, including networks, roles, and keypairs.
  2. Deploying the MapR software.

These stages are kept separated in order to support the myriad ways in which users or organizations want to customize their cloud environment, or the way they deploy software. Many other software vendors try to control the entire cloud lifecycle, including provisioning of networks, to the dismay of customers with organizational policies that restrict network configuration, naming, and security policies.

For the first stage, deploying the AWS cloud environment, MapR provides pre-built utilities including the AWS Marketplace and pre-defined example CloudFormation templates. Because every company and environment is different, MapR also supports fully customized deployments, including modification of example CloudFormation templates or manually provisioning a cloud environment from the AWS console. Power users can also automate cloud provisioning steps using another automation framework like Ansible or Terraform by following the steps listed in the manual deployment.

Once a cloud environment is deployed, the MapR Installer has an AWS plugin for deploying the AWS instances that will become the MapR nodes. Letting the MapR Installer control instance provisioning allows the MapR software to control the full lifecycle of the cluster, expanding the size on-demand, and in the future cycling through failed or underperforming instances. The MapR installer links to AWS Auto-Scaling groups, which serve as templates for instance configuration, allowing users to create instances using any available configuration and features that AWS supports.

The architecture diagram below shows the separation of duties between what the MapR-provided CloudFormation Templates or AWS Marketplace entires perform, and what the MapR Installer Performs.