Skip to end of metadata
Go to start of metadata

FileCloud Public AMI (Amazon Machine Image) is currently available in Amazon AWS Marketplace.  See Link.

Using FileCloud's AMI,  one can host their own file share sync and mobile access solution for their organization is less than 10 minutes. The FileCloud AMI image is built on top of Ubuntu 14.04 Trusty OS and the size of the image is 20 GB. FileCloud stores the meta data and file share information in MongoDB database which is already pre-configured in the FileCloud AMI. The actual files can be stored in EBS or S3. For scalability and redundancy, we recommend to use Amazon S3 for production. We also recommend to take periodic snapshots of your running instance for disaster recovery.

For a 100 users organization, a t2.medium or m3.medium  or m3.large instance is good enough. Using Amazon EBS for FileCloud stack (FileCloud application, Apache Webserver, MongoDB Database) and Amazon S3 for cloud storage provides a scalable, redundant infrastructure that will satisfy any stringent business requirements. Since you only pay for the FileCloud licenses ($25/user/year) and Amazon infrastructure  the cost savings is very significant compared to any other public cloud file sharing app like Dropbox or Box.net.

In a normal usage scenario, we expect FileCloud + AWS Infrastructure  will cost $40/user/year compared to $150/user/year for Dropbox or Box.net. In addition, with FileCloud you have complete control over the app, branding, domain naming and access permissions. Using FileCloud + AWS, one can approximately save over $10,000 (assumption 100 users) when compared to Dropbox for business or Box.net.


Steps To Launch FileCloud AMI

  1. Login to AWS management console and Click EC2 (Virtual Servers in the Cloud)

Amazon account screen showing all available services

2. Click Launch Instance

Launch a new AMI instance

3. Search FileCloud AMI in community AMIs or AWS marketplace.  Choose the latest version. We recommend the AWS marketplace for the latest version.

Search for FileCloud AMI

4.  Choose the desired Amazon EC2 Instance type. We recommend atleast t2.medium.

Select EC2 type

5.  Configure the security group to open up the port 80 for web access.

Note

You might need to open other ports such as 443 (HTTPS), depending on your business requirements.

6. Complete the Final Review and launch the instance.

Review and launch the instance

7.  You can see now your FileCloud is running in your AWS dashboard.  Please note the Public DNS name to access your FileCloud.

Instance started with a public IP

8. Type 'http://<public_dns_name>/ui/admin/index.html' in your browser to access the FileCloud admin portal.   If the Webpage fails to load, please verify port 80 is open as mentioned above in Step 5.

Default Adminadmin
Default PasswordYour amazon instance ID
NotePlease change the admin password upon first login.

9. Once you logged into the admin portal, please install the FileCloud License.
Please register at our license management portal (https://portal.getfilecloud.com/ui/user/index.html?mode=register) to get trial licenses.

 

  1. The user name for the underlying Ubuntu trusty OS is 'ubuntu'. Before launching the instance you will be required to create a key pair or you can use your existing key pair.
  2. If you go to 'http://<public_dns_name>/install' , the page will show all the installed packages in this instance. Check the page and familiarize yourself with FileCloud components. Before going production move the install folder to somewhere else.
  3. We recommend you to use S3 for file storage instead of the EBS. Please check this page (Setting up FileCloud Managed S3 Storage) to know how to setup S3 for FileCloud file storage.
  4. Take Periodic snapshots of your running instance for Disaster recovery and as an additional backup for FileCloud database and app.


  • No labels