You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
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.
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
locked and limited conversation to collaborators
Jun 18, 2020
This issue was closed.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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: