[lug] Ubuntu repository access on private AWS VPC?

[David Leonard]

You could use a route table with a NAT gateway or your own firewall running
in an instance with an igw.

Thanks!
David Leonard -- 303.245.4509
AppliedTrust -- https://appliedtrust.com

--

Please excuse my brevity as I am responding via mobile to get you a faster
response.

On Tue, Mar 27, 2018, 8:05 PM Bear Giles <bgiles at coyotesong.com> wrote:

> I've seen references to this but haven't found actual instructions (except
> for S3 and Dynamo DB)....
>
> I have some AWS EC2 instances that have a public interface. I have a few
> that don't have a public interface at all - they're only accessible from
> the first systems.
>
> Think webapp server (public) and database (private). Or even reverse proxy
> (public), webapp server (private), database (super-private).
>
> The problem is getting Ubuntu packages onto the private instances. I've
> been manually copying a few extra packages, e.g., for the database, but
> that's not sustainable when I want to apply bug fixes, etc. Supposedly
> there's a way to set up your private VPC so it can see extremely selective
> external resources without setting up a full gateway but I haven't found
> any details.
>
> I am aware of 'endpoints', but only for S3 and DynamoDB.
>
> The Ubuntu repository is a HTTP server (
> http://us-east-1.ec2.archive.ubuntu.com/ubuntu/) or could be an FTP
> server.
>
> It looks like another approach is using 'apt-transport-s3' to point to an
> S3 bucket containing the packages, but I don't think that's what people
> were referring to. I don't know that for sure though.
>
> Bear
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> Join us on IRC: irc.hackingsociety.org port=6667 channel=#hackingsociety
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lug.boulder.co.us/pipermail/lug/attachments/20180328/527de9ef/attachment.html>