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.

score 6 · Answer 1 · answered Jun 13 '21 at 16:47

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.

score 3 · Answer 2 · answered Jul 18 '19 at 16:26

3

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

answered Jul 18 '19 at 16:26

Shishir

39
2

4

Can you please explain your answer? – Haseeb Burki Aug 22 '20 at 17:14
1

This does will exclude any changes to the artifact done during the build step. – Andrey Jun 13 '21 at 16:17

score 2 · Answer 3 · answered Dec 11 '16 at 20:52

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 '16 at 20:52

James111

15,378
15
78
121

3

There is no option for artifacts packaging – Code Wiget Jul 11 '19 at 23:05
1

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. – Adam Loving Aug 21 '19 at 23:02

Error in AWS codepipeline when deploying ElasticBeanstalk

3 Answers3