I'm having the same issue and since I can't login using withAWS it's blocking our deployments

stevenna you can manually install the needed version of elastic beanstalk using this hpi, that should fix your problem while they work on the solution

https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/aws-java-sdk/aws-java-sdk-elasticbeanstalk/1.12.246-349.v96b_b_f7eb_a_c3c/aws-java-sdk-elasticbeanstalk-1.12.246-349.v96b_b_f7eb_a_c3c.hpi

Thanks griefwar,

I can confirm that, with the elastic beanstalk version linked above the dependencies problems are gone. Going to run a few jobs to see if everything works as expected.

Ciao

Will release a new version to fix this issue?

https://github.com/jenkins-infra/helpdesk/issues/3019 describes the issue that you're seeing. The Jenkins update center data is updated every few minutes from a cached copy of all the Jenkins plugins and their versions. The combination of artifact ID and version number that is used by the most recent release of the AWS elastic beanstalk SDK plugin exceeded the limits of the caching mechanism that is currently being used. That stopped update center data refreshes for all users.

https://github.com/jenkins-infra/update-center2/pull/606 implements a short term workaround to allow update center data refreshes to continue over the weekend. That short term workaround blocks the distribution of the most recent release of the AWS elastic beanstalk plugin so that other Jenkins users can continue to receive update center data refreshes.

Further work is expected early next week to allow the update center to again distribute the most recent release of the AWS elastic beanstalk SDK plugin.

In the interim, users can download the plugin from the Jenkins artifact repository.

Resolved by the latest changes from https://github.com/jenkins-infra/helpdesk/issues/3019

I still see the previous release number on the Jenkins server as shown in the one of attachments file "Screen Shot 2022-06-28 at 10.34.19".

I've tried updating APT package as well as restart or downgrade all plugins of AWS SDK:: *.

Am I missing something here or is it unreleased yet? Im not so familiar with Jenkins issue page yet.

I was able to update the plugin by adding the downloaded `.hpi` file in the Advanced Installation UI page. 

haeyoonj you should also have been able to resolve the issue by clicking the "Check Now" button on the Jenkins Plugin Manager page. The update center data is stored centrally and only downloaded to the Jenkins controller periodically. The "Check Now" button requests an immediate download of the update center data.

markewaite Thanks for sharing it! Finally I was able to see "Update information obtained" time after clicking the "Check Now" button