Expire an instance

You can set an expiration date to delete unneeded instances. Instance expiration dates can help:

• Improve security by ensuring that VMs are updated.

• Manage your limited virtual resources.

• Ensure new instances are available when required.

• Save your organization money.

You can set expiration dates to 1, 3, 6, or 12 months from the most recent day that all of the instance's nodes are stopped. Set this limit when creating the instance, but you can change it any time before the instance is automatically deleted.

Notes

• Upcoming expirations appear in the AVEVA Integration Studio notification hub. You can also change an instance's expiration period from the notification panel until the expiration day.

• AVEVA Integration Studio emails you a list of instances near their expiration.

• When an instance expires and is deleted, it cannot be recovered. You can only create the instance anew.

• While the instance is running:

  • You cannot delete any of its nodes.

  • Node expiration dates are not visible.

• If you restart a stopped instance, its expiration timer restarts. For example, consider an instance created on January 1 with a 3 month expiration period. It is stopped on February 1, then restarted on April 1 and stopped again on May 1. Its new expiration date is extended to July 31.

To extend or shorten the expiration period of a stopped instance

1. Select Change.

   

   The Change expiration date dialog opens.

   

2. Change the Expiration period to a new value.

3. Select Save.

   Warning: If the new expiration period is shorter than the old one, the instance may be deleted immediately.