I can't help you, but if you are able to pin down some FileMaker people at DevCon, please tell them we have the same issue using a hosting service. Ever since the 12.0.4 upgrade, our interactive containers broke and we can't get them operational.
Thanks Mike for that info. I contacted someone from FileMaker that I met at last years DevCon to see if something happened during the upgrade. I will let you know what the response is.
When you check "By reference", FileMaker is not storing the PDF on the server. It is only referencing it on the local drive. Re-insert the PDF and uncheck "By reference" to store it on the server.
Visionary of Value
FileMaker 12 Certified Developer
FileMaker 12 Authorized Trainer
Thanks Kirk for the reply. I only did that to test to see if the interactive containers actually worked. Perhaps, I wasn't clear in my initial post. I also tested with it unchecked and the .pdf if storing on the EBS root volume to the instance as it should. Unfortunately, the issue is seeing the document in the interactive container field. It is looking for the document on the server, as it should, but it displays a blank container field.
I contacted FileMaker to ask if there was a conflict between AWS and FileMaker. They are testing it and will get back to me.
Are you able to open the admin-console remotely from the machine FileMaker Pro is on (http://<server-name>:16000/)? This will help to check if port 16000 is truly open. You mentioned you created an inbound rule for port 16000. If you haven't already, you'll need to make an outbound rule for 16000.
Yes. I tested that this morning and I can open it.
I finally was able to view my interactive container fields hosted on AWS.
You might want to try and enabling SSL and disabling progressive downloads on the Admin Console. This is how I got mine to work. The difference is instead of streaming through port 16000 or 16001, it streams the content through port 5003.
You have to restart the server database in order for the change to take affect.