Skip to content

First Spring Boot Deployment to Elastic Beanstalk

This tutorial walks through a first Spring Boot deployment using a runnable JAR, a Procfile, and the Corretto 17 platform branch on 64bit Amazon Linux 2023. The goal is to make the startup contract explicit and keep the deployment bundle predictable.

Prerequisites

  • Completed local setup from 01-local-run.md.
  • EB CLI authenticated through your configured AWS CLI profile.
  • A working Spring Boot project that packages as target/guide-0.0.1-SNAPSHOT.jar.
  • IAM permissions to create Elastic Beanstalk applications and environments.

What You'll Build

You will initialize Elastic Beanstalk metadata, create a web server environment, deploy the application version, and validate health through /health.

sequenceDiagram
    participant Dev as Developer
    participant Maven as Maven
    participant EBCLI as EB CLI
    participant S3 as Elastic Beanstalk S3 Bucket
    participant Env as EB Environment

    Dev->>Maven: mvn clean package
    Dev->>EBCLI: eb init
    Dev->>EBCLI: eb create
    Dev->>EBCLI: eb deploy --staged
    EBCLI->>S3: Upload source bundle
    EBCLI->>Env: Start deployment
    Env->>Env: Launch Procfile command
    Env->>Env: Route health checks to /health

Steps

  1. Package the application.
mvn clean package
  1. Confirm the project root contains the JAR path expected by Procfile.
web: java -jar target/guide-0.0.1-SNAPSHOT.jar
  1. Initialize Elastic Beanstalk metadata.
eb init

During prompts, select:

  • The target $REGION.
  • Existing or new application named $APP_NAME.

  • The platform branch Corretto 17 running on 64bit Amazon Linux 2023.

  • Create the environment with an explicit CNAME and health check path.

eb create "$ENV_NAME" --cname "$ENV_NAME" --envvars SPRING_PROFILES_ACTIVE=prod
  1. Configure /health as the application health check path.
option_settings:
    aws:elasticbeanstalk:environment:process:default:
        HealthCheckPath: /health
  1. Deploy the current application version.
eb deploy --staged
  1. Inspect the environment.
eb status
eb health
eb events
eb open
  1. Validate the deployment URL directly.
curl --verbose "http://$ENV_NAME.$REGION.elasticbeanstalk.com/health"

Verification

Use these checks after deployment:

eb status "$ENV_NAME"
eb health "$ENV_NAME"
eb logs --all
aws elasticbeanstalk describe-environments --application-name "$APP_NAME" --environment-names "$ENV_NAME" --region "$REGION"

Expected outcomes:

  • The environment reaches Ready state.
  • Health is Green.
  • The endpoint responds from the Spring Boot app.
  • Logs show Elastic Beanstalk launching the JAR from Procfile.

See Also

Sources