Amazon S3 error- A conflicting conditional operation is currently in progress against this resource.

This error means that, the bucket was recently deleted and is queued for delete in S3. You must wait until the name is available again.


This error means that, the bucket was recently deleted and is queued for delete in S3. You must wait until the Bucket name is available again.

Kindly note, I received this error when my access-priviliges were blocked. The error means your Operation for creating new bucket at S3 is aborted. There can be multiple reasons for this, you can check the below points for rectifying this error:

  1. Is this Bucket available or is Queued for Deletion
  2. Do you have adequate access privileges for this operation
  3. Your Bucket Name must be unique

P.S: Edited this answer to add more details as shared by Sanity below, and his answer is more accurate with updated information.

You can view the related errors for this operation here. I am editing my asnwer so that correct answer posted below can be selected as correct answer to this question.


Creating a S3 bucket policy and the S3 public access block for a bucket at the same time will cause the error.

Terraform example

resource "aws_s3_bucket_policy" "allow_alb_access_bucket_elb_log" {
  bucket = local.bucket_alb_log_id
  policy = data.aws_iam_policy_document.allow_alb_access_bucket_elb_log.json
}

resource "aws_s3_bucket_public_access_block" "lb_log" {
  bucket = local.bucket_alb_log_id

  block_public_acls   = true
  block_public_policy = true
}

Solution


resource "aws_s3_bucket_public_access_block" "lb_log" {
  bucket = local.bucket_alb_log_id

  block_public_acls   = true
  block_public_policy = true

  #--------------------------------------------------------------------------------
  # To avoid OperationAborted: A conflicting conditional operation is currently in progress
  #--------------------------------------------------------------------------------
  depends_on = [
    aws_s3_bucket_policy.allow_alb_access_bucket_elb_log
  ]
}

Tags:

Amazon S3