Just use more than one AWS account!!!! Use Roles to manage any cross-account dependencies.
13 karma · joined August 11, 2016
To back up my first point, the framework owner could easily instruct users to set up a temporary user/role that creates the initial function roles/policies as one-time setup. Then a user/role with only the service-level permissions (Lambda etc.) could manage all the actual resources.
The devs who build these frameworks want them to be super simple to use, otherwise they won't retain users!
Getting 15 ms latency on a brand new TLS connection is nearly impossible over the internet. If you actually check the latency breakdown on your Ping, you'll see the TLS handshake is dominating the API Gateway -> EC2 request.
I'm all for this type of analysis, but too often it isn't apples to apples.
Apple doesn't want everyone to switch to lightning. They are banking that bluetooth will eventually be the 90% even 99% standard among consumers. I tend to agree.