In each one of these cases, the old EC2 instance is terminated and a brand new EC2 instance is generated (and therefore a brand new Instance ID). There are four (4) scenarios under which your FileMaker Cloud Instance ID will change: 1) an EC2 upgrade/downgrade, 2) a Storage upgrade, 3) a server "Refresh", or 4) Restoring from a backup. Instance IDs: The CLI commands to start and stop FileMaker Cloud all point to your servers by their AWS Instance ID. If you currently point to hosted files on AWS servers by host IP address, consider switching to using DNS names. The only way to avoid this is by using static IP addressing, known as Elastic IP addressing in AWS terms, which at the moment FileMaker Cloud does not officially support. IP Addresses: With or without Data Pipeline, stopping and starting FileMaker Cloud instances will cause their IP address to change each time they start up.
0 Comments
Leave a Reply. |