Re: Global networking change in our AWS accounts

2021-11-17 Thread Antonio Terceiro
On Wed, Nov 17, 2021 at 01:05:01PM +0100, Bastian Blank wrote: > Hi > > On Wed, Nov 17, 2021 at 08:01:55AM -0300, Antonio Terceiro wrote: > > For ci, we are working with the security team on testing embargoed > > security updates, and for that we need a unique IP address, because it > > will be

Re: Global networking change in our AWS accounts

2021-11-17 Thread Tianon Gravi
On Wed, 17 Nov 2021 at 09:12, Noah Meyerhans wrote: > However, based on the responses, it is evident that this change will > cause sufficient problems for enough people that we should reconsider > its timing. To be clear, there is absolutely no pressure from AWS or > any other entity to reduce

Re: Global networking change in our AWS accounts

2021-11-17 Thread Noah Meyerhans
On Wed, Nov 17, 2021 at 07:45:31AM -0800, Ross Vandegrift wrote: > > We like to do a global change to the way the network is setup on the new > > AWS accounts. The goal is to reduce the amount of global IPv4 addresses > > to a minimum, as those are an increasingly rare comodity nowadays. > >

Re: Global networking change in our AWS accounts

2021-11-17 Thread Ross Vandegrift
Hi Bastian, On Tue, Nov 16, 2021 at 10:16:38PM +0100, Bastian Blank wrote: > We like to do a global change to the way the network is setup on the new > AWS accounts. The goal is to reduce the amount of global IPv4 addresses > to a minimum, as those are an increasingly rare comodity nowadays.

Re: Global networking change in our AWS accounts

2021-11-17 Thread Bastian Blank
Hi On Wed, Nov 17, 2021 at 08:01:55AM -0300, Antonio Terceiro wrote: > For ci, we are working with the security team on testing embargoed > security updates, and for that we need a unique IP address, because it > will be added to an ACL on the security repository side. You mean via

Re: Global networking change in our AWS accounts

2021-11-17 Thread Antonio Terceiro
On Tue, Nov 16, 2021 at 10:16:38PM +0100, Bastian Blank wrote: > Hi folks > > We like to do a global change to the way the network is setup on the new > AWS accounts. The goal is to reduce the amount of global IPv4 addresses > to a minimum, as those are an increasingly rare comodity nowadays. >

Re: Global networking change in our AWS accounts

2021-11-17 Thread Lucas Nussbaum
On 17/11/21 at 10:30 +0100, Bastian Blank wrote: > Hi > > On Tue, Nov 16, 2021 at 10:31:12PM +0100, Lucas Nussbaum wrote: > > I'm surprised by this: what is the motivation? Have we been asked to use > > less IPv4 addresses? > > Yes, you get at most two. We can also remove the NAT one, as access

Re: Global networking change in our AWS accounts

2021-11-17 Thread Bastian Blank
Hi On Tue, Nov 16, 2021 at 10:31:12PM +0100, Lucas Nussbaum wrote: > I'm surprised by this: what is the motivation? Have we been asked to use > less IPv4 addresses? Yes, you get at most two. We can also remove the NAT one, as access to Debian's infrastructure is capable of working IPv6-only,