If you have a FileMaker server that you want to ensure high availability, Amazon’s AWS Route 53 service has some functionality that you’ll want to know about. For this post, I’m going to show how you can set up monitoring and alarms for the XML interface on FileMaker Server.
As y’all probably know by now, FileMaker 17 has been released, including the first production edition of FileMaker Server’s Data API. This API was originally released with FileMaker 16, but only as a “beta”, expiring September 2018. As you might expect, the FileMaker 17 Data API introduces significant changes. This means that any applications written against the FM 16 Data API need to be refactored for compatibility with FileMaker 17. And that’s the work we’re here to do!
Continue reading “Using REST and cURL with FileMaker 17’s Data API”
In addition to the more typical external authentication methods, FileMaker supports client authentication using OAuth accounts from Google, Amazon, and Microsoft. In this instance, I needed to set up a FileMaker Cloud server to use a company’s directory accounts, which were hosted at Azure. In order to set this up I hit a couple of minor complications, which I’m going to cover here.
Recently, I needed to revert a database file hosted on a FileMaker Cloud 16 server. Due to a problem I was having with the Download function however I had to take a different route from the usual method.
If you purchased your FileMaker Cloud server with user connection licenses, you may well wonder “Where do I get the client software to connect to my server?”.
A fair chance you’ll initially land on the screen below. This seems relevant, but there’s still no indication here how you can download the FileMaker Pro clients you have licenses for.
Here we’ll list the steps you’ll need to enable authentication using Amazon accounts with FileMaker Cloud.
If you’ll be having more than a few different people logging in to the Admin Console of your FileMaker Cloud server, it’s generally good practive to avoid having everyone use the same credentials. By enablling an additional authentication mechanism, you can easily add or remove administrative access to a server, and user’s get to use their own own credentials.
If you’ve installed the FileMaker Pro client using a “For Teams” license, or as part of your FileMaker Cloud server usage, you may see a new dialog in FileMaker Pro.
In version 15, FileMaker has introduced a a new user-based licensing model. With FileMaker for Teams and FileMaker Cloud, a license allows use of Server and Client software based on the number of subscribed users.
We’ll discuss how you can use a one or three year reserved instance for your FileMaker Cloud instance. This can shave 30% or more off your AWS instance charges.
When you spin up any new AWS based VM you will by default be using an hourly instance. This can be perfect for short-term usage or where your usage may fluctuate frequently.
If you had started a FileMaker Cloud deployment, but lost access, accidentally closed the page, or had some other issue that caused the process to stop, you may be able to restart your deployment easily by going to the AWS Marketplace and checking your history.