Setting Up

This page provides instructions for creating a Datomic Cloud System via the AWS Marketplace template. If you are upgrading or managing templates manually, see first upgrade.

If you are setting up a Datomic Cloud System for production or doing exploratory work for such a purpose then consider creating separate storage and compute stacks. This brings benefits in stack management, upgrading and access control.


Before you can run Datomic Cloud, you must have:

  1. An AWS Account That Only Supports EC2-VPC
  2. An EC2 Key Pair

An AWS Account That Only Supports EC2-VPC

To run Datomic Cloud, currently you must have an AWS Account that supports only EC2-VPC in the region in which Datomic Cloud runs. If you created your AWS Account on or after Dec 4, 2013, you should have a properly configured account that only supports EC2-VPC.

If you created your AWS Account prior to Dec 4, 2013, or if you are unsure when you created your account, you should verify that you have an EC2-VPC only region prior to going through the getting started instructions.

Create an EC2 Key Pair

If you do not already have an EC2 Key Pair, create one from the EC2 Key Pair console

  1. Click the Create Key Pair button.
  2. Enter a name for your new Key Pair. Take note of this name–You will need it when you create your system.
  3. Press the Create button.
  4. Save the downloaded certificate (.pem) file for later use.
  5. From a terminal window run:

    chmod 400 <path-to-your-pem-file>

    Replacing <path-to-your-pem-file> with the path to the .pem file you downloaded in step 4.

Create Stack

Subscribe to Datomic

Follow these steps from the Datomic listing on AWS Marketplace:

  1. Click the Continue to Subscribe button:


  2. On the next page, read the EULA and if you agree then click the Accept Terms button to subscribe.


  3. Wait up to 30 minutes until your subscription is confirmed with a message in the green status bar:


  4. Click the Continue to Configuration Button.
  5. Choose a Fulfillment Option. First-time users should choose the "Solo" topology.
  6. Choose a the most recent version and an AWS Region from the drop down menus.
  7. Click the Continue to Launch button.
  8. Select "Launch CloudFormation" from the the drop down menu and click the Launch button.

"Select Template" Screen

  1. Under "Choose a Template", select the "Specify an Amazon S3 template URL" option. The URL field will be pre-populated for you.
  2. Click the Next button

"Specify Details" Screen

Fill in the template's parameter values as specified below.

Note: Stack Name and Application Name cannot be changed later. See planning your system for guidance.

Stack Name
Choose a name for your system. Use only lowercase letters, numbers, and hyphens. ASCII characters only. Your system name gets concatenated in various contexts and so should be kept short, e.g. fewer than 24 characters.
Reuse existing storage
Set this to "False".
Start bastion?
Set this to "Yes" so that the template will start a bastion for developer internet access. You will need to authorize access to the bastion instance in a later step.
AWS EC2 Key Pair
The key pair to assign to compute nodes. Select a key pair for ssh access to nodes and the bastion host.
Application Name
Leave this blank to create an application with the same name as the system.
Environment Map
Ion environment map. Set to {:env :dev} for now.
Preload Database
All compute group instances will load this database when they start.

This CloudFormation Template creates a VPC in which to run Datomic Cloud. Configure the settings for the VPC in the VPC Configuration section. See the AWS VPC Guide for details on specifying the CIDR blocks. Unless you know you need to change the CIDR block settings, you should accept the default configuration.

VPC CIDR block
The CIDR block to assign to the VPC. Accept the defaults.
First, Second, and Third CIDR Blocks.
Datomic will configure three subnets in the VPC. These three CIDR Blocks must be subsets of the VPC CIDR Block, and they must not overlap with each other. Accept the defaults.
Existing IAM managed policy for node
Optional. The name of an IAM managed policy to add to the role that group nodes run with. Leave blank.

Click the Next button.

"Options" Screen

  1. Leave the default settings
  2. Click the Next button.

"Review" Screen

  1. Under "Capabilities", click the checkbox stating "I acknowledge that AWS CloudFormation might create IAM resources with custom names." You may need to scroll down.


  2. Click the checkbox stating "I acknowledge that AWS CloudFormation might require the following capability: CAPABILITY_AUTO_EXPAND"
  3. Click "Create" to launch the stack.

Verify System

Your Datomic system will have a Cloudwatch dashboard named datomic-\((System)-\)(Region). Open the CloudWatch dashboards and refresh the window until your dashboard appears. This can take several minutes.

If your dashboard does not appear after 25 minutes, check for a possible CloudFormation failure.

Once your dashboard is visible, click on it and find the "Alerts, Events" widget. If this shows zero Alerts and nonzero Events, your system is ready to go.

Next: Now you are ready to Configure User Access.