From ec7d2b9687aa712f8eb8da32241ff2850a9d37ed Mon Sep 17 00:00:00 2001 From: Ram Balachandran Date: Sun, 25 Oct 2020 01:49:17 +0530 Subject: [PATCH] Update AWS-Deployment-Guide.md (#2354) How to address the dynamic ip changes that are part of AWS or cloud based instances --- cvat/apps/documentation/AWS-Deployment-Guide.md | 1 + 1 file changed, 1 insertion(+) diff --git a/cvat/apps/documentation/AWS-Deployment-Guide.md b/cvat/apps/documentation/AWS-Deployment-Guide.md index d954e06b..7e354f79 100644 --- a/cvat/apps/documentation/AWS-Deployment-Guide.md +++ b/cvat/apps/documentation/AWS-Deployment-Guide.md @@ -18,3 +18,4 @@ services: environment: CVAT_HOST: your-instance.amazonaws.com ``` +In case of problems with using hostname, you can also use the public IPV4 instead of hostname. For AWS or any cloud based machines where the instances need to be terminated or stopped, the public IPV4 and hostname changes with every stop and reboot. To address this efficiently, avoid using spot instances that cannot be stopped, since copying the EBS to an AMI and restarting it throws problems. On the other hand, when a regular instance is stopped and restarted, the new hostname/IPV4 can be used in the `CVAT_HOST` variable in the `docker-compose.override.yml` and the build can happen instantly with CVAT tasks being available through the new IPV4.