And FMS is going to narrow down the field further for us.Īs of the date of this post, the official line is that FileMaker Server 13 is supported on Windows Server 2012 Standard Edition (64-bit) and Windows Server 2008 (Standard & Enterprise) R2 SP1 (64-bit). There’s still quite a number to choose from, but as above we know we’re limited to the Windows Server versions so we can ignore the rest. This essentially boils down to what server operating system do we want – to reduce the list a bit and, because we’re just checking out AWS using their Free Tier option, to ensure we don’t get charged by selecting something by mistake, click the check box on the left that says Free Tier Only. Then click on the big blue button that says Launch Instance.Ī plethora of options for our Amazon Machine Image (AMI) awaits us. So, head over to the AWS Console and click on EC2 under the Compute section.īe sure that your region selected (in the top right of the screen) is the same as the one we used in our previous post to create the key pair and security group. FMS will not run on Linux or any other offerings from AWS. To run FMS we need to use a Windows Instance. So, now that we have all that taken care of, without further ado, let’s launch and connect to our server in the sky… Step 1: Launch a Windows Instance In our previous blog post, we did all that was necessary on the AWS side to set up groups, users and security prior to being able to launch our server Instance using AWS’ Free Tier option – a free cloud server as long as we stick within the Free Tier guidelines. The second part of our FileMaker Server (FMS) on Amazon Web Services (AWS) series focuses on launching our server Instance and getting FMS installed and up and running. Launching an Instance and Installing FileMaker Server
0 kommentar(er)
