Page MenuHomeFreeBSD

Make EC2 AMIs use portsnap and freebsd-update mirrors hosted in AWS
ClosedPublic

Authored by cperciva on Jun 28 2020, 7:26 PM.
Tags
None
Referenced Files
F151884412: D25498.id73899.diff
Sat, Apr 11, 8:25 AM
F151871923: D25498.id73899.diff
Sat, Apr 11, 6:17 AM
Unknown Object (File)
Wed, Apr 8, 10:28 PM
Unknown Object (File)
Wed, Apr 8, 1:07 PM
Unknown Object (File)
Wed, Apr 8, 8:16 AM
Unknown Object (File)
Mon, Apr 6, 4:02 AM
Unknown Object (File)
Sat, Mar 28, 2:13 PM
Unknown Object (File)
Fri, Mar 27, 7:34 PM
Subscribers

Details

Summary

This adjusts freebsd-update.conf and portsnap.conf files in EC2 AMIs to
point at the new AWS-hosted mirror network.

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Skipped
Unit
Tests Skipped
Build Status
Buildable 32024

Event Timeline

delphij added a subscriber: delphij.

LGTM, but I wonder if it's possible to have AWSDNS/Route53 to do the resolution for the clients since we are already using it?

This revision is now accepted and ready to land.Jun 28 2020, 9:16 PM

We're using route53 for portsnap right now; not for freebsd-update. But yes, I'll be looking into adjusting the existing portsnap DNS records to send traffic to these -- at very least in place of the old portsnap mirrors I've had in EC2 for many years.