You can also only restore the whole set of files, not individual files.

To its credit, backups are very efficient and fast since they use AWS snapshots and not the file-copy mechanism that regular FileMaker Server uses.

The backup schedule is fixed and runs every 20 minutes you cannot add your own backup schedules.

The PHP API and the XML API are not available, but WebDirect is.

Unlike the on-premise version of FileMaker Server you cannot split the deployment over a database and a web-server machine it is strictly a one-machine deployment.

You will see an indication of the expected monthly cost both in the admin console where you can switch between instance types and in the marketplace when you choose your initial instance size.

Amazon AWS itself has a lot more instance types but FileMaker has made a good move here to simplify the choices.The FileMaker Server that powers FileMaker Cloud runs on CentOS Linux and in our testing is very efficient when it comes to how much resources it requires. You can select from eight different instance types that range from one processor with 2GB of RAM all the way to 40 processors and 160GB of RAM.You can pick a FileMaker Cloud instance in two regions: US East and US West, the closer the instance is to where your users are, the more responsive your FileMaker solution will be.Some important things to note and consider about FileMaker Cloud and where it differs from the regular FileMaker Server:

That admin console for FileMaker Cloud is unlike the one for the traditional on-premise version of FileMaker Server as you can see from the screenshot below it is meant to be simple and intuitive to use. All of the interaction with your FileMaker Cloud is through the admin console.

Filemaker pro server 15 ports