[jira] [Commented] (BIGTOP-3630) Some repositories yield to HTTP 403

["Luca Toscano (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BIGTOP-3630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17472780#comment-17472780 ] 

Luca Toscano commented on BIGTOP-3630:
--------------------------------------

I checked the old S3 account, we used "repos.etc.." in there, so we should rename the bucket :(
It seems not possible via S3 UI, the docs suggests to copy data in a new bucket..

[~sekikn] do you have time to do it? Otherwise I can try something using the aws cli :)

> Some repositories yield to HTTP 403 
> ------------------------------------
>
>                 Key: BIGTOP-3630
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-3630
>             Project: Bigtop
>          Issue Type: Bug
>            Reporter: Luca Toscano
>            Priority: Major
>
> Hi everybody,
> at Wikimedia we use reprepro to manage our internal Debian APT repository, in which we sync/copy package from Bigtop's. Today I noticed a weird issue, namely:
> {code}
> aptmethod error receiving 'http://repos.bigtop.apache.org/releases/1.5.0/debian/10/amd64/dists/bigtop/InRelease': '403  Forbidden [IP: 52.216.83.32 80]'
> {code}
> If I swap the config from repos.bigtop.apache.org to repo.bigtop.apache.org.s3.amazonaws.com, everything works fine.
> The value repo.bigtop.apache.org.s3.amazonaws.com comes from the S3 config, and it is the first CNAME of repos.bigtop.apache.org:
> {code}
> $ dig repos.bigtop.apache.org +short
> repo.bigtop.apache.org.s3.amazonaws.com.
> s3-1-w.amazonaws.com.
> s3-w.us-east-1.amazonaws.com.
> 52.216.132.251
> {code}
> Could it be that our new S3 config needs to be called repos.bigtop.apache.org.s3.amazonaws.com (see the extra s - repoS) to make everything working?



--
This message was sent by Atlassian Jira
(v8.20.1#820001)