I got this template working, but I am having a big problem. I currently have the template applied to 6 RDS instances, all polling from the same polling engine. I have several other RDS instances to add; however, I'm at a halt. The component powershell script is locking a file in the AWSToolkit on the polling engine. This is preventing the other templates and components to have an unknown status until the file is free to process the script. The application and component availability keeps teetering from unknown to Up. Adjusting the timeout and polling frequency helps a little, and I can also spread them out across polling engines, but overall this will not help when I assign the template to about 50 RDS instances.
Anyone know how to work around this? Is there a way to adjust the script so it doesn't lock the file, or perhaps run the script in it' own space?
@jvb
