# Deploying to AWS Elastic Beanstalk from Jenkins **URL:** \ **Category:** Ask a question\ **Created:** [March 22, 2022, 7:36am UTC](https://community.jenkins.io/t/deploying-to-aws-elastic-beanstalk-from-jenkins/1880 "2022-03-22T07:36:42Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![vikram291194](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/vikram291194/32/940_2.png) [@vikram291194](https://community.jenkins.io/u/vikram291194)\ **Post date:** [March 22, 2022, 7:36am UTC](https://community.jenkins.io/t/deploying-to-aws-elastic-beanstalk-from-jenkins/1880/1 "2022-03-22T07:36:43Z")
Hello, I am trying to deploy my code from Jenkins to AWS Elastic Beanstalk using the AWS Elastic beanstalk Plugin. The project is a maven project which is being built successfully by the Jenkins job(Freestyle type). My Jenkins is running on an AWS EC2 instance and I have given S3 full access and AWS CodePipeline full access to my EC2 server and also Attached the proper bucket policy to my S3 bucket i.e with the proper Elastic Beanstalk role. Also I have also added proper credentials in AWS Elastic Beanstalk plugin in Jenkins and also stored my AWS account credentials in Jenkins. Below are the snippets that show the console output error (1) As you can see that Jenkins is marking the build as a success. ![image](https://europe1.discourse-cdn.com/flex013/uploads/jenkins/original/2X/7/78794dd05774b40fda117d2386ebe50498dac12c.png) Finally, whenever I config. the Deploy to S3 tab under Additional behaviors I get the above error. If i don’t config the additional Deploy to S3 config. the older version of the application the Elastic Beanstalk get updated by Jenkins, but that too is not being verified as when I run the AWS EB environment that has the latest application (according to Jenkins) i’m still seeing the old version. Also I’m unable to figure out the Application version format in the AWS EB plugin in Jenkins. I would like to create a new application version and not update the previous one. Br, Vikram ---
**Author:** ![halkeye](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/halkeye/32/8_2.png) [@halkeye](https://community.jenkins.io/u/halkeye)\ **Post date:** [March 22, 2022, 5:31pm UTC](https://community.jenkins.io/t/deploying-to-aws-elastic-beanstalk-from-jenkins/1880/2 "2022-03-22T17:31:25Z")
as with [CopyOnWriteArrayList Exception when viewing the project from the dashboard after upgarde to 2.332.1 from 2.263.4 - #2 by halkeye](https://community.jenkins.io/t/copyonwritearraylist-exception-when-viewing-the-project-from-the-dashboard-after-upgarde-to-2-332-1-from-2-263-4/1877/2) please update your plugins. It sounds like the plugin is using apis that no longer exist in core. ---
**Author:** ![vikram291194](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/vikram291194/32/940_2.png) [@vikram291194](https://community.jenkins.io/u/vikram291194)\ **Post date:** [March 23, 2022, 5:40am UTC](https://community.jenkins.io/t/deploying-to-aws-elastic-beanstalk-from-jenkins/1880/3 "2022-03-23T05:40:09Z")
Hello sir, I have updated all the plugins that were available for update and also I’m running Jenkins version 2.332.1. After releasing the source code from the AWS CodePipeline in Jenkins I’m facing the below error. Please see the below image ![image](https://europe1.discourse-cdn.com/flex013/uploads/jenkins/original/2X/2/23c535dbea9086c39486cffeb5d277c4186b0f7f.png) ---
**Author:** ![vikram291194](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/vikram291194/32/940_2.png) [@vikram291194](https://community.jenkins.io/u/vikram291194)\ **Post date:** [March 25, 2022, 5:10am UTC](https://community.jenkins.io/t/deploying-to-aws-elastic-beanstalk-from-jenkins/1880/4 "2022-03-25T05:10:59Z")
Hello sir, Is there any solution to this issue? I have already upgraded all the plugins but still the error persists. Br, Vikram ---
**Author:** ![halkeye](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/halkeye/32/8_2.png) [@halkeye](https://community.jenkins.io/u/halkeye)\ **Post date:** [March 25, 2022, 5:26am UTC](https://community.jenkins.io/t/deploying-to-aws-elastic-beanstalk-from-jenkins/1880/5 "2022-03-25T05:26:31Z")
Have you looked for any open bugs for that plugin? Have you reported the bug? I recommend just using the AWS cli ---
**Author:** ![vikram291194](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/vikram291194/32/940_2.png) [@vikram291194](https://community.jenkins.io/u/vikram291194)\ **Post date:** [March 25, 2022, 5:28am UTC](https://community.jenkins.io/t/deploying-to-aws-elastic-beanstalk-from-jenkins/1880/6 "2022-03-25T05:28:45Z")
Okay sir, I will do so and thank you for the suggestion.