AWS instance types determine the particular configuration of the CPU, memory and networking capacity of the host computer used for your instances. You may find that you need to change your instance type at some point, such as if your instances are being overused or underused, in which case you would want to change the size accordingly. This article describes how to change your running On Demand instance type to a different type (for example, from m1.large to c3.xlarge).
Any data on the ephemeral storage of your instances will be lost when stopping an instance. Additionally, note that starting or stopping an instance can cause the administrator password in your application's web UI to reset to the instance ID.
- Ensure that all data is backed up.
- Stop your instance by clicking Actions > Instance State > Stop
- Once your instance has stopped, change the instance type by clicking Actions > Instance Settings > Change Instance Type
- From the drop down menu, select the instance type that you would like to change to.
- Start your instance by clicking Actions >Instance State > Start
- If using an Elastic IP, reassociate it to your instance by doing the following:
a) Use the AWS interface to reassign the Elastic to your instance.
b) Navigate to AWS Elastic IP menu.
c) Select the IP address and associate address with your instance.
If you are not using an Elastic IP, update the <server_name> section in /opt/aspera/etc/aspera.conf with the host name or Public DNS of the new instance.
- If your product has Shares or Console enabled, ensure that your web UI appears in a browser.
Note: It may take several minutes for your web UI to be available online.
- Your instance type has been changed. Please do a test transfer to ensure that everything is working as expected.