3 ms·

So this looks very cool. Great job... but... It would be pretty simple to wrap this up and automate it easily using a Terraform file. All it requires is an S3

• Mizza 10y ago
  ...but why? We already use CloudFormation under the hood for the API Gateway, though to be honest I'm seriously considering moving away from it because it's so fickle. There are also some security disadvantages and other problems from using CloudFormation for maintaining Lambda functions, plus you lose out on all the extensive functionality we provide. We're pretty damn well battle tested to avoid that stuff now.
  • movedx 10y ago
    Well, by using Terraform you're opening up the door to using other Lambda offerings as they pop up from other venders (and become supported by Terraform, of course.) CloudFormation is nice, and in your case it makes perfect sense given you're offering a Lambda specific service, but in the grand scheme of things I don't believe it's the best solution "all round." What you're offering is awesome, for the record. I think it's a good idea, I think it's powerful, I think it's fast. It's a good idea and you should keep working on it. However, it's a single, small Terraform file worth of work from my perspective.