We provide free training, feel free to reach us through our training page.
- Single user per server for better security, and organization.
- Unlimited storage for the uploaded data.
- Ability to easily browse pre-existing EFS drives.
Example use cases
Your imagination is your limit, but here are some ideas that are worth considering:
- Ingest vast amounts of data with a predictable price.
- Allow financial institutions to share data with you in a secure manner.
- Browse existing EFS drives that you might have in your account and forget what is contained within them.
Our product has built in resilience to make sure that you don't lose all your data, or lose connectivity by a changing IP. Our CloudFormation provides a quick way to be up and running with all that you need.
Complete feature list
This section lists all the features of this product for easy referencing.
The product itself
- Single user access using password.
- No manual management needed.
- All the configuration is done through the EC2 Instance UserData section.
- Infinite storage using an EFS drive.
If you were to use our CloudFormation file, you’d also get
- An Alarm to check for CPU Bursts.
- An Alarm to check for CPU Load.
- An Alarm to check for Disk usage.
- An Alarm to auto recover the instance if it gets terminated suddenly by AWS due to hardware failure.
- An Alarm for EC2 Instance termination protection.
- A SNS Topic to receive notifications from the above alarms.
We provide a CloudFormation file. Before you click the orange button to deploy the stack, make sure to subscribe first to the product on the AWS Marketplace, and if you want to check the CloudFormation prior to deployment, follow this link.
What will be deployed
- 1x EC2 instance with 0x4447 custom AMI:
- 1x IAM Role.
- 1x IAM Policy.
- 1x Security Group.
- 1x Instance profile.
- 1x Elastic IP.
- 1x Elastic IP Association.
- 4x CloudWatch Alarms:
- CPU Burst.
- CPU Load.
- Disk Usage.
- EC2 Instance Recovery.
- 1x SNS Topic:
- 1x SNS Policy.
- 1x Topic Subscription.
- 1x CloudWatch Dashboard for instance overview,
- 1x EFS drive:
- 1x Mount target.
- 1x Security group.
- 1x Backup:
- 1x Plan.
- 1x Role.
- 1x Selection.
- 1x Vault.
The First Boot
The boot time of our product will be slower than if you started an instance from a clean AMI, this is due to our custom code that needs to be executed in order to prepare the product for you. This process can take a few minutes longer than usual.
Connecting to the Server
If you need to connect to the server: get it's IP, connect to the instance over SSH with the username
ec2-user, while using the private key you selected at deployment time. If successfully connected, you should be greeted with a custom MOTD detailing the product information.
Test the setup
Before you go into production, make sure to test the product; not because we don't believe it, but to make sure that you get used to how it works.
Below we give you a list of potential ideas to consider regarding security, but this list is not exhaustive – it is just a good starting point.
- Limit access to the server to just a fixed IP.
- Don't give root access to anyone but yourself.
Backup Your Data
Make sure you regularly backup your drive(s). One simple solution would be to use AWS backup.
How to change the instance type
If you need more memory and CPU capacity, you can change your instance type to a bigger one. To do so, follow these instructions:
- Go to the CloudFormation console
- Click on the stack that you want to update.
- Click the
- Keep the default selection and click
- On the new
Parameterspage, change the instance type from the drop down.
Nexttill the end.
Wait for the stack to finish updating.
These are some of the common solutions to problems you may run into:
Not authorized for images
My CloudFormation stack failed with the following error
API: ec2:RunInstances Not authorized for images:... in the Event tab.
You have to accept the subscription from the AWS Marketplace first, before you use our CloudFormation file.
The product is misbehaving
I did follow all the instructions from the documentation.
Check if the values entered in the UserData reached the instance itself.
sudo cat /var/lib/cloud/instance/user-data.txt
UserData seams ok
The UserData reached the instance, and yet the product is not acting as it should.
Use the following command to see if there were any errors during the boot process.
sudo cat /var/log/messages | grep 0x4447
Issue with EFS backup restoration
I did launch the product by using an EFS drive restored from a backup and the old OpenVPN profile don’t work.
You have to reorganize the EFS drive. By design AWS restores the data (even on a new and empty drive) in special folders called:
aws-backup-restore_timestamp-of-restore. Meaning they do not recreate the original folder structure. Check how AWS restores EFS Backups to learn more.
Before using the restored drive, you can reorganize it using our SFTP Server - Single User Setup product.