Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Is it possible to use an S3 bucket with subfolder in the ElasticBeanstalk deploy pipe?

Within the pipe for ElasticBeanstalk, we are looking to use the $S3_BUCKET variable to use different subfolders based on deployments, such as companybucket/beta, companybucket/feature, and so on.


However, when we set a subfolder within that variable, we get an error during deploy that reads:

An error occurred (InvalidParameterCombination) when calling the CreateApplicationVersion operation: Invalid S3 location Bucket: companybucket/beta Key: environment/


It is strange, as it can upload successfully to S3 in the line before this one:

Artifact uploaded successfully to s3://companybucket/beta/environment/


My hunch is that the parameters are different for the S3 upload and the ElasticBeanstalk deploy.

Is there a workaround for this, or a better way we can use one bucket for multiple deployments?

2 answers

0 votes

Hi @Douglas Kolpien

Thank you for your question!

We'll investigate this feature and notify you.


Oleksandr Kyrdan

0 votes

@Douglas Kolpien indeed, we hardcode the location in s3 bucket.

Our flow right now: we upload to $APPLICATION_NAME folder.

One workaround for you is that you can pass APPLICATION_NAME as beta, but that means that application created also will be beta.

Tell us if that is ok for you, based on this we consider true S3 location support sooner or later.

Thanks for raising this and helping us to improve.

Regards, Galyna

Thank you for the reply @Galyna Zholtkevych 

With our current structure, changing out APPLICATION_NAME to beta would not work.

A solution supporting true S3 location would be ideal.

We can work around this now, and keep an eye on this for future implementation.


@Douglas Kolpien ok, we'll discuss within a team this change, I'll notify you once we have an update for you.

Cheers, Galyna

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Marketplace Apps & Integrations

Staying organized with Jira: best practices for a better project management

Project managers know this problem: A “mountain of work” lays in front of you, and you don’t know how and where to tackle them. Different to-dos lie ahead, but just one task after the other can be ha...

152 views 2 1
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you