In our AWS migration, we found it necessary to run an FTP server. Yeah, I know — “FTP? In the 20-teens?”. Look, I get it — nobody wants to run an FTP server in this day and age. But it is still a convenient way for partner companies to transfer data to us via automation. This isn’t highly sensitive data; our main concern is keeping the FTP server isolated from our other services so that any vulnerabilities there don’t propagate to more critical systems.
At any rate, we found it surprisingly challenging to build a highly available FTP service in AWS.
Continue reading AWS Adventures, part 2 – high-availability FTP service
After a lot of reading about AWS and the failures that have happened over the years, I’ve come to the conclusion that to be truly resilient against complete AZ failure, you need to have enough capacity running in both AZs to handle the entire load of your application.
Continue reading AWS: hedging against AZ failure
We are in the middle of a massive migration to the AWS cloud. While we are excited by the prospects of ditching a lot of our hardware responsibilities, you can’t make a change this big without some pain.
So far, Snowball has been the biggest source of frustration.
Continue reading AWS Adventures, part 1 – Snowball