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)
Thu, Oct 9, 1:45 AM
Unknown Object (File)
Wed, Oct 8, 3:54 PM
Unknown Object (File)
Sun, Oct 5, 1:06 AM
Unknown Object (File)
Mon, Sep 29, 9:39 AM
Unknown Object (File)
Thu, Sep 18, 7:10 AM
Unknown Object (File)
Sep 11 2025, 3:57 AM
Unknown Object (File)
Sep 6 2025, 5:11 AM
Unknown Object (File)
Sep 3 2025, 9:51 AM
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.