Comment 3 for bug 1538522

Well, this is configurable. you can make the command be whatever you want in user-data.
But cloud-init started the walinuxagent because it needs walinuxagent to do some work for it, and cluod-init is at that point blocking most of boot. So without the start, it wouldnt be started.

The fix I'd like to apply is to remove the need for cloud-init to use walinuxagent at all, and instead use the '__builtin__' agent command that makes cloud-init do what walinuxagent did for us.