AWS Error Message: A conflicting conditional operation is currently in progress against this resource

193
votes

I'm getting this error intermittently.

I have a program that uses the java aws sdk and loads over the 10s of thousands of small files to s3. I see this error intermittently.

Could not find any helpful answer after doing a quick search on the internet.

Note the calling program is single threaded. The underlying aws java sdk does seem to use worker threads.

Status Code: 409, AWS Service: Amazon S3, AWS Request ID: 75E16E8DE2193CA6, AWS Error Code: OperationAborted, AWS Error Message: A conflicting conditional operation is currently in progress against this resource. Please try again., S3 Extended Request ID: 0uquw2YEoFamLldm+c/p412Lzd8jHJGFBDz3h7wN+/4I0f6hnGLkPMe+5LZazKnZ
    at com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java:552)
    at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:289)
    at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:170)
    at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:2648)
    at com.amazonaws.services.s3.AmazonS3Client.createBucket(AmazonS3Client.java:578)
    at com.amazonaws.services.s3.AmazonS3Client.createBucket(AmazonS3Client.java:503)
9
javaamazon-web-servicesamazon-s3
Are you trying to put objects into S3 and then immediately read them? – jamieb
@jamieb, actually no, not at this time. – user1172468
I wish I had an answer for you. Are you trying to rewrite the same keys in rapid succession? S3 is built on an "eventually consistent" model where PUTs need time to settle. – jamieb
@jamieb, thanks for spending brain cycles but the answer provided by Guy is correct I think. I think in my code I retry to create a bucket -- expecting to fail gracefully -- it does like 99.99% of the time and sometimes it throws this error. Again really appreciate you taking the time to help me out. Cheer! – user1172468
Thanks for the follow-up. Good luck! – jamieb

9 Answers

483
votes

I got the same error message, when I did following:

  1. created a bucket - it went by default to US region (used AWSCLI)

  2. realized, the bucket shall go to EU region and deleted it (used AWS console)

  3. (few minutes later) tried to create the bucket, specifying the EU region

At step 3, AWS console has shown me the error message from title of your question.

So I guess, that the bucket in US was deleted, but there are possibly some synchronization processes, which are taking time. And I hope, that waiting few hours I will find the bucket name again available for creation - this time in proper (EU) region.

FIX :- Edit: About an hour later, my attempt to create the bucket (in EU region) succeeded.

41
votes

For all others who stumble upon this thread from google, as 1st result in search for this error message:

If you deleted bucket, to recreate in new region, do not wait "manually" until this background sync will be complete, instead put a small bash script to run and retry your needed bucket creation every 5 seconds or so.

Example:

#!/bin/bash 
RESULT=2 
until [  $RESULT -eq 0 ]; do
    aws s3 mb s3://your.bucket.name --region us-west-2
    RESULT=$?
    sleep 5 
done 
echo "Bucket created!"

it will retry the "create bucket" operation for you, every few seconds (depend on 'sleep' ) and as soon as it's possible - will create it for you, so no one can steal your bucket name by mistake :)

hope it helps :)

23
votes

The request in your example is to create a bucket. If you are trying to create too many buckets or replace buckets, it is not healthy.

Note that you have a limit of 100 buckets for an account (see here). EDIT: Now this limit is a "soft limit" and you can increase it if needed.

Also note that a creation of a bucket takes time and:

...it is not appropriate to make bucket create or delete calls on the high availability code path of your application...

It is better to create your buckets once and then, you can put as many objects that you like in your existing buckets (or even a single one).

Anyway, when working with a system that is bound to fail any now and then, you should be able to handle errors and slow down your process when receiving such an error. See more details in AWS Docs.

12
votes

This error usually occurs when a Bucket is deleted and a new bucket is created in the same name as the old bucket.

I believe we would need to wait for certain amount of time until we can create a new bucket in the same name.

10
votes

Simple and straightforward: Change the new bucket name or wait 1 hour.

0
votes

You also get this message when you have more than 100 buckets in the account already. There is a soft limit of 100 buckets.

0
votes

Finally, AWS now has a clear answer in their own knowledge center, see https://aws.amazon.com/premiumsupport/knowledge-center/s3-conflicting-conditional-operation/.

I've just deleted a bucket (since S3 bucket names are globally unique and I need to create the same bucket in another AWS account) and my script that creates a bucket with the same name fails with the same error. So I have to be patient and wait for an hour.

Just as a confirmation: After around one hour, I can successfully create a bucket with the same name as the deleted bucket.

0
votes

I got the error running a Cloud Formation template.

Turns out the IAM role the EC2 assumed that I was running the CFN template on didn't have permission to create S3 buckets.

Either provide IAM access, or use a different IAM role by doing an AWS Configure or programmatically assume a role with necessary permission to create an S3 Bucket.

-1
votes

Change your bucket name or wait. I waited less than 30 minutes for mine. I did not need to change the name and I couldn't change it as I was set on it - it had to match my already existing domain name for a static website that I was looking to host. Anyway, in less than 30 minutes it was created automatically.