![]() ![]() Within a minute or so you’ll be looking at your brand new Windows Server 2012… Open the RDP file you downloaded, enter your password as above and… Finally! Our server in the cloud starts its initial boot up. ![]() Your password will be displayed – take note of this! ![]() We decided to open the key pair file using Notepad, copy the contents and paste into the empty box. Click Get Password and locate the key pair file. Now we have to get the password for this RDP connection using the key pair file we downloaded in step 3 of the previous blog post. In the window that appears you can download the RDP settings – it’s worthwhile doing this as it will save having to enter all the required information into a blank RDP file. If the newly created Instance is marked as running then ensure it’s selected and click Connect. If you’re not already looking at your Instance, then in the EC2 dashboard click Instances in the vertical menu. We’ll be using a PC for our demo but Mac users can download the Remote Desktop application from here.Īmazon advises that if you’re a Mac user and have trouble with that download, try the one from the App Store instead. Windows machines come with an RDP client installed. But wait, where is it, how do you see it, aren’t we supposed to install FMS? Administering your Instance is done via Remote Desktop. Ours was up and running pretty much straightaway.Īwesome, so our Instance (or virtual server) is now up and running. Click the blue View Instances button to check on the status. Your Instance will now be created and start launching. Now click Launch and select the key pair you made in Step 3 of the previous blog post. Still, for our testing purposes 30GB is sufficient.Ĭlick Next: Tag Instance – we’re not going to concern ourselves with this for now.Ĭlick Next: Configure Security Group – we’ll be selecting the existing security group we created in step 5 of the previous blog post. Sounds like a reasonable amount, but the Windows Server 2012 Standard Edition (64-bit) operating system is going to consume more than 20GB of that. Note some options will result in a charge.Ĭlick Next: Add Storage – Free Tier accounts get 30GB included and it should default to this value. We’ll be selecting the only Free Tier option, which is the t2.micro Instance.Ĭlick Next: Configure Instance Details – we chose to leave these settings at the default values. So, we’re going to opt for Windows Server 2012 Standard Edition (64-bit) – note not the R2 version.Īfter selecting our server operating system, we’re presented with a list of Instance Types – essentially how powerful a server do you want to run. 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 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |