> You can store the username/password in the module configuration file. > Another solution is to create a central utility method that can be > called to get a reference to a cloud object. Only the utility method > will need to look up the password in order to create a cloud instance. > Another benefit from the latter solution is one single cloud instance > can be shared and reused by all code, as the basic cloud implementation > is (apparently) threadsafe.
I was thinking that depending on the caller the security implementation could return a valid cloud (based on a stacktrace)
