Starting with LogLogic LMI 6.1.0 the LMI EVA is supported on AWS. The hostname is set by AWS and defined by AWS as containing the private IP of the virtual machine. The private IP is not intended to change for the VM when running on AWS which means the hostname is not expected to change once it's been set. However if the user changes the hostname using the LMI GUI this will break the networking scripts and subsequently the network stack.

Every LogLogic LMI deployed on AWS will have it's own unique hostname, and this can be viewed in the  Administration > Network Settings page. The below screenshot shows an example of what a default hostname field looks like in LMI:




The field is active for editing which can cause users to believe editing the hostname is allowed. However, in the AWS environment, only the default hostname is supported by LMI and AWS. Changing the hostname using this method requires the system to reboot. But when the system reboots the AWS hostname will no longer match the startup scripts for the network, hence the networking for the system will be broken. 

Due to the fact that AWS does not offer a direct console to the VM's like VMWare ESX offers, this makes it impossible to connect to an LMI instance that does not have any functioning network stack. This means that the system becomes inaccessible for users and administrators. Hence, users should avoid changing this property in the AWS environment. 

Note: A fix is planned for future versions of LMI. This is a known issue as of the latest generally available LMI version when this article was published.

This article provides an advisory for users using LMI on Amazon Web Services regarding changing the default hostname.

Only those users who host LMI on Amazon Web Services are affected by this issue.