Error in AWS codepipeline when deploying ElasticBeanstalk

Question

I've created a pipeline which does the following:

Git changes trigger next action (code build)
Codebuild initiates & builds a docker image from git source
Set latest docker container up on Elasticbeanstalk

The first 2 steps are working fine, git changes initiate a codebuild, the codebuild builds a docker image, and then tries to set it up on Elasticbeanstalk (which fails). The following error is thrown:

Invalid action configuration The action failed because either the artifact or the Amazon S3 bucket could not be found. Name of artifact bucket: MY_BUCKET_NAME. Verify that this bucket exists. If it exists, check the life cycle policy, then try releasing a change.

In my codebuild project, I've set the artifact location to MY_BUCKET_NAME & named it aws-test-artifact. Is this all I have to do?

I've tried looking around and am unable to find anything on this issue.

Andrey · Accepted Answer · 2021-06-13 16:47:46Z

7

As Adam Loving commented we must add artifacts section.

Adding this section to your buildspec.yml file will make this work.

artifacts:
  files:
    - '**/*'

From documentation https://docs.aws.amazon.com/codebuild/latest/userguide/build-spec-ref.html#build-spec.artifacts.files adding '**/*' will include all files into the build target.

answered Jun 13, 2021 at 16:47

Andrey

3774 silver badges4 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

James111 · Accepted Answer · 2016-12-11 20:52:15Z

2

So I found the fix to this issue! What I had to do was goto codebuild => edit project => Show advanced settings => Artifacts packaging

From here I changed Artifacts packaging to Zip!

answered Dec 11, 2016 at 20:52

James111

16k17 gold badges89 silver badges130 bronze badges

2 Comments

Code Wiget Over a year ago

There is no option for artifacts packaging

Adam Loving Over a year ago

Also, make sure your Buildspec has an artifacts section. Otherwise the build will succeed and link to an artifacts file that doesn't exist and was never uploaded.

Shishir · Accepted Answer · 2019-07-18 16:26:50Z

2

I had the same problem. Just changed Input artifacts from BuildArtifact to SourceArtifact in the build stage, and everything worked.

answered Jul 18, 2019 at 16:26

Shishir

372 bronze badges

2 Comments

Haseeb Burki Over a year ago

Can you please explain your answer?

Andrey Over a year ago

This does will exclude any changes to the artifact done during the build step.

Collectives™ on Stack Overflow

Error in AWS codepipeline when deploying ElasticBeanstalk

3 Answers 3

Comments

2 Comments

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

Comments

2 Comments

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related