In less than obvious fashion, Amazon EC2 Windows Server AMIs reset their hostname on startup due to the Ec2ConfigService. To disable this feature, select ‘EC2ConfigService Settings’ from the start menu, and uncheck the first checkbox under ‘Set Computer Name’
Recent Posts
- Stubbing class constants with rspec and Ruby
- Downloading All The Github Repositories
- Generating entropy in the cloud
- Disabling Firefox shortcuts on OS X
- Recreating the Opscode Chef validation key
- require-rubygems.overrides and gem2deb 0.2.2
- locale errors on debian
- Creating a Debian sid emi for Eucalyptus
- LVM errors with sbuild
- munin-cgi-graph with fcgid on ubuntu lucid
Archives
What I'm Doing...
- When I was young and my father was an airline captain for @Continental Express, they flew all over Maine. Now @United only serves PWM. 7 hrs ago
- @sr00t @jtimberman when disoriented, always remember that the enemys gate is down. in reply to sr00t 11 hrs ago
- .@jtimberman yes! #noops == "I like my Wall, thank you very much." 13 hrs ago
- More updates...
Posting tweet...
Powered by Twitter Tools
Good one,
This behaviour of Amazon EC2 – Windows based hosts – caused us a lot of headache because our software stack was sensitive to host name changes
Thanks. I hadn’t seen this setting!
Thanks for the tip! Is there a way to permanently associate an Elastic IP address with an instance too so that I don’t have to associate it each time I start the instance?
Is there a way to make this change programmatically?
Cheers mate! This is what I needed.
Hi btm.geek,
Thanks for the inputs, we’ve been searching for this answer since last year.
Maraming Salamat! (Thank you very much!)