<div dir="ltr">It's a /56 per VPC, and a /64 per subnet.<div><br></div><div>Seems reasonable to me.</div><div><br></div><div><a href="https://docs.aws.amazon.com/vpc/latest/userguide/get-started-ipv6.html">https://docs.aws.amazon.com/vpc/latest/userguide/get-started-ipv6.html</a><br></div><div><br></div><div>Dave</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, 28 Nov 2021 at 20:54, Michael Thomas <<a href="mailto:mike@mtcc.com">mike@mtcc.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<p><br>
</p>
<div>On 11/27/21 2:44 PM, Fletcher Kittredge
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div><br>
</div>
<a href="https://www.theregister.com/" target="_blank">The
Register</a> says: <a href="https://www.theregister.com/2021/11/24/aws_claims_monumental_step_forward/" target="_blank">AWS claims 'monumental step forward'
with optional IPv6-only networks</a><br clear="all">
<div><br>
</div>
<br>
</div>
</blockquote>
<p>I was reading their howto yesterday and it seems they are only
allocating a /64? Why? <br>
</p>
<p>I guess I just don't get the point of the VPC in the first place.
I get the firewall aspect but it seem to be more than that.</p>
<p>Mike<br>
</p>
</div>
</blockquote></div>