#7959 aws s3 mirror broken
Closed: Will Not/Can Not fix 2 months ago by puiterwijk. Opened 2 months ago by einventor.

Hi, I found this document: https://fedoraproject.org/wiki/Infrastructure/Mirroring/Amazon
and we used: http://s3-mirror-us-west-2.fedoraproject.org.s3-website-us-west-2.amazonaws.com/pub/epel/7/x86_64/ for a long time, but since Friday, this mirror stopped working.
http://s3-mirror-us-west-2.fedoraproject.org.s3-website-us-west-2.amazonaws.com/pub/epel/7/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found

Does somebody know what happened with this mirror?


Hi, that document is very old (last change was in 2012), and that was just a proposal.
We did in fact have those same hostnames as a proof of concept for a long while, but recently started to remove that in favor of a setup where we have everything in a single region S3 bucket but fronted by Cloudfront.
As a consequence, we have been removing all the older buckets.
Specific mirror URLs are never regarded as stable, as the only stable endpoint is the mirrorlist URL, and you are strongly suggested to use that rather than point to any specific mirror.
That should automatically find you the closest up-to-date mirror, and additionally gives you additional security protections against various forms of attacks: https://fedoramagazine.org/fedora-secures-package-delivery/.

Metadata Update from @puiterwijk:
- Issue close_status updated to: Will Not/Can Not fix
- Issue status updated to: Closed (was: Open)

2 months ago

I have added a warning to the top of the page to indicate this as well.

Login to comment on this ticket.

Metadata