The former Porticor support site is now frozen. Please refer to our Intuit page.

The Appliance's Life Cycle

In a production environment, your Porticor appliance will always be on, ensuring you can always access your secured data.

In rare cases you might want to restart the appliance. You can do that using the AWS Management Console (right-click the instance and press Restart), or using the Amazon API. Remember that if you selected to not persist the master key to the virtual disk, you will need to log into the appliance and enter the master key that you saved. Before you do that, the appliance will not allow you to access any data.

In a lab environment or when you are evaluating the product, you might want to stop the appliance for a few hours or days, and then restart it. After all, Amazon bills you per hour of use. We support this usage with our Dynamic DNS feature. Each instant receives a stable address of the form instXXX-projYYY.d.porticor.net. Whenever you stop/start the appliance (but not when you reboot it), Amazon assigns it a new IP address. But as soon as the appliance starts, it updates the DNS system with its new address, so that you can always reach it.

Our dynamic DNS addresses, just like Amazon's ec2-* addresses, translate to different IP addresses depending on whether you resolve the address from inside the EC2 cloud or from the outside. This has the twin advantages of minimizing both network latencies and financial costs when you access the appliance from inside the cloud.

If you close the project, the instance stays around and you may terminate it manually. But the DNS mapping is deleted and the instance is no longer reachable though the stable address.

Limitation: the lifetime (Time To Live, TTL) of the DNS record is 3600 seconds, or 1 hour. This means that if you stop the instance and start it again within an hour, you might see inconsistent behavior. The appliance might appear accessible from within the cloud, but not from the open Internet. The solution is simply to wait for the DNS entry to expire. This may take a bit less or a bit more than an hour, depending on peculiarities of your client machine and even your local router.