3 ms·
I like Heroku. I use it. I suppose maybe I'm a possible customer for these guys, but I just don't care about their nitpicks or glib / empty twitter quotes. Li
by duxup 6y ago
I like Heroku. I use it.
I suppose maybe I'm a possible customer for these guys, but I just don't care about their nitpicks or glib / empty twitter quotes.
Like I have a login for Heroku... it wasn't hard to make but apparently it was for them, that kinda makes me wonder about them.
Meanwhile their example is the opposite of Heroku, super opaque:
>The documentation says to create a new AWS IAM role with credentials for automation.
Oh just jump in the "create a new AWS IAM role with credentials for automation" canon and fly off to AWS land? I've worked with AWS plenty and man it's not been fun. I'm sure someone who knows thinks that's a trivial step, but I don't do it often enough to be sure of what is going on / be all that comfortable with it.
That kinda "here's a link to some documentation for a vague step" (that they don't time....) is why I use Heroku...
- gagege 6y agoIAM is never fun, even if you work with it a lot. You always end up forgetting something and, come security audit time, you find out that people have been creating tons of policies that are just like "s3::*"