Kemp Support, how can we help?

The latest application delivery knowledge and expertise at your fingertips.

Hostname persistency in AWS environment

 

Information

 

Summary:

Hostname assignment and hostname persistency for Flowmon appliances deployed in AWS.

Environment:

Product: FOS

Version: Any

Platform: AWS

Question/Problem Description: Why the hostname of the Flowmon appliance was changed after reboot to:
private-ipv4-address.ec2.internal
or
ec2-instance-id.ec2.internal
Steps to Reproduce:  
Error Message:  
Defect Number: FLMON-7360
Enhancement Number:  
Cause: The hostname is given by the instance and settings of the assigned subnet. Due to the wrong permission (root) for /etc/hostname for deployed appliances from AWS marketplace, manually assigned hostname from GUI is not persistent after reboot.
[flowmon@localhost ~]$ ll /etc/hostname
-rw-r--r--. 1 root root 21 Jun 16 2022 /etc/hostname
Resolution: The fix of /etc/hostname permission will be implemented in one of the future versions.
Workaround:  
Notes:

Hotfix:
https://nextcloud.flowmon.com/index.php/s/ad8QkjXr4T3R7Wm

AWS documentation:
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-naming.html


Was this article helpful?
0 out of 0 found this helpful

Comments