Due to some maintenance issues, this service has been switched in read-only mode, you can find more information about the why

and how to migrate your plugin documentation in this blogpost

Skip to end of metadata
Go to start of metadata

Publish zip files to Amazon Web Service Elastic Beanstalk Applications.

Plugin Information

View AWS Elastic Beanstalk Publisher on the plugin site for more information.

The current version of this plugin may not be safe to use. Please review the following warnings before use:

Amazon Web Services Elastic Beanstalk Publisher

Master status:

This plugin allows for publishing to an Elastic Beanstalk application as either a Build or Post Build step.

Amazon credentials are set in the global configuration.
IAM credentials need to be able to read and upload to S3, and to read and configure Elastic Beanstalk.

Example Credentials

  "Version": "2012-10-17",
  "Statement": [
      "Effect": "Allow",
      "Action": [
      "Resource": "*"

After adding the Access Key ID and Secret Key in to the Jenkins master configuration, click Advanced and choose a region to see what applications your credentials actually see.


Global Configuration

Job Configuration


-> 1.0

  • Multithreading the update environment process, in case there are multiple environments to be updated.
  • Added test buttons to see which applications your credentials can see, both in the global and job config.
  • Added a test button to see currently available environment names for the given application.
  • Verify that environment completed updating.
  • Bug fixes regarding duplicate AWS credentials.


This is a fork of Aldrin Leal's Elastic Beanstalk Deployment plugin

type key summary

Data cannot be retrieved due to an unexpected error.

View these issues in Jira
  • No labels


  1. Unknown User (bedge)

    How does this differ from Aldrin Leal's Elastic Beanstalk Deployment plugin ?

  2. Unknown User (bella)

    Is there a way to not fail the build if the application version already exists?

    In my case the application version was created by a previous promotion step and deployed to env-1.  

    When I run the second promotion step the application version has already been created and just needs to be deployed to env-2.

  3. Unknown User (jgallport)

    Need to add us-east-2 to drop down

  4. Unknown User (aasencio)

    Note that there is an issue with using a zip file to deploy a single war to AWS EBS Tomcat. If you want to deploy a single app using a zip, you will have to include a second dummy war. See https://stackoverflow.com/q/43376178/786110