Typically, you buy an SSL certificate for a server from a SSL vendor. However, some companies may decide that they want to issue their own SSL certificates. Often this is because the domain is only used internally, and most vendors don’t easily allow (if at all) the signing of server certificates for non-public domains. Additionally, issuing your own certificates can remove complications caused by the certificate verification process used by most vendors, and there are no fees needed for each certificate.
Apple’s macOS Server 5.x has a rather different Apache configuration compared to the core macOS setup or those used in previous versions of Server. In particular, an instance of Apache is used as a proxy to any ‘backend’ copies of Apache. Here’s how to work around this…
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.
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.
Although setting up your AWS account and creating a new FileMaker Cloud instance is a fairly easy process, it does have dozens of steps, and a few places where you could easily take a wrong turn. On this post we’ll go through each step in the configuration of your Amazon AWS account and requesting your first server.
Continue reading “Step-by-step for FileMaker Cloud”
Intro: SSL Basics
SSL certificates are a very common way to secure client/server network connections, and the FileMaker platform has made use of them for many years. Starting with version 15 however, FileMaker introduced a number of security changes, in handling SSL and certificates, on both the server and the clients. But where do they come into play, and how might this affect your deployments?
Recently we’ve been thinking about how we can better monitor the collection of systems that we manage. These can be client servers with very diverse configurations, access, or functions. Additionally, we have our own array of systems, almost as diverse as our clients’.
As an aid to improving the security of your server, Fail2ban is an open source component that checks for signs of abusive activity in your logs, and when these are detected, blocks an address (or possibly a subnet) for a given period of time. In May of ’13 I blogged about how to set up Fail2ban rules to check the FileMaker Server event logs (http://buzz.beezwax.net/mVfrR7).