This blog post will walk you through using a CloudFormation template that we have provided to help you easily get started using Fli on AWS. We will take 10-15 minutes to download the template, create our CloudFormation in AWS Console, log in to our newly created Fli client and start using Fli.
- An AWS account. You can sign up for free here.
- An SSH client.
sshfrom a Linux or Mac terminal, or something like PuTTY on Windows.
If you would like to view the video, see below.
Overall, you will take the following steps to complete this tutorial:
- Go to the Amazon CloudFormation Console.
- Choose “Upload a template”, and then choose the fli-CloudFormation-Ubuntu16.04 template from this repository.
- Choose your SSH Key and give your Stack a name.
Createto start the Stack.
Download the Pre-Baked CloudFormation Template
Log Into AWS CloudFormation
Create Stack in the top left.
Set Up the Template and Deploy Your Stack
Choose the template from the examples repository.
You will use the
Upload a template to Amazon S3.
Next, then enter a
Stack name and an SSH Key.
Create and wait for your Fli client to boot up.
SSH to Your New Machine and Start Using Fli!
Now that your CloudFormation template is complete, you can find the DNS name of your server in the outputs tab of your CloudFormation stack.
Sync and Push Your New Volumeset and Snapshot!
First, you need a token.
Copy the contents of the authentication token file
token.txt to a file in your new machine.
The authentication token can be created by navigating to your settings in FlockerHub. Also, make sure to place it in
/root/because Fli is set up in this guide to run as a container with the
/root/directory mapped in as a volume. You can change the alias and volume in
.bashrcif you desire.
Once your token is on the machine, use it to configure Fli.
Then, you can
push your data!
Visit your volumesets page to see your newly created volumeset.
Where to Go From Here
Check out our How To Examples for using Fli. There are also videos below for other use cases!
Notes About the Environment
This environment above only provisions a
100GB EBS volume to support Fli. The alloted free amount with new FlockerHub accounts is
5GB. If you wish to use more data than this, email
You can optionally edit the CloudFormation template where the size of the volume is set, in the type
AWS::EC2::Volume where it currently is set for
"Size" : "100",. You may edit this to be larger or as small at
1GB, which is the minimum AWS allows.
Clean Up / Refresh the Environment
To refresh the environment, destroy your stack from the CloudFormation console.
Then, go through the above steps again to create a fresh, new Fli client.
We hope this was useful! We will continue to post new blogs in this series, as well as use cases for Fli and FlockerHub. Stay tuned!