My specific situation is that I have a bitbucket pipelines file that uses an AWS-CLI docker image as a service container. My pipeline step script runs `aws` commands to set some configurations before running an AWS S3 sync of files generated on the main container to a specified endpoint in S3. The problem is that I end up with the following error:
bash: aws: command not found
I defined the service definition to use the `xueshanf/awscli` image. Am I simply using the wrong one, or do I need to pass additional Docker run options in the pipeline file? I didn't see any options for that in the documentation.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
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!
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