serverless-localstack VS MAMIP

Great point. Fully agree that providing a first-class local development experience is critical to the overall story of application development frameworks.

I guess the main difference is that frameworks like Serverless provide a great experience if you fully buy into their way of doing things (i.e., implement your application assets in the Serverless YAML DSL, etc), whereas LocalStack is a generic platform that works on the API emulation level, hence integrates with most tooling out of the box.

Making the switch from Serverless to, say, AWS CDK, or AWS SAM, or Architect framwork may not be as seamless - however, for each of these frameworks you can always run the local emulation natively on LocalStack. This can help reduce the overall vendor lock-in effect that a lot of application development frameworks come with.

In fact, LocalStack also provides an integration with Serverless [0] - among many other tools [1].

[0] https://github.com/localstack/serverless-localstack

For anyone else who wants to see the role permissions themselves, look here: https://github.com/z0ph/MAMIP/blob/master/policies/AWSSupportServiceRolePolicy

Reverted 22 hours ago: https://github.com/z0ph/MAMIP/commit/b6f696cebc7b9a4f71dd34c...

- https://github.com/z0ph/MAMIP/blob/master/DEPRECATED.json

Saw it referenced at https://github.com/z0ph/MAMIP/commit/acb0ede and Google is failing me.

That page includes an explanation as to why the finding did not result in a deprecation of a managed policy. All other findings from the report not already surfaced and discussed on our documentation page are associated with deleted or deprecated policies (presumably still available in the MAMIP repo, leading to why your work referenced some managed policies that are no longer applicable).