Are you sure MySQL and/or ODBC stuff is installed on the FileMaker cloud server?
(I may have missed that info, but a missing driver may make your approach impossible)
2 of 2 people found this helpful
I configured an ODBC Source for SQL Server on one of our FileMaker Cloud instances a few weeks ago. I used the same settings we had on the previous Windows server and it has worked fine with a daily import ever since. No changes were required in the AWS security settings or the FileMaker scripts.
I'm wondering if your SQL Server IP is accessible to the public? Perhaps port 1433 needs to be open on the other server or its firewall.
Thanks Greg! That's what I was hoping to hear. My gut was that it is the network settings on the SQL Server.
I have been told that they opened port 1433 just to the public IP of the FM Cloud server. Do you know if AWS does anything else to the traffic that would make it look like it's coming from a different source than the IP showing in the FM Cloud console?
I’m not aware of anything unusual that AWS would do to the traffic.
I believe the public IP address of the FileMaker Cloud server can change when the server is restarted. If you have the option to specify the host name in the access restriction, it might help to avoid the need to update the IP in the future.
This may not be your case, but SQL Server can use dynamic port instead of static 1433.
Have you tested creating the DSN in your local machine and accessing the SQL server with a local FMP file?
Just to confirm that the problem is on the FM Cloud / AWS side, instead of the SQL server configuration.