8 ms·

With Software defined networking you don't need the subdomain to do that.

by cobookman 7y ago

wbl 7y ago
Huh? If the DNS doesnt see the bucket name how can it hand back the right IP of where the bucket lives?
tedunangst 7y ago
How does that work? My browser is going to send all requests to the same domain to the same place.
- cobookman 7y ago
  Anycast ip. You have a sole ip address. All traffix routed to nearest PoP. The PoP makes the call on where and how to route the request. Lookup google front end (GFE) whitepaper. Or thd google cloud global load balancer That front end server that lives in the PoP can also inspect the http packets for layer 7 load balancing. https://cloud.google.com/load-balancing/docs/load-balancing-overview https://cloud.google.com/load-balancing/docs/load-balancing-...
  - BillinghamJ 7y ago
    Added to my comment, but basically S3 is not a CDN - it doesn't have PoPs/anycast. They _do_ use anycast and PoPs for the DNS services though. So that's basically how they handle the routing for buckets - but relies entirely on having separate subdomains. What you're saying is correct for Cloudfront though.
    - dlubarov 7y ago
      Presumably Amazon has PoPs for CloudFront; why couldn't S3 share the same infrastructure?
      - wbl 7y ago
        It means two hops not one. S3 gets can be cached but then you have a whole host off issues. Better to get to the origin.
      - BillinghamJ 7y ago
        They could do that, but they have absolutely no incentive to do so - all it would do is cost them more. S3 isn't a CDN and isn't designed to work like one.
    - cobookman 7y ago
      With SDN the PoP would only need to receive the TCP request and proxy TCP acks. Raw data could flow from a different PoP that's closer to DC. Aka user->Closest PoP-> backhaul fiber -> dc->user
BillinghamJ 7y ago
Yeah you basically do. Sure you can reroute the traffic internally over the private global network to the relevant server, but that's going to use unnecessary bandwidth and add cost. By sharding/routing with DNS, the client and public internet deal with that and allow AWS to save some cash. Bear in mind, S3 is not a CDN. It doesn't have anycast, PoPs, etc. In fact, even _with_ the subdomain setup, you'll notice that before the bucket has fully propagated into their DNS servers, it will initially return 307 redirects to https ://<bucket>.s3-<region>.amazonaws.com This is for exactly the same reason - S3 doesn't want to be your CDN and it saves them money. See: https://docs.aws.amazon.com/AmazonS3/latest/dev/VirtualHosting.html https://docs.aws.amazon.com/AmazonS3/latest/dev/VirtualHosti...
- hueving 7y ago
  I'm not sure you understand how anycast works. It would be very shocking if Amazon didn't make use of it and it's likely the reason they do need to split into subdomains. Anycast will pull in traffic to the closest (hop distance) datacenter for a client, which won't be the right datacenter a lot of the time if everything lives under one domain. In that case they will have to route it over their backbone or re-egress it over the internet, which does cost them money.
  - cavisne 7y ago
    AWS in general are not fans of Anycast. Interesting thread from one of their principal engineers on the topic. https://twitter.com/colmmacc/status/1067265693681311744 https://twitter.com/colmmacc/status/1067265693681311744 Google Cloud took a different approach based on their existing GFE infrastructure. It does not really seem to have worked out, there have been a couple of global outages due to bad changes to this single point of failure, and they introduced a cheaper networking tier that is more like AWS.
    - ignoramous 7y ago
      > AWS in general are not fans of Anycast. I don't think that's true. Route53 has been using Anycast since its inception [0]. The Twitter thread you linked simply points out that fault isolation is tricky with Anycast, and so I am not sure how you arrived at the conclusion that you did. [0] https://aws.amazon.com/blogs/architecture/a-case-study-in-global-fault-isolation/ https://aws.amazon.com/blogs/architecture/a-case-study-in-gl...

With Software defined networking you don't need the subdomain to do that.

wbl 7y ago

Huh? If the DNS doesnt see the bucket name how can it hand back the right IP of where the bucket lives?

tedunangst 7y ago

How does that work? My browser is going to send all requests to the same domain to the same place.

cobookman 7y ago
Anycast ip. You have a sole ip address. All traffix routed to nearest PoP. The PoP makes the call on where and how to route the request. Lookup google front end (GFE) whitepaper. Or thd google cloud global load balancer That front end server that lives in the PoP can also inspect the http packets for layer 7 load balancing. https://cloud.google.com/load-balancing/docs/load-balancing-overview https://cloud.google.com/load-balancing/docs/load-balancing-...
- BillinghamJ 7y ago
  Added to my comment, but basically S3 is not a CDN - it doesn't have PoPs/anycast. They _do_ use anycast and PoPs for the DNS services though. So that's basically how they handle the routing for buckets - but relies entirely on having separate subdomains. What you're saying is correct for Cloudfront though.
  - dlubarov 7y ago
    Presumably Amazon has PoPs for CloudFront; why couldn't S3 share the same infrastructure?
    - wbl 7y ago
      It means two hops not one. S3 gets can be cached but then you have a whole host off issues. Better to get to the origin.
    - BillinghamJ 7y ago
      They could do that, but they have absolutely no incentive to do so - all it would do is cost them more. S3 isn't a CDN and isn't designed to work like one.
  - cobookman 7y ago
    With SDN the PoP would only need to receive the TCP request and proxy TCP acks. Raw data could flow from a different PoP that's closer to DC. Aka user->Closest PoP-> backhaul fiber -> dc->user

BillinghamJ 7y ago

Yeah you basically do. Sure you can reroute the traffic internally over the private global network to the relevant server, but that's going to use unnecessary bandwidth and add cost. By sharding/routing with DNS, the client and public internet deal with that and allow AWS to save some cash. Bear in mind, S3 is not a CDN. It doesn't have anycast, PoPs, etc. In fact, even _with_ the subdomain setup, you'll notice that before the bucket has fully propagated into their DNS servers, it will initially return 307 redirects to https ://<bucket>.s3-<region>.amazonaws.com This is for exactly the same reason - S3 doesn't want to be your CDN and it saves them money. See: https://docs.aws.amazon.com/AmazonS3/latest/dev/VirtualHosting.html https://docs.aws.amazon.com/AmazonS3/latest/dev/VirtualHosti...

hueving 7y ago
I'm not sure you understand how anycast works. It would be very shocking if Amazon didn't make use of it and it's likely the reason they do need to split into subdomains. Anycast will pull in traffic to the closest (hop distance) datacenter for a client, which won't be the right datacenter a lot of the time if everything lives under one domain. In that case they will have to route it over their backbone or re-egress it over the internet, which does cost them money.
- cavisne 7y ago
  AWS in general are not fans of Anycast. Interesting thread from one of their principal engineers on the topic. https://twitter.com/colmmacc/status/1067265693681311744 https://twitter.com/colmmacc/status/1067265693681311744 Google Cloud took a different approach based on their existing GFE infrastructure. It does not really seem to have worked out, there have been a couple of global outages due to bad changes to this single point of failure, and they introduced a cheaper networking tier that is more like AWS.
  - ignoramous 7y ago
    > AWS in general are not fans of Anycast. I don't think that's true. Route53 has been using Anycast since its inception [0]. The Twitter thread you linked simply points out that fault isolation is tricky with Anycast, and so I am not sure how you arrived at the conclusion that you did. [0] https://aws.amazon.com/blogs/architecture/a-case-study-in-global-fault-isolation/ https://aws.amazon.com/blogs/architecture/a-case-study-in-gl...