Skip to end of metadata
Go to start of metadata

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

See FileCloud AMI here on AWS Marketplace.


(lightbulb) In the following section, to display more information, click on a topic.


 How Does It Work?

The FileCloud AMI image is built on top of Ubuntu 16.04.

  • 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 you use Amazon S3 for production.
  • We also recommend to take periodic snapshots of your running instance for disaster recovery.

Best Practices for an organization of up to 100 users:

  • Select a t2.medium, m3.medium, or m3.large instance
  • Use Amazon EBS for FileCloud stack (FileCloud application, Apache Webserver, MongoDB Database)
  • Use Amazon S3 for cloud storage to provide a scalable, redundant infrastructure to satisfy any business requirement

What if I'm not using Ubuntu?

Apart from FileCloud AMI on Ubuntu 16.04, we have also pre-built AMIs (BYOL - Bring Your Own License) available on Windows Server 2016 and Windows Server 2012. Please see the AWS marketplace links below,

FileCloud Enterprise File Sharing and Sync (Windows Server 2016)

FileCloud for Windows Server 2012

We have also the following paid AMI's available on AWS Marketplace,

FileCloud Enterprise File Sharing and Sync (20 Users)

FileCloud Enterprise File Sharing and Sync - Windows 2012 R2 -(20 Users)



Launching the FileCloud AMI

  An Amazon Machine Image (AMI) is a master image for the creation of virtual servers, known as Elastic Cloud (EC2 instances) in the Amazon Web Services (AWS) environment.

Machine images are like templates that are configured with:

  • A root volume. This is an operating system and other software.
  • Permissions.  These settings constrain AMIs for instance launches to the appropriate AWS accounts.
  • A block device mapping. This ensures that the correct volumes are attached to the launched instance.

These elements determine the user’s operating environment.


(lightbulb) In the following section, to display more information, click on a step.

To launch the FileCloud AMI:


 1. Complete the Pre-requisites

An AWS Account

An AWS account allows you to:

  • Open the Amazon EC2 console
  • Choose a launch instance
  • Launch your instance


(tick) If you've already signed up for Amazon Web Services (AWS), you can start using Amazon EC2 immediately.


(error) If you haven't signed up for AWS yet, use the following link to get set up to use Amazon EC2.

Setting up with Amazon EC2


(lightbulb) You can read more about Amazon Elastic Compute Cloud on Amazon's site.


 2. Choose an AMI

You can begin the process of launching a Linux instance by using the AWS Management Console.

To launch an instance:

  1. Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/.
  2. From the console dashboard, choose Launch Instance.
  3. The Choose an Amazon Machine Image (AMI) page displays a list of basic configurations, called Amazon Machine Images (AMIs), that serve as templates for your instance.
  4. In the Search bar, type in FileCloud.
  5. Next to the latest version, click Select.

Figure 1. An example of FileCloud listings in AWS Marketplace. (This image does not necessarily show the latest version.)



 3. Choose an Instance Type

When you launch an instance, the instance type that you specify determines the hardware of the host computer used for your instance.

Each instance type offers different capabilities, such as:

  • compute
  • memory
  • storage capabilities

Instance types are grouped in instance families based on these capabilities.

Read more about Amazon's Instance Types

Table 1. General Purpose Instance Types

Instance FamilyCurrent Generation Instance Types
General Purposet2.nano | t2.micro | t2.small | t2.medium | t2.large | t2.xlarge | t2.2xlarge | t3.nano | t3.micro | t3.small | t3.medium | t3.large | t3.xlarge | t3.2xlarge | m4.large | m4.xlarge | m4.2xlarge | m4.4xlarge | m4.10xlarge | m4.16xlarge | m5.large | m5.xlarge | m5.2xlarge | m5.4xlarge | m5.12xlarge | m5.24xlarge | m5d.large | m5d.xlarge | m5d.2xlarge | m5d.4xlarge | m5d.12xlarge | m5d.24xlarge

Read Amazon's complete listing of Available Instance Types


(lightbulb) CodeLathe recommends that you should select an instance type based on:

  • Minimum requirement: t2.medium or t3.medium
  • For best performance: select a type in the m series. For example: m3.medium


To choose the Amazon EC2 Instance type:

  1. On the Choose an Instance Type page, you can select the hardware configuration of your instance.



 4. Configure Instance Details

This step can change depending on the Instance Type you chose:

  • T2 instances, such as t2.micro, must be launched into a VPC.
    • If your AWS account supports EC2-Classic and you do not have a VPC in the selected region, the launch wizard creates a VPC for you and you can continue to the next step.
    • Otherwise, the Review and Launch button is disabled and you must choose Next: Configure Instance Details and follow the directions to select a subnet.

Figure 2. Options for the next step after selecting an instance type.


To configure instance details:

  1. If you selected an Instance Type of t2.medium or t3.medium, then you must enable T2/T3 unlimited. See Figure 3.
  2. When you get to the Configure Security Group step, open up the port 80/443 for web access. See Figure 4.
  3. You might need to open other ports such as 443 (HTTPS), depending on your business requirements.

Figure 3. Configure Instance Details



Figure 4. Configure Security Groups


You can read more about Amazon EC2 Security Groups.

To complete the Final Review and Launch, see the next step: Step 5: Launch the Instance


 5. Launch the Instance

To launch an instance:

  1. When you are ready, click Review and Launch
  2. Next to your instance, select the acknowledgement check box, and then choose Launch Instance.
  3. A confirmation page lets you know that your instance is launching.
  4. Choose View Instances to close the confirmation page and return to the console.
  5. On the Instances screen, you can view the status of the launch. It takes a short time for an instance to launch.
  6. When you launch an instance, its initial state is pending. After the instance starts, its state changes to running and it receives a public DNS name.
  7. If the Public DNS (IPv4) column is hidden, choose Show/Hide Columns (the gear-shaped icon) in the top right corner of the page and then select Public DNS (IPv4).
  8. It can take a few minutes for the instance to be ready so that you can connect to it.
  9. Check that your instance has passed its status checks in the Status Checks column.
  10. Note the Public DNS name to access your FileCloud site.


Figure 5. FileCloud Status in Your AWS dashboard.

Instance started with a public IP

 6. Connect to the Instance

To connect to your instance:

  1. Open a Web browser.
  2. to access the FileCloud admin portal, type in the following URL:
http://<public_dns_name>/ui/admin/index.html

3. To login to the Admin Portal, use the following information:

Default Adminadmin
Default PasswordYour amazon instance ID

After logging in for the first time, you must change the admin password.

4. After logging in, you will see an Admin Attention window. Use this to install the FileCloud License.

light-on (on) To receive a license you must register at the FileCloud license management portal.


 7. Post-installation

After logging in to the Admin Portal, you will see an Admin Attention window. You will also see tags on the right side of the dashboard telling you about what needs to be done after installation.

Complete the following items after you are able to launch and connect to your instance:

Item

Remove the Installation Folder

The default FileCloud instance uses CodeLathe SMTP servers and accounts to send emails.

Change the SMTP servers and accounts to use your own servers for security purposes.


The admin email address is used in all the emails that sent out from the FileCloud System.

Change the admin email to your organization email address.


To show all the installed packages in this instance:

  1. Open a Web browser
  2. Navigate to http://<public_dns_name>/install.
  3. Check the page and familiarize yourself with FileCloud components.

The user name for the underlying Ubuntu OS is 'ubuntu'. Before launching the instance you will be required to create a key pair or you can use your existing key pair.

FileCloud recommends you use S3 for file storage instead of the EBS.

To understand how to setup S3 for FileCloud file storage, read Setting up FileCloud Managed S3 Storage


After you configure the FileCloud storage, follow the site setup instructions to setup the FileCloud site according to your requirements.

Take Periodic snapshots of your running instance for Disaster recovery and as an additional backup for FileCloud database and app.

The ability to install an Enterprise license with components (like Salesforce) is available in FileCloud Server version 18.2 and later.

  • Your AMI image will automatically come with a standard or enterprise license.
  • When you log in to the Admin Portal, you can automatically see the License type (BASE/ENTERPRISE) and also the total number of licenses on the dashboard.


Need to seed data quickly into your new FileCloud installation?

Seeding FileCloud for Amazon S3

  • No labels