[Code Pipeline x Elastic Beanstalk] Summary of errors and countermeasures for CI / CD Java applications to Elastic Beanstalk with Code Pipeline

CI / CD Java application to Elastic Beanstalk with Code Pipeline This is a summary of the errors that can occur in and how to deal with them.

environment

• OS：Windows10
• IDE：Eclipse 2020-03
• JDK：Amazon Correto 8 --Framework: Spring Boot
• AWS
  • CodePipeline
    • CodeCommit
    • CodeBuild
    • CodeDeploy
  • Elastic Beantalk --Java SE (Java 8 version 2.10.8)
    → * This is not the latest version released on June 3, 2020. Please understand. --RDS: MySQL Community Edition (version 8.0.17)

Error and countermeasures

1. Elastic Beanstalk

(1) 502 (Bad Gateway) error occurs when accessing

Let's check the settings again. [Code Pipeline x Elastic Beanstalk] CI / CD Java application to Elastic Beanstalk with Code Pipeline Part 2 Review "[2] Additional settings" in "3. Creating an Elastic Beanstalk environment" and check if there are any omissions in the settings.

2. RDS

(1) Cannot access the database

Let's check the permission settings again. [Code Pipeline x Elastic Beanstalk] CI / CD Java application to Elastic Beanstalk with Code Pipeline Part 2 Review the areas (4) to (9) in "[1] Connection settings in RDS" in "4. Database settings" and check for any omissions.

3. CodePipeline

(1) "The action failed because either the artifact or the Amazon S3 bucket could not be found ...." error appears during deployment

Changing the input artifact from Build Artifact to Source Artifact will fix it. Follow the procedure below to change it.

① In the pipeline, click "Edit".

② Click "Edit Stage" in the "Deploy" column.

③ Click the edit mark (?).

④ Change "Input Artifact" to "Source Artifact" (①) and click "Finish" (②).

⑤ Click "Save".

⑥ Click "Save".

(2) "Deployment failed. The provided role does not have sufficient permissions: Failed to deploy application. Service: AWS Logs ..." appears.

This error occurs because you do not have access to CloudWatch Logs. This can be resolved by granting the "CloudWatchLogsFullAccess" policy to the role created for CodePipeline.

The procedure is as follows.

① Find and click "IAM" on the management console.

② "Role" (①)> Search for the target CodePipeline role (②) and click the role name (③).

③ Click "Attach policy"

④ Search for "CloudWatch Logs Full Access" (1), check it (2), and click "Attach Policy" (3).

At the end

As I wrote in the main part, I made an error 3 days in the 1- [3]-(5) gradlew permission change in the main part, and 3 times in the deployment stage of 5- [1]-(10). I stumbled and almost broke my heart many times. Even if an error occurs, don't be discouraged, but rather, let's enjoy it with the feeling of how to solve it!