Multiple aws_s3_bucket with the same bucket name does not generate an error

[hashibot]

This issue was originally opened by @jleclanche as hashicorp/terraform#10085. It was migrated here as part of the provider split. The original body of the issue is below.

---

terraform 0.7.10

I had the following typo'd configuration:

resource "aws_s3_bucket" "example_org_bucket" {
	bucket = "example.org"
	website {
		redirect_all_requests_to = "https://example.net"
	}
}

resource "aws_s3_bucket" "www_example_org_bucket" {
	bucket = "example.org"
	website {
		redirect_all_requests_to = "https://example.net"
	}
}

Terraform did not complain (and even proceeded to do... something?), even though this makes no sense. This was a pretty simple typo, forgetting www. in the second bucket name.

[bflad]

We would like to address the duplicate Terraform resource problem, more generically for all Terraform resources that could be potentially duplicated by certain criteria (such as per-region and per-name). The enhancement that would be available to all Terraform resources, which we could then implement the Terraform AWS Provider, can be tracked upstream in the Terraform Plugin SDK: hashicorp/terraform-plugin-sdk#224.

[bflad]

Hi folks 👋 Thank you for submitting this and this is an excellent use case of somewhere that Terraform and the Terraform AWS Provider could be much more helpful since in many cases they have enough information to return an error upfront during planning instead of unexpected behavior during apply.

I believe this falls under the provider-wide enhancement proposal of #14394, so by adding this link here it will add a reference to that issue so we can include it as a use case when thinking about the implementation details. Since this is likely something we will want more broadly across many resources, I'm going to close this particular issue to consolidate discussions, efforts, and prioritization on the topic while the reference would serve as the cue to make this specific resource one of the initial implementations. I would suggest those 👍 upvoting and subscribing here to do so on #14394 so we can appropriately gauge interest. Please feel free to provide feedback there.

Thanks again!

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!