![]() ![]() User ExperienceĪfter logging into AppStream, you land on the catalog screen which displays icons for each streaming application defined for your image. Note that AppStream sessions can only be run on browsers with full HTML 5 support, including Google Chrome, Mozilla Firefox, Microsoft Internet Explorer, and Microsoft Edge. This URL is the same for everyone in your user pool, so it’s easy to keep track of, and while the URL itself is a bit ugly, you can use a URL shortening service like Bitly to create a custom link that’s easy to remember. Each user gets a welcome email and a link to your AppStream URL. Through the AppStream user pool, you add your users and assign them to your stack. With your base image, fleet, and stack in place, it’s time to get your users connected. In the AppStream image builder, use the Image Assistant to select the applications you want to make available to your streaming users. This has several implications that we’ll get into shortly. Note that currently the only OS platform available in AppStream that is supported by FileMaker Pro is Windows Server 20xx. Finally, you create a stack, which controls access to your fleet. ![]() Fleet options include AWS instance type (to meet your particular performance requirements), capacity (minimum and maximum number of running instances), and scaling policies (to dynamically create or reduce available instances based on user demand). You then configure a fleet, or a set of instances running this image. Using the AppStream image builder, you create an image that contains the application(s) you want to make available for streaming, such as FileMaker Pro. Do bear in mind that there are costs associated with most AppStream resources, so any testing you want to do will incur some cost. If you’re already running a FileMaker Cloud server, or a regular FileMaker Server in AWS, you’ll already have this set up, but if not, it’s pretty straightforward. How it works AWS accountĪppStream runs in AWS, so if you’re interested in setting up an AppStream environment, the first thing you’ll need is an AWS account. We’ll start with an overview of the AppStream architecture and then dive into specifics on how running FileMaker Pro inside AppStream differs from the standard FileMaker experience. Since this was our first time working with the service, we thought we’d share our findings. Skeleton Key recently had a project that involved an AppStream deployment. These factors make AppStream worthy of consideration for anyone hosting their FileMaker solution(s) in AWS. You also get the benefit of elastic pricing with AWS you only pay running instance fees when there are active user sessions. Moreover, since AppStream applications are delivered through a web browser, users don’t actually have to install FileMaker Pro on their local machines. Because AppStream instances live in AWS, you can configure a fleet to run in the same AWS region as your FileMaker server, effectively putting them in the same local network and giving you the speed of a LAN connection. Amazon’s AppStream 2.0 is an application streaming service that allows you to stream desktop applications from AWS to a user through a web browser. There are ways to optimize FileMaker for WAN performance, but if your database is sufficiently complicated, performance over the WAN simply might not be workable. Chief among these is performance: If you’re connecting from your office to a FileMaker database hosted in AWS, you’re doing so over the WAN. Even with all these benefits, running FileMaker Server in AWS does have its drawbacks. The fact that you can provision a FileMaker Cloud server and not have to worry about hardware failure or replacement, disaster recovery, or managing the server OS, makes the prospect of running a local server machine much less attractive (though there might still be valid reasons to do so). Reliability, availability, redundancy, scalability, security, and cost optimization are all reasons to consider employing cloud services for your computing infrastructure needs. The benefits of cloud computing are many. And in late 2016, FileMaker unveiled FileMaker Cloud, a new AWS-based service that allows you to deploy a FileMaker server without having to spend the time and resources normally required to build out and manage a server machine. FileMaker Server can be run in the cloud through a cloud services provider such as Amazon Web Services (AWS) or Microsoft Azure. ![]() ![]() Over the past several years, FileMaker has entered the cloud computing landscape. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |