Hi Matthew,
As long as you use a DNS hostname instead of an IPv4 literal address,
things should work fine for both local apps or tethered/hotspot access
because Telstra's DNS servers can do DNS64. Locally on the iPhone you can
use a literal IPv4 too because iOS will do local address translation
The person that got access to their system was not an AWS employee when the
breach happened. The person got access via a misconfigured server/system
that wasn't Amazon's fault.
See the original court case for details:
http://regmedia.co.uk/2019/07/29/capital_one_paige_thompson.pdf
This is the
I'm not sure if the Megaport Direct Connect is any different to a regular
AWS Direct Connect, but a friend of mine has successfully used a regular
AWS Direct Connect that they extended into their EC2 VPC and assigned IP
addresses to their instances from their own /28 range.
The subnet has a Route
Hi Giles,
Do you have a traceroute and/or MTR output that you could include?
Do you see packet loss to IP addresses listed on
http://ec2-reachability.amazonaws.com/ as well? If so, can you include
traceroutes/MTR for those too please?
Andras
On Tue, Jan 30, 2018 at 11:34 AM, Giles Pollock
