Windows EC2 build agent AMI sources no longer auto register

I created a new windows EC2 and installed build agent and configured normally. The agent will show up in 'unauthorized' on the TC server indicating a good connection.

I then created an AMI of the machine once configured, and added that AMI as a cloud profile source.

When using the image source as an AMI, it will never register the agent automatically as a cloud agent, it will always show up as an unregistered normal agent. I have tried everything and confirmed this same exact buildAgent.conf works fine on linux AMIs. The Teamcity tags are added to the instance indicating it was started as a cloud agent. HOWEVER if I use an instance for the source instead of an AMI, it works fine as an auto authorized cloud . Any ideas?