Viewing deployment logs for an Elastic Beanstalk environment

Elastic Beanstalk generates a deployment log for each deployment to your environment. The deployment log provides a consolidated, chronological view of what happened during a deployment, including dependency installation, build output, application startup, and any errors encountered. You can use deployment logs to quickly diagnose failed deployments without needing to SSH into instances or correlate multiple log files.

Deployment logs are written to each instance locally. For deployments triggered through the console, CLI, API, or managed updates, one instance continuously uploads its log to Amazon S3 during the deployment. The Elastic Beanstalk console reads the log from Amazon S3, so you can monitor progress without connecting to the instance.

Deployment logs are designed to be concise. On success, the log shows only summary messages (for example, which commands ran and completed). On failure, the log includes up to 50 lines of output from the failed step, so you can see the error without sifting through verbose output.

Note

Deployment logs are available on Amazon Linux 2 and Amazon Linux 2023 platform versions released on or after March 11, 2026. Windows platforms are not currently supported.

Supported operations

Deployment logs are generated for the following operations:

• Application deployments – Deploying a new application version to your environment.

• Configuration updates – Changing environment configuration settings that require instance updates.

• Environment creation – The initial deployment when you create a new environment.

• Restart app server – Restarting the application server on your instances.

Operations that don't modify application or configuration state on instances, such as requesting logs, swapping CNAMEs, or updating tags, do not generate deployment logs.

Deployment log contents

A deployment log captures the following information during a deployment:

• Deployment lifecycle – Start and completion messages for each deployment phase, such as Starting Application deployment and Completed Application deployment.

• .ebextensions output – On success, the names of commands that ran. On failure, the last 50 lines of cfn-init output to help diagnose the issue.

• Platform hooks output – On success, the names of hook scripts that ran. On failure, the last 50 lines of hook output.

• Dependency installation – Output from package managers such as npm install, pip install, composer install, and bundle install. On success, only a completion message is logged. On failure, the last 50 lines of output are included.

• Build output – Output from build commands such as docker build, go build, and Java builds. On failure, the last 50 lines of output are included.

• Application startup output – Initial output from your application after it starts. The source depends on your platform:

  • Docker – Container logs from docker logs or docker compose logs

  • Java SE, Go, Node.js, Python, Ruby, .NET – Process stdout logs

  • Tomcat – Catalina log output

  • PHP – PHP-FPM master and pool error logs

  • ECS – Container logs from each task container

  Note

  Application output is captured starting 2 seconds after the application starts. Only the initial startup messages are included – if your application takes longer to produce output, it won't appear in the deployment log. To see full application logs, request bundle logs or connect to the instance directly. For more information, see View instance logs.

When a deployment step fails, the log marks it with [ERROR] and includes up to 50 lines of output from the failed step. If the deployment log does not contain enough detail, you can retrieve the full instance logs (including eb-engine.log, eb-hooks.log, and application logs) from the Logs tab. For more information, see Viewing logs from Amazon EC2 instances in your Elastic Beanstalk environment.

Viewing deployment logs in the console

The Elastic Beanstalk console provides a Deployments tab on the environment dashboard where you can view your deployment history and logs.

Viewing deployment history

To view deployment history

1. Open the Elastic Beanstalk console, and in the Regions list, select your AWS Region.

2. In the navigation pane, choose Environments, and then choose the name of your environment from the list.

3. In the environment dashboard, choose the Deployments tab.

   The Deployments tab shows a table of deployments for the environment. Each row includes the following information:

   • Request ID – The unique identifier for the deployment.

   • Status – Succeeded, Failed, or In progress.

   • Type – The deployment type, such as Environment Creation, Application Deployment, Configuration Update, Managed Platform Update, Restart App Server, Rebuild Environment, Restore Environment, Swap Environment Domain, or Terminate Environment.

   • Start Time – When the deployment began.

   • Duration – How long the deployment took to complete.

When a deployment is in progress, the tab automatically polls for updates. You can also choose the refresh button to manually reload the list.

Viewing deployment details and logs

To view deployment details

1. On the Deployments tab, choose the Request ID link for the deployment you want to inspect.

2. The deployment detail page shows a summary section with the request ID, status, deployment type, start time, duration, and deployment policy. The deployment policy (for example, All at once, Rolling, Rolling with additional batch, Immutable, or Traffic splitting) is shown when it can be determined from the deployment events.

3. Below the summary, choose one of the following tabs:

   • Events – A timeline of events related to this deployment, filtered to show only events for the selected deployment.

   • Deployment Logs – The consolidated deployment log from the instance. You can search, filter by log level, and download the log file.

For in-progress deployments, the logs tab automatically refreshes to show new log entries as they are written. After a deployment completes, the console fetches the final log state to ensure you see the complete output.

Important

Viewing deployment logs in the console requires s3:GetObject permission on the environment's Amazon S3 storage bucket (elasticbeanstalk-region-account-id). If your IAM policy does not include this permission, the deployment history and events will still be available, but the logs tab will show an error.

Deployment log files on instances

Deployment logs are written to the /var/log/deployments/ directory on each instance. The log filename depends on how the deployment was triggered:

• Workflow-controlled deployments (triggered through the console, CLI, or API) – eb-deployment-request-id.log, where request-id is the unique deployment request ID.

• Self-startup deployments (instance launch or restart app server) – eb-deployment-unix-timestamp.log.

Elastic Beanstalk automatically rotates these files, keeping the 50 most recent deployment logs on each instance.

For workflow-controlled deployments, the log is uploaded to Amazon S3 at the following path:

s3://elasticbeanstalk-region-account-id/resources/environments/logs/deployments/environment-id/log-filename

In multi-instance environments, the first instance to begin uploading claims the role for the entire deployment. That instance uploads its log to Amazon S3 for the duration of the deployment. All instances still write deployment logs locally.

Important

Uploading deployment logs to Amazon S3 requires s3:PutObject permission on the environment's Amazon S3 storage bucket in the instance profile, and the VPC configuration must allow connectivity to Amazon S3.

Deployment log uploads are capped at 1 MB per file. If a deployment log exceeds this size, the uploaded version is truncated with a message indicating that the full log is available on the instance.

Disabling S3 log uploads

To prevent deployment logs from being uploaded to Amazon S3, set the following environment property on your environment:

option_settings:
  - namespace:  aws:elasticbeanstalk:application:environment
    option_name:  EB_DEPLOYMENT_LOG_S3_DISABLED
    value:  true

When this environment property is set, deployment logs are still written locally to /var/log/deployments/ on each instance, but they are not uploaded to Amazon S3 and will not be available in the console Deployments tab. You can also set this property in the Configuration page under Software, or by using the EB CLI or AWS CLI.