Skip to content
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 #24962

Closed
cat-turner opened this issue May 15, 2020 · 3 comments

Comments

@cat-turner
Copy link

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

@danieldreier
Copy link
Contributor

Thanks for reporting this! I think that this is an issue to be addressed in the AWS Terraform provider, rather than in core. This GitHub repository is for issues specifically about Terraform core, and issues specific to individual providers are tracked in other repositories. I'm going to label it as such, and the HashiBot will shortly migrate it over to the AWS provider. Please feel free to re-open this if they determine that it is indeed an issue that needs to be addressed in Terraform core.

@ghost
Copy link

ghost commented May 18, 2020

This issue has been automatically migrated to hashicorp/terraform-provider-aws#13381 because it looks like an issue with that provider. If you believe this is not an issue with the provider, please reply to hashicorp/terraform-provider-aws#13381.

@ghost ghost closed this as completed May 18, 2020
@ghost
Copy link

ghost commented Jun 18, 2020

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Jun 18, 2020
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants