堆栈内存溢出
  简体   繁体   English

无法在Terraform中创建新的S3存储桶

[英]Unable to create new s3 bucket in terraform

 原文  2019-07-07 04:19:30  2   1    amazon-web-services/ amazon-s3/ terraform/ terraform-provider-aws

问题描述

I'm attempting to create a new s3 bucket and getting a conflict though I know the bucket name is new, unique, and has been many hours (8+) since that name was in use. 我正在尝试创建一个新的s3存储桶，但遇到冲突，尽管我知道存储桶名称是新的，唯一的，并且自使用该名称以来已经过了几个小时（超过8个）。 Details attached. 附上详细信息。 I've even tried with a new name that I know was never a bucket in my account (and likely never a bucket). 我什至尝试使用一个新名称，我知道我的帐户中从未有过这样的名字（而且可能永远也没有）。

The name in the logs below is made up and not the one I was using, which was unique and namespaced to my domain. 以下日志中的名称是组成的，而不是我使用的名称，该名称是我域的唯一名称空间。

If I use the aws s3 cli to make the bucket (ie aws s3 mb s3://{same-bucket-name} --region us-east-2 ) where {same-bucket-name} is the name of the bucket I want to create, it works fine. 如果我使用aws s3 cli来创建存储桶（例如aws s3 mb s3://{same-bucket-name} --region us-east-2 ），其中{same-bucket-name}是{same-bucket-name}我要创建，它工作正常。 

2019-07-07T00:12:19.463-0400 [DEBUG] plugin.terraform-provider-aws_v2.18.0_x4: 2019/07/07 00:12:19 [DEBUG] Trying to create new S3 bucket: "my-unique-s3-bucket-name"
2019-07-07T00:12:19.464-0400 [DEBUG] plugin.terraform-provider-aws_v2.18.0_x4: 2019/07/07 00:12:19 [DEBUG] [aws-sdk-go] DEBUG: Request s3/CreateBucket Details:
2019-07-07T00:12:19.464-0400 [DEBUG] plugin.terraform-provider-aws_v2.18.0_x4: ---[ REQUEST POST-SIGN ]-----------------------------
2019-07-07T00:12:19.464-0400 [DEBUG] plugin.terraform-provider-aws_v2.18.0_x4: PUT /my-unique-s3-bucket-name HTTP/1.1
2019-07-07T00:12:19.464-0400 [DEBUG] plugin.terraform-provider-aws_v2.18.0_x4: Host: s3.us-east-2.amazonaws.com
2019-07-07T00:12:19.464-0400 [DEBUG] plugin.terraform-provider-aws_v2.18.0_x4: User-Agent: aws-sdk-go/1.20.12 (go1.12.5; darwin; amd64) APN/1.0 HashiCorp/1.0 Terraform/0.12.2
2019-07-07T00:12:19.464-0400 [DEBUG] plugin.terraform-provider-aws_v2.18.0_x4: Content-Length: 153
2019-07-07T00:12:19.464-0400 [DEBUG] plugin.terraform-provider-aws_v2.18.0_x4: Authorization: AWS4-HMAC-SHA256 Credential=MYCREDS/20190707/us-east-2/s3/aws4_request, SignedHeaders=content-length;host;x-amz-acl;x-amz-content-sha256;x-amz-date, Signature=b5acd2dbcaf09eda51b4ea8448f1991d26c8eb8249a85e7ac28044864df377b9
2019-07-07T00:12:19.464-0400 [DEBUG] plugin.terraform-provider-aws_v2.18.0_x4: X-Amz-Acl: public-read
2019-07-07T00:12:19.464-0400 [DEBUG] plugin.terraform-provider-aws_v2.18.0_x4: X-Amz-Content-Sha256: 70cae86320841ea73b0bdc759f99920c7caa405e61af2742575750c6586272c9
2019-07-07T00:12:19.464-0400 [DEBUG] plugin.terraform-provider-aws_v2.18.0_x4: X-Amz-Date: 20190707T041219Z
2019-07-07T00:12:19.464-0400 [DEBUG] plugin.terraform-provider-aws_v2.18.0_x4: Accept-Encoding: gzip
2019-07-07T00:12:19.464-0400 [DEBUG] plugin.terraform-provider-aws_v2.18.0_x4:
2019-07-07T00:12:19.464-0400 [DEBUG] plugin.terraform-provider-aws_v2.18.0_x4: <CreateBucketConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/"><LocationConstraint>us-east-2</LocationConstraint></CreateBucketConfiguration>
2019-07-07T00:12:19.464-0400 [DEBUG] plugin.terraform-provider-aws_v2.18.0_x4: -----------------------------------------------------
2019-07-07T00:12:19.697-0400 [DEBUG] plugin.terraform-provider-aws_v2.18.0_x4: 2019/07/07 00:12:19 [DEBUG] [aws-sdk-go] DEBUG: Response s3/CreateBucket Details:
2019-07-07T00:12:19.697-0400 [DEBUG] plugin.terraform-provider-aws_v2.18.0_x4: ---[ RESPONSE ]--------------------------------------
2019-07-07T00:12:19.697-0400 [DEBUG] plugin.terraform-provider-aws_v2.18.0_x4: HTTP/1.1 409 Conflict
2019-07-07T00:12:19.697-0400 [DEBUG] plugin.terraform-provider-aws_v2.18.0_x4: Connection: close
2019-07-07T00:12:19.697-0400 [DEBUG] plugin.terraform-provider-aws_v2.18.0_x4: Transfer-Encoding: chunked
2019-07-07T00:12:19.697-0400 [DEBUG] plugin.terraform-provider-aws_v2.18.0_x4: Content-Type: application/xml
2019-07-07T00:12:19.697-0400 [DEBUG] plugin.terraform-provider-aws_v2.18.0_x4: Date: Sun, 07 Jul 2019 04:12:19 GMT
2019-07-07T00:12:19.697-0400 [DEBUG] plugin.terraform-provider-aws_v2.18.0_x4: Server: AmazonS3
2019-07-07T00:12:19.697-0400 [DEBUG] plugin.terraform-provider-aws_v2.18.0_x4: X-Amz-Id-2: v5M1x31BcVCS4DLIgqmCR4KRHipO3ZRbTSXF1PCS9+q9nyT8O5/3s04Z22o8t4x8JZ0HF9HWkO4=
2019-07-07T00:12:19.697-0400 [DEBUG] plugin.terraform-provider-aws_v2.18.0_x4: X-Amz-Request-Id: 835B636D828335A1
2019-07-07T00:12:19.697-0400 [DEBUG] plugin.terraform-provider-aws_v2.18.0_x4:
2019-07-07T00:12:19.697-0400 [DEBUG] plugin.terraform-provider-aws_v2.18.0_x4:
2019-07-07T00:12:19.698-0400 [DEBUG] plugin.terraform-provider-aws_v2.18.0_x4: -----------------------------------------------------
2019-07-07T00:12:19.698-0400 [DEBUG] plugin.terraform-provider-aws_v2.18.0_x4: 2019/07/07 00:12:19 [DEBUG] [aws-sdk-go] <?xml version="1.0" encoding="UTF-8"?>
2019-07-07T00:12:19.698-0400 [DEBUG] plugin.terraform-provider-aws_v2.18.0_x4: <Error><Code>OperationAborted</Code><Message>A conflicting conditional operation is currently in progress against this resource. Please try again.</Message><RequestId>835B636D828335A1</RequestId><HostId>v5M1x31BcVCS4DLIgqmCR4KRHipO3ZRbTSXF1PCS9+q9nyT8O5/3s04Z22o8t4x8JZ0HF9HWkO4=</HostId></Error>
2019-07-07T00:12:19.698-0400 [DEBUG] plugin.terraform-provider-aws_v2.18.0_x4: 2019/07/07 00:12:19 [DEBUG] [aws-sdk-go] DEBUG: Validate Response s3/CreateBucket failed, attempt 0/25, error OperationAborted: A conflicting conditional operation is currently in progress against this resource. Please try again.
2019-07-07T00:12:19.698-0400 [DEBUG] plugin.terraform-provider-aws_v2.18.0_x4:  status code: 409, request id: 835B636D828335A1, host id: v5M1x31BcVCS4DLIgqmCR4KRHipO3ZRbTSXF1PCS9+q9nyT8O5/3s04Z22o8t4x8JZ0HF9HWkO4=
2019-07-07T00:12:19.698-0400 [DEBUG] plugin.terraform-provider-aws_v2.18.0_x4: 2019/07/07 00:12:19 [WARN] Got an error while trying to create S3 bucket my-unique-s3-bucket-name: OperationAborted: A conflicting conditional operation is currently in progress against this resource. Please try again.
2019-07-07T00:12:19.698-0400 [DEBUG] plugin.terraform-provider-aws_v2.18.0_x4:  status code: 409, request id: 835B636D828335A1, host id: v5M1x31BcVCS4DLIgqmCR4KRHipO3ZRbTSXF1PCS9+q9nyT8O5/3s04Z22o8t4x8JZ0HF9HWkO4=
2019-07-07T00:12:19.698-0400 [DEBUG] plugin.terraform-provider-aws_v2.18.0_x4: 2019/07/07 00:12:19 [TRACE] Waiting 10s before next try

1 个解决方案

解决方案1
 1  2019-07-07 07:41:20

If the bucket did previously exist then there is an indeterminate amount of time before that bucket name is released. 如果存储桶以前确实存在，那么释放该存储桶名称之前的时间不确定。

Unfortunately the AWS docs aren't very specific here: 不幸的是， AWS文档在这里不是很具体：

Important 重要

If you want to continue to use the same bucket name, don't delete the bucket. 如果您想继续使用相同的存储桶名称，请不要删除该存储桶。 We recommend that you empty the bucket and keep it. 我们建议您清空水桶并保留它。 After a bucket is deleted, the name becomes available to reuse, but the name might not be available for you to reuse for various reasons. 删除存储桶后，该名称可重新使用，但是由于各种原因，该名称可能不可用。 For example, it might take some time before the name can be reused, and some other account could create a bucket with that name before you do. 例如，重用该名称可能要花费一些时间，而其他帐户可能需要先使用该名称创建存储桶。

You can talk to AWS support to confirm what's happening (and check that another AWS account doesn't have the bucket) but ultimately you just need to wait. 您可以与AWS支持人员联系，以确认发生了什么（并检查另一个AWS账户没有存储桶），但最终您只需要等待即可。 If the S3 bucket matches a domain name that you control and you intend to use it for website hosting and someone else already has that S3 bucket then there is a process for getting that bucket name back to you, just as there is with CloudFront CNAMEs which are also globally unique. 如果S3存储桶与您控制的域名匹配，并且您打算将其用于网站托管，并且其他人已经拥有该S3存储桶，则有一个过程可以将该存储桶名称找回给您，就像CloudFront CNAME一样。在全球范围内也是独一无二的。

You should also be able to check if the bucket name is available by running the following command : 您还应该能够通过运行以下命令来检查存储桶名称是否可用： 

aws s3api head-bucket --bucket [bucket name]

Ages back when we briefly tried deleting S3 buckets in test environments over night (along with everything else) we would occasionally see this error for over 48 hours while sometimes the bucket name was available again within a few hours. 早在我们短暂尝试在夜间（连同其他所有操作）在测试环境中删除S3存储桶时，我们就可以偶尔在48小时以上的时间内看到此错误，而有时存储桶名称会在几个小时内再次可用。 Unfortunately, AWS provide no guarantees here. 不幸的是，AWS在此不提供任何保证。

暂无
暂无

声明:本站的技术帖子网页，遵循CC BY-SA 4.0协议，如果您需要转载，请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 无法使用 terraform 创建带有版本控制的 s3 存储桶 - Unable to create a s3 bucket with versioning using terraform 重命名 Terraform（但不是 S3）中的 s3 存储桶会导致创建然后销毁？ - Renaming s3 bucket in Terraform (but not S3) causes create then destroy? S3存储桶已删除，无法检索地形状态 - Unable to retrieve terraform state as S3 bucket deleted 无法对齐导入的 S3 存储桶地形配置 - Unable to align imported S3 bucket terraform configuration 如何将旧 S3 存储桶中的 Terraform 状态移动到新 S3 存储桶？ - How can I move Terraform state in an old S3 bucket to a new S3 bucket? Terraform 尝试创建 s3 存储桶策略，尽管它存在 - Terraform tries to create s3 bucket policy although it exists 如何使用 terraform 在亚马逊 S3 存储桶中创建文件夹 - How to create a folder in an amazon S3 bucket using terraform 为什么terraform会在s3桶里创建一个空目录？ - Why does terraform create an empty directory in the s3 bucket? 使用 powershell 在 s3 存储桶中创建一个新文件夹 - Create a new folder in s3 bucket with powershell Terraform aws - 将更改用于创建同名 s3 存储桶的模块删除 s3 存储桶并重新创建它 - Terraform aws - Will changing the module for creating s3 bucket of same name delete the s3 bucket and re-create it
相关标签
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM