cj-zhukov commented on PR #18747:
URL: https://github.com/apache/datafusion/pull/18747#issuecomment-3562267468

   > > > It looks like the `nyc-tlc` bucket is no longer publicly accessible. 
Anonymous ListBucket and GetObject requests now return AccessDenied, which 
makes the example fail even with `--no-sign-request`:
   > > > ```shell
   > > >  aws s3 ls s3://nyc-tlc/  --no-sign-request
   > > > ```
   > > > 
   > > > 
   > > >     
   > > >       
   > > >     
   > > > 
   > > >       
   > > >     
   > > > 
   > > >     
   > > >   
   > > > I updated the example to use a test Parquet file uploaded to a 
user-controlled S3 bucket instead.
   > > 
   > > 
   > > If the CI is currently running this example without errors, the address 
should be valid — am I missing something? 🤔
   > 
   > I might be missing something here, but I wasn’t able to access the 
`s3://nyc-tlc` bucket from my machine - even
   > 
   > ```shell
   > aws s3 ls s3://nyc-tlc/ --no-sign-request 
   > ```
   > 
   > returns `AccessDenied`.
   > 
   > One possibility is that CI is running the example with temporary AWS 
credentials in the environment, so the request becomes signed, which would 
explain why it still works there.
   > 
   > To confirm whether the bucket is still publicly accessible, could you 
please try running the same `aws s3 ls` command on your side?
   > 
   > If it is public, I will revert my change; if not, we can keep the example 
using a user-controlled bucket to avoid confusion for others.
   
   I'm reverting my changes related to `nyc-tlc` because it was on my end 
(https://github.com/awslabs/open-data-registry/issues/1418)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to