nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Setting AWS Credentials, Script Task and PowerShell

Jeremy Roelfs

For a Script Task in your plan. You typically need to set your AWS credentials to point to and use your EC2 instances.

Set-Credentials is the AWS way, but that does not work.

Instead use this?
SET AWS_ACCESS_KEY_ID=$Env:bamboo_AWSAccessKeyId
SET AWS_SECRET_ACCESS_KEY=$Env:bamboo_AWSSecretKeyPassword
SET AWS_DEFAULT_REGION=us-east-1

Put it is still not pointing to my EC2 instance correctly. None of my AWS CLI commands work.

Accepted answers

Jeremy Roelfs

You can't set the creds in an inline PS. Or, at least I have not been able to find a way to.

Recommend using an inline cmd as follows.

Create a Script task. Use cmd. Set your creds:

@echo off
SET AWS_ACCESS_KEY_ID=${bamboo.AWSAccessKeyId}
SET AWS_SECRET_ACCESS_KEY=${bamboo.AWSSecretKeyPassword}
SET AWS_DEFAULT_REGION=us-east-1

Then, if you need to invoke any PowerShell scripts or other functionality.

Create a Local Agent so you can talk to your local bamboo server. Remember everything works from these agents.
You do not need to setup any capability.
Bamboo's auto-magic will chose the correct agent to build with.

Then in that same inline cmd use the below code to talk to your PowerShell scripts correctly:

<span>powershell </span><span>-</span><span>NoProfile</span> <span>-</span><span>Command</span> <span>"C:\scripts\<myPSscript>.ps1 <arg>; exit $LASTEXITCODE"</span> <span><</span><span> NUL</span>

Reference

This seems to work well for our needs. HTH.

All comments

Alexey Chystoprudov

@Jeremy Roelfs, when you see output or logs of Script task exception Bamboo will show what environment variables are available for script. Most possible you should use

${bamboo_AWSAccessKeyId} variable name, not $Env: form

Jeremy Roelfs

I never could get it working in PowerShell. Not sure what I'm doing wrong. So I switched to a inline cmd. It took some work getting my commands switched to a cmd, but I can set the variables just fine now:

@echo off
SET AWS_ACCESS_KEY_ID=${bamboo.AWSAccessKeyId}
SET AWS_SECRET_ACCESS_KEY=${bamboo.AWSSecretKeyPassword}
SET AWS_DEFAULT_REGION=us-east-1

Jeremy Roelfs

@Alexey Chystoprudov We have to use PowerShell, so I'm back again... can you please just give me an example?

is it SET AWS_ACCESS_KEY_ID=${bamboo_AWSAccessKeyId}

This is how you set it in PowerShell: $env:AWS_ACCESS_KEY_ID=<key here>

But this: $env:AWS_ACCESS_KEY_ID=${bamboo_AWSAccessKeyId} does not work in the Script Task.

The error I receive is "A positional parameter cannot be found that accepts argument" Real descriptive...

What is it exactly? Can you give me a full example please?

Alexey Chystoprudov

@Jeremy Roelfs, I'm not familiar with PowerShell scripts

Steffen Opel [Utoolity]

Update 2018-02-26: We have fixed the below referenced example from our docs by adding the required 'Env:' prefix for accessing environment variables from PowerShell.

According to the related documentation for our (Utoolity's) AWS Credentials Variables task, the following syntax for referencing Bamboo environment variables in PowerShell should work within Bamboo's Script task:

$AWS_SECRET_ACCESS_KEY = $Env:bamboo_custom_aws_secretAccessKey_password<br>$AWS_SESSION_TOKEN = $Env:bamboo_custom_aws_sessionToken_password$AWS_ACCESS_KEY_ID = $Env:bamboo_custom_aws_accessKeyId<br>

So given your Bamboo variable names, the following should do the trick in your AWS CLI based scenario:

$AWS_SECRET_ACCESS_KEY = $Env:<span>bamboo_AWSSecretKeyPassword</span>$AWS_ACCESS_KEY_ID = $Env:<span>bamboo_AWSAccessKeyId</span><br>

Caveats

Please note that those standard environment variables only work for the AWS CLI and not the AWS Tools for PowerShell due to an easily confusing difference between these two:

The AWS CLI supports specifying credentials via environment variables (i.e. '$AWS_ACCESS_KEY_ID' etc.), but does not support specifying credentials via the command line.
The AWS Tools for PowerShell support specifying credentials via the command line (i.e. '-AccessKey $Env:bamboo_AWSAccessKeyId' etc.), but do not support specifying credentials via environment variables.

Further, at least the AWS Tools for PowerShell will also fall back to any subsequent credentials source in the default credentials provider chain in case credentials explicitly specified on the command line are incorrect or absent (rather than complaining about an incorrect parameter), which is at least a bit counter intuitive I think.

Jeremy Roelfs

That does not work either. I think this is working

$AWS_ACCESS_KEY_ID="${bamboo.AWSAccessKeyId}"
$AWS_SECRET_ACCESS_KEY="${bamboo.AWSSecretKeyPassword}"
$AWS_DEFAULT_REGION="us-east-1"

Jeremy Roelfs

NOPE. The above doesn't work either. Set-AWSCredentials doesn't work... how the do you set the fricken credentials? Seems like pretty basic, straight-forward and common thing? Are we restricted to using a .ps1 file or a cmd?

Jeremy Roelfs

I can get the key/secret key in the script. You can Write-Host and they show up. I just cannot set the AWS variables so my commands will work

Jeremy Roelfs

You can't set the creds in an inline PS. Or, at least I have not been able to find a way to.

Recommend using an inline cmd as follows.

Create a Script task. Use cmd. Set your creds:

@echo off
SET AWS_ACCESS_KEY_ID=${bamboo.AWSAccessKeyId}
SET AWS_SECRET_ACCESS_KEY=${bamboo.AWSSecretKeyPassword}
SET AWS_DEFAULT_REGION=us-east-1

Then, if you need to invoke any PowerShell scripts or other functionality.

Then in that same inline cmd use the below code to talk to your PowerShell scripts correctly:

<span>powershell </span><span>-</span><span>NoProfile</span> <span>-</span><span>Command</span> <span>"C:\scripts\<myPSscript>.ps1 <arg>; exit $LASTEXITCODE"</span> <span><</span><span> NUL</span>

Reference

This seems to work well for our needs. HTH.

Tanishka

you can set it by :

#1. How to configure AWS CLI

➜ ~ aws configure
AWS Access Key ID [****************xxxxx]: XXXXXXXXXXXXXX
AWS Secret Access Key [****************xxxxx]: XXXXXXXXXXXXXXXXXXXXXXX
Default region name [us-east-1]:
Default output format [json]:

For details check this https://thedbadmin.com/aws-mysql-rds-database-creation-using-awscli/

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

bamboo

script

aws

powershell