Access value of secure environment variable in Pipelines

I am writing some code to integrate with AWS, using APIs (Node.js) but keep getting stuck at the point of the SDK tries to authenticate with AWS in the signature generation. Both my ACCESS and SECRET keys were marked as secure. 

I have reverted the AWS_ACCESS_KEY_ID variable to be non-secure and managed to get an authentication error, rather than a signature error (as I was getting when this variable was secured), which leads me to beleive its to do with my scripts not being able to access the secure variable value correctly.

I have tried to access via process.env or pass them in as args to no avail.

What is the correct way of ensuring the correct value is used by any script, bash or node?



0 answers

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Thursday in Agile

How Scrum works? It starts with training and education

To answer “How scrum works,” most of the teams I've worked with first addressed the question: “where to start?”  That question applies to both implementation and improvements on the Scrum framew...

196 views 3 5
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you