A pop-up survey could appear while you're here--curious what it's for? Click here to learn more!

×
Forums
Home Q&A Discussion groups Articles Ask a question Search
Learning
Events
Champions
Community
Forums
Home Q&A Discussion groups Articles Ask a question Search
Learning Events Champions
Forums
Home Q&A Discussion groups Articles Ask a question Search
Learning Events Champions

Forums

Articles
Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Q&A
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Events
Community resources

Bitbucket Pipeline, Boto3, AWS and multi account stack deployments

Peter McAlister
Peter McAlister
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Get involved
December 6, 2017

Hi folks

 

The AWS_ACCESS_KEY_ID environment variable seems to constrain deployment to a single account and my attempt to override this in Boto3 post innit have failed. Is there a recommend practice for multi account deployments, so as per AWS Orgs for example we have account ids per DEV, UAT and PROD swimlanes.

Answer
Watch
Like Be the first to like this
864 views

1 answer

0 votes
Deleted user July 30, 2018

Hi Peter, I am going through this right now.  Did you ever find a good solution?

How are you scripting it?

Thanks,

Brad

Reply

Suggest an answer

Log in or Sign up to answer
Bitbucket
Bitbucket
TAGS
AUG Leaders

Atlassian Community Events

    See all events
    Community
    Forums
    FAQs Forums guidelines
    Learning
    About learning Resources
    Events
    Champions
    Copyright © 2025 Atlassian
    Privacy Policy Notice at Collection Terms Security