Live data from Hacker News

Migrating From AWS to FB

instagram-engineering.tumblr.com

91–94 of 94 posts

Re: Migrating From AWS to FB

#91
post #20
post #19

Called it, five years ago: http://www.web2expo.com/webexny2009/public/schedule/detail/9... Run in multiple clouds from day one. Take the pain. It gives you flexibility. Basic vendor management 101.

This article mentions nothing about latency.

They mentioned AWS direct connect which helps to reduce latency.

Re: Migrating From AWS to FB

#92

Earlier quoted context omitted.

I'm confused by this. S3 GET requests are the cheapest request type, and getting the images out would just cost you the bandwidth involved. Maybe you're mixing things up with Glacier?

GET Requests are cheap But I was thinking of bandwidth costs to get things out of S3 entirely and do a complete outmigration. But the prices there have come down quite a bit since I last checked.

Bandwidth costs of a one-off transfer out would be a lot less than they were already paying to serve those images out of S3 to the public.

Re: Migrating From AWS to FB

#93
post #9
post #8

Earlier quoted context omitted.

I think it has more to do with the fact that there are a standard series of private IP blocks.

Right, but if everyone used IPv6 there would be no need to use non-routeable private IPs for anything, you could just use non-conflicting IPv6 addresses and not route them.

Service-net (https://github.com/mesosphere/service-net/) is a proof-of-concept for service routing and discovery with IPv6 and DNS. The underlying mechanism is similar -- IP tables is used for routing and load-balancing -- but DNS and IPv6 tunneling are integrated as well.

One downside of IPv6 on AWS is that the IPv6 tunneling protocol -- protocol number 41 -- is only available in VPCs. The EC2 classic network allows only 3 IP protocols -- TCP, UDP and ICMP -- to pass through it.

Re: Migrating From AWS to FB

#94
post #72

Earlier quoted context omitted.

We're small, comparatively - 20-30 servers max - and we need to get in to VPC for a new cluster that requires static internal IPs. (Reboot an EC2 Classic instance and you may get a different 10.x address.) In any case, the migration is daunting even at our size, although our devops team size is 1. I do wish they had VPC when we started.

You could also just attach EIPs and use those, right?

In an incredibly late reply - EIPs are public-facing, I need internal IPs for fastest possible LAN routing.
Post reply on HN