Two things first:

1. Hostname must be the fully qualified name, inlcuding the domain and TLD, e.g. http://myfmeserver.mycompany.com/fmerest/
2. There must be a DNS entry for the hostname myfmeserver.mycompany.com and the server must be part of the DMZ for it to be reachable externally

These things must usually be handled by the IT department.

On a side note, I would strongly recommend using https if this is an externally visible server. See http://docs.safe.com/fme/html/FME_Server_Documentation/AdminGuide/configuring_for_https.htm

Thank you david.

Any tips for accessing throughout REST-API a cloud hosted server? We are thinking to move the server to AWS.

Thank you!

Jorge

Shouldn't be a problem in itself, as long as the endpoints have been made accessible in the AWS firewall. I would strongly recommend configuring SSL (https) if the server is reachable from the outside.

David.,

Can i assume the same applies when configuring an "Amazon SNS topic notified" trigguer? When I am configuring the subscription, I am not getting what the 'endpoint' should be? the FME guide said> "Enter the web address of the FME Server Amazon SNS Publisher " . https://docs.safe.com/fme/html/FME_Server_Documentation/ReferenceManual/Amazon_SNS_Publisher_Configure_AWS_Subscription.htm

In principle, it's the same thing. But AWS has some added functionality that can both help and complicate matters. You may want to look at the documentation for SNS from AWS as well: https://aws.amazon.com/sns/resources/

Safe has also published a sample workspace using SNS that my be helpful: https://hub.safe.com/publishers/safe-lab/templates/amazon-sns-example

Cool, I made it through SQS (SNS to transmit the message) and it works ok! Thank you