we attempted to install our first ESP Agent in our AWS cloud environment and ran into an issue. Our EC2 instances are going to consistently come up and down, and when they come up with grab new dns name and ip address. Because ESP needs the dns name to talk back to the agent, how are folks handling this? Is there some way to dynamically update ESP that an Agent has a new ip/dns?
Anyone run into this issue, or any other similar issues? anyone actually running ESP Agents in their cloud env? Thanks!
It seems to me that you could include a script that runs at startup that grabs the new DNS name and then modifies the agent.parm file. Of course, this should run before the startup script for the agent runs. Or, maybe you could include that as part of the agent startup script.
Just a thought. . .
Thanks for the feedback Jonathan. We are looking at something similar, just trying to nail down the best way to have AWS let us know a new instance has been stood up and a new dns/ip is available.
I think we can get it to work, but it would be nice if ESP had a way to dynamically know when an Agent ip/dns is changed.
Consultant, Infrastructure Eng
IT Operations – Batch Application Services
Also, it appears we’d then have to issue an AGENT SET command to tell ESP agent dns has changed.
Since these are new instances (meaning scale), could you manage this using Puppet?