Elastic Bamboo Startup Script is corrupted

[Roger Mier]

I've been trying to add a Startup Script to the Base Windows AMI in order to install Visual Studio Community 2017 when the instance is created.  I thought this would be a fairly easy thing to do, but nothing I do seems to work.  Regardless of what I put in there, when the instance is running, and I look at the User Data, it's all random characters and symbols, and the script itself never seems to run.

Do I have to make a custom image to get this working?  I'd really rather not have to do that just to get this project to build.

I've tried using <powershell> tags, I've tried without.  I've tried Base64 encoding the script.  I've tried using a Bamboo task to do the install, but the bamboo user doesn't seem to have rights to install things.

I've spent the better part of a workday trying to get this one thing to work and I'm about at my wits' end.

[Robert W]

Hey Roger,

When you add a Startup Script to the elastic image configuration, that script is actually bundled with a series of other scripts which is then encoded and sent to AWS.  This is why when you attempt to 'view User Data' from the AWS console, it appears all garbled.

The script you designate is sent to the EC2 instance in

C:\Windows\Temp\BambooStartupScript-1.bat

You can view/debug the logs for the startup script here:

C:\Users\Bamboo\BambooStartupLog.txt

At this time, it is not possible to use Powershell startup scripts for an elastic agent.  However, we do have an open Feature Request for this functionality.  I highly recommend you comment and vote on the request.

BAM-20058: Add support for Powershell scripts to Elastic Agent User Startup Scripts.

Cheers,

Robert 

Dev Tools Support | Atlassian