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
Unknown Object (File)
Wed, Jun 25, 8:33 AM
Unknown Object (File)
Tue, Jun 17, 7:54 PM
Unknown Object (File)
Sun, Jun 15, 6:51 PM
Unknown Object (File)
Wed, Jun 11, 8:40 AM
Unknown Object (File)
Mon, Jun 9, 5:00 AM
Unknown Object (File)
Thu, Jun 5, 7:39 PM
Unknown Object (File)
Wed, Jun 4, 7:31 PM
Unknown Object (File)
Tue, Jun 3, 5:30 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 Not Applicable
Unit
Tests Not Applicable

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.