Live data from Hacker News

AWS Transfer for SFTP – Fully Managed SFTP Service for Amazon S3

aws.amazon.com

21–30 of 158 posts

Re: AWS Transfer for SFTP – Fully Managed SFTP Service for Amazon S3

#21

I'd be curious how this handles all the posix cases not well suited to object storage. Renaming a folder than has a million files/folders inside is a single operation in SFTP, but 2 million operations on S3. Does it handle writing at arbitrary offsets within a file? Does it download the file first then let you start writing? What about just writing a few bytes at the beginning of a large existing file and then closin…

I don't work on the S3 team so I can't answer all these questions but relative to the "2 million operations on S3" question I can point out that S3 now has batch operation support: https://aws.amazon.com/about-aws/whats-new/2018/11/s3-batch-...

Re: AWS Transfer for SFTP – Fully Managed SFTP Service for Amazon S3

#22
post #2

Enterprises will love this. There are so many legacy app flows kicked off via sftp/scp file drops. Being able to hook into those via lambda events on the associated S3 bucket will create a whole ecosystem of enterprise spaghetti for years to come.

Spaghetti as a service, delicious

Welcome to the real world.

Re: AWS Transfer for SFTP – Fully Managed SFTP Service for Amazon S3

#23

I'd be curious how this handles all the posix cases not well suited to object storage. Renaming a folder than has a million files/folders inside is a single operation in SFTP, but 2 million operations on S3. Does it handle writing at arbitrary offsets within a file? Does it download the file first then let you start writing? What about just writing a few bytes at the beginning of a large existing file and then closin…

I don't work on the S3 team so I can't answer all these questions but relative to the "2 million operations on S3" question I can point out that S3 now has batch operation support: https://aws.amazon.com/about-aws/whats-new/2018/11/s3-batch-...

I think the point being that when a filesystem the mv is atomic and just updates an inode but on S3 those operations can take place on thousand of different machines.

Re: AWS Transfer for SFTP – Fully Managed SFTP Service for Amazon S3

#25
post #7
post #4

We currently pay $250/month through some small vendor for hipaa compliant sftp hosting (that we transfer a whopping 50kb on a weekly basis). I always felt like it was a rip off, but azure/aws didn't have their own version. And I'm loathe to manage a VM. PaaS is my sugar bear. My eyes lit up when I saw this. We're an azure shop, but I'm not afraid to use AWS for limited cases. Then I saw - $.30/hr (so, $214/mo). Reall…

HIPAA compliance, even on AWS is extremely expensive. I believe the best vendor to get HIPAA (someone correct me if I'm wrong) is to go with Google Cloud. Last time I checked did not charge any extra for HIPAA BAA signing. Edit: I stand corrected on this, AWS no longer requires dedicated hardware for BAA HIPAA: Sorry I didn't look this up, I had old information. https://aws.amazon.com/blogs/apn/aws-hipaa-program-upda…

AWS is IMO the best vendor if you are looking to for HIPAA compliant cloud computing. Our bills are higher than they would be for a non-medical application, but nothing astronomical. Programmer time is still way more expensive.

Re: AWS Transfer for SFTP – Fully Managed SFTP Service for Amazon S3

#28

Earlier quoted context omitted.

I don't know about comically easy, but should be doable to have some sort of shared frontend. $214 (even $100) is a really beefy vm, though. I wonder whats provisioned and why.

Nothing beefy, probably, but as for HIPAA compliance, AFAIK, you need to sign several specific contracts with your provider and blahblahblah, probably they're just billing you for the incovenience and for having the HIPAA seal. "I'm HIPAA, the rest aren't, just pay for it".

You have to sign a single business associate agreement (BAA) depending on the nature of the business you are working with. These are usually boilerplate contracts around 2-3 pages long and full of legalese.

It is uncommon for someone to charge you for signing a BAA. It is very common to tie these plans into enterprise only pricing. This is terrible because it adds unnecessary costs to the medical system (which get passed onto consumers) and it completely shuts out smaller players from entering the marketplace. (Cue me side eyeing every single error tracking software SaaS currently on the market who wants to start at 5K a year for their 'small' plan - get real guys)

Re: AWS Transfer for SFTP – Fully Managed SFTP Service for Amazon S3

#29

Earlier quoted context omitted.

The only downside is whitelisting but not on the SFTP server-side. Many enterprises restrict egress SFTP (usually for security reasons) so you need to provide IPs and they can’t frequently change because it can take enterprise network admins quite some time to deal with all of the bureaucracy and change control. That said, I wouldn’t be surprised if modern networking gear can handle CNAMEs but there’s no guarantee th…

It's less whether the gear is modern and more about the layer that it operates at. A network firewall doesn't see the DNS name that an internal system looked up in order to make an outbound connection. It just sees the source/destination IP/port. Processing a rule based on source/destination IP or CIDR and port is very fast, and all happens locally. Trying to make that device handle rules by IP address is pretty tric…

I wonder if you could use the DNS resolution cache itself to do the reverse lookup. As long as the DNS cache lasted at least as long as the TTL, it should work.

Re: AWS Transfer for SFTP – Fully Managed SFTP Service for Amazon S3

#30
post #3

There are a handful of services out there that do this, I know because I've needed it on multiple occasions. It's nice that Amazon is providing it in house now, but it just reminds of me the last time I went to re:invent and walked through the vendor area and thought about how many of these companies are four dev cycles away from Amazon producing a baked in competitor. Hard to make a B To B Amazon tool these days.

Dave Winer:

http://scripting.com/stories/2007/04/04/coexistingWithPlatfo...

Sometimes developers choose a niche that's either directly in the path of the vendor, or even worse, on the roadmap of the vendor. In those cases, they don't really deserve our sympathy. It's almost like a game of PR, there's no way you're not going to have a fight on your hands.

Further discussed by Joel Spolsky

https://www.joelonsoftware.com/2009/06/10/platform-vendors/

Post reply on HN