Lambda deploy from Eclipse not working: AWS ResourceConflictException

0

Hello,

Please see below the steps that return an AWS error in local Eclipse:

  • I installed AWS Toolkit for Eclipse, on Eclipse Jee 2018-12

  • When I installed it 2 years ago, it worked fine and the lambda project was deployed in the Lambda Service directly from Eclipse without any configuration from my side; congratulations for this clean deploy configuration !

  • An year ago this deploy started not to complete successfully: it worked only until the transfer of the eclipse archive in S3, without installation in Lambda Service. I have to do the installation of the S3 archive from the Management Console -> Lambda console, manually.

  • The Error Cause: An update is in progress for resource: arn:aws:lambda:us-east-2:<removed>:function:RekonAddUser (Service: AWSLambda; Status Code: 409; Error Code: ResourceConflictException; Request ID: 408040a5-f1fe-4ba0-b251-df0c2fc8fe9c) This cause was thrown wile I did not have any other interaction with that resource !

  • The message was: Failed to upload project to Lambda

  • The error was: com.amazonaws.eclipse.core.exceptions.AwsActionException: The operation cannot be performed at this time. An update is in progress for resource: arn:aws:lambda:us-east-2:<removed>:function:RekonAddUser (Service: AWSLambda; Status Code: 409; Error Code: ResourceConflictException; Request ID: 408040a5-f1fe-4ba0-b251-df0c2fc8fe9c) at com.amazonaws.eclipse.lambda.upload.wizard.UploadFunctionWizard.doFinish(UploadFunctionWizard.java:115) at com.amazonaws.eclipse.core.plugin.AbstractAwsJobWizard$1.run(AbstractAwsJobWizard.java:35) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63) Caused by: com.amazonaws.services.lambda.model.ResourceConflictException: The operation cannot be performed at this time. An update is in progress for resource: arn:aws:lambda:us-east-2:<removed>:function:RekonAddUser (Service: AWSLambda; Status Code: 409; Error Code: ResourceConflictException; Request ID: 408040a5-f1fe-4ba0-b251-df0c2fc8fe9c) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleErrorResponse(AmazonHttpClient.java:1639) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeOneRequest(AmazonHttpClient.java:1304) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:1056) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:743) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:717) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.execute(AmazonHttpClient.java:699) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.access$500(AmazonHttpClient.java:667) at com.amazonaws.http.AmazonHttpClient$RequestExecutionBuilderImpl.execute(AmazonHttpClient.java:649) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:513) at com.amazonaws.services.lambda.AWSLambdaClient.doInvoke(AWSLambdaClient.java:2654) at com.amazonaws.services.lambda.AWSLambdaClient.invoke(AWSLambdaClient.java:2630) at com.amazonaws.services.lambda.AWSLambdaClient.executeUpdateFunctionCode(AWSLambdaClient.java:2514) at com.amazonaws.services.lambda.AWSLambdaClient.updateFunctionCode(AWSLambdaClient.java:2490) at com.amazonaws.eclipse.lambda.upload.wizard.util.UploadFunctionUtil.performFunctionUpload(UploadFunctionUtil.java:134) at com.amazonaws.eclipse.lambda.upload.wizard.UploadFunctionWizard.doFinish(UploadFunctionWizard.java:111) ... 2 more

  • The Session Data: eclipse.buildId=4.10.0.I20181206-0815 java.version=1.8.0_60 java.vendor=Oracle Corporation BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_GB Framework arguments: -product org.eclipse.epp.package.jee.product Command-line arguments: -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.jee.product

Thank you,

  • Per guidelines, I've removed the account IDs from the ARNs in this comment.

asked a year ago337 views
1 Answer
0

Hello,

I understand that you are having issue when trying to deploy lambda function, using AWS Toolkit for Eclipse. You mentioned that it was working before, and about a year ago the process was incomplete, when deploying lambda via aws toolkit. Currently the process is incomplete and only working until the transfer of eclipse archive to S3. The error message is as follows:

“The operation cannot be performed at this time. An update is in progress for resource… Error Code: ResourceConflictException...”

We already have an issue open with AWS Toolkit Eclipse SDK team, regarding this issue:

https://github.com/aws/aws-toolkit-eclipse/issues/242

At this time, we do not have an ETA on when or if this issue will be fixed. Please use above official Github repository issue to track progress and provide any feedback.

You are already using proper workaround to deploy lambda function, by manually accessing zip file uploaded in S3 bucket. Alternately, you can also build Lambda deployment package using Eclipse (without toolkit), and manually upload the JAR file to deploy Lambda function code.

AWS
SUPPORT ENGINEER
Isha_K
answered a year ago
  • Hello,

    Thanks a lot for the answer. I will follow that github issue.

    Because you are just update the AWS Toolkit, please consider also another issue that I just added: Lambda deploy from Eclipse not working: JAXBException. The effect of this issue is that the archive does not leave the local drive anymore. I have to upload to Lambda directly from local drive.

    Thank you,

    Mihai

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions