Using the demo file: In order to run the examples, you will need to have an AWS account. You will also need to have an AWS access key and secret key corresponding to a user which has permission to use the services in the demo. If you're just getting started with AWS, the easiest way to do this is to attach the administrator policy to the user, which allows that user to do anything. You should only do this for trying out the demonstrations - for actual deployment, you should create the most restrictive policy possible. Read the IAM documentation for details on how to configure AWS policies. Once you have the proper credentials, open the AWS functions.fmp12 file, switch to the AWS settings layout, and paste your AWS credentials. Then select the region that you want to use. I've tested all of the demos in the us-east-1 Virginia region. Some services, such as the new transcribe service, may not work in certain AWS regions. When following the demo-specific notes below, make sure that you do any necessary AWS configuration in the same region that you select in the FileMaker database. To run each specific demo, here are the setup steps you'll need to take: * For Simple Queue Service, you'll need to create a queue and copy the URL into the 'Queue URL' field. To do that, go to https://console.aws.amazon.com/sqs/ and click the 'Create new Queue' button. To get the URL, select that queue in the list and then copy the URL field from the detail section at the bottom of the console. * For Kinesis firehose, you'll need to set up a new data firehose delivery stream at https://console.aws.amazon.com/firehose/. Once that is done, just put the name of the delivery stream into the FileMaker database, and you should be ready to go. * For S3, you'll need to create a new S3 bucket at https://console.aws.amazon.com/s3, and copy and paste its name into the 'Bucket' field in the demo. Enter any arbitrary path you want into the 'Path' field, then insert some file into the 'File' container field, then click the upload button. After the upload completes, try deleting the container contents and then click the download button, which should download the file back into the container field. * For transcribe, you'll need to first upload some audio file (an m4a audio file is what I've tested with, but mp3 and wav should work as well). You can use the S3 example layout to accomplish this. Use the AWS console to find out the full URL for the uploaded audio file, then paste that into the MediaFileUrl field. Use 'en-US' for the language code (Spanish is supported as well, but you'll need to find the appropriate code for that) and 'mp4' for the MediaFormat. Click the 'Start transcribing' button to ask AWS to transcribe the audio; this typically takes 100-200 seconds for short audio clips. Click the 'Get result' after waiting for a bit; it will either download the resulting transcription or tell you it's still inprogress. * There is no setup required for translation; just type in text, select the languages, and click the 'translate' button.