#Ocropus windows installer update#

Eventually all servers should receive the update, but when this happens is out of your control. The resolution implemented by AWS is that the HostManager running on the servers polls for updates. In fact this is still the case today, and is exasperated by the number of servers.

#Ocropus windows installer update#

The result is that any number of servers within an auto-scaling group could fail to update and continue running on stale code. The reason AWSDeploy was not production ready is that it suffered an issue with the update mechanic, whereby the update signal to a particular server sometimes got lost. That may be true depending on your requirements, but here is some important background. It appears this has since been removed and I'm assured by Amazon support that it's now production ready.

This used to be clearly documented with a disclaimer that AWSDeploy was a best endeavours tool only and should not be used for production deployments. The Lost Update SignalДЄlthough the basic limitations of AWSDeploy can be overcome, there are still inherit issues with AWSDeploy and the update mechanic. In doing so it provides a more robust mechanic for rolling out updates, and offers a much greater level of flexibility & control over the update process. NET applications running on EC2 instances, and further mitigates the shortcomings of the AWSDeploy standalone tool. This article focuses on an alternative way to update. NET applications into the AWS Cloud to support auto-healing and auto-scaling in particular to provision multiple websites and/or Windows services on a single box. In a previous article I wrote about the shortcomings of Amazon's AWSDeploy tool, and the problems associated with deploying.