-
Notifications
You must be signed in to change notification settings - Fork 9.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
aws_cloudfront_distribution: InvalidArgument: The parameter Logging Bucket does not refer to a valid S3 bucket #13381
Comments
hello I am open to work arounds. thanks |
@cat-turner you want something like this:
|
Hey @cat-turner 👋 Thank you for taking the time to file this issue. Given that there's been a few Terraform and AWS Provider releases since you initially filed it, and given the information provided above, can you confirm whether you're still running into this? |
I ran into this issue after referencing my bucket from #....
logging_config {
include_cookies = false
bucket = "${aws_s3_bucket.cdn-website-logs.id}.s3.amazonaws.com"
prefix = "logs/cdn"
#....
} I'm using the current AWS provider; terraform {
required_providers {
aws = {
source = "hashicorp/aws"
version = "~> 5.31.0"
}
}
required_version = "~> 1.6.5"
}
} |
Thank you @appwebtech ! The documentation is not CLEAR at all :-/. They shall add a note to let users know that |
This issue was originally opened by @cat-turner as hashicorp/terraform#24962. It was migrated here as a result of the provider split. The original body of the issue is below.
Hi
According to the docs, we need to specify the logging bucket as
myawslogbucket.s3.amazonaws.com
https://www.terraform.io/docs/providers/aws/r/cloudfront_distribution.html#logging-config-arguments
AWS is planning to deprecate path style access logs in favor of virtual. I am unable to point to the s3 bucket in any other way. Will we need to update this?
https://forums.aws.amazon.com/ann.jspa?annID=6776
https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html
The text was updated successfully, but these errors were encountered: