cjol / boilerplate-sam-typescript Goto Github PK

I want to experiment and document how to use this with a local dynamodb instance for offline development.

Right now I'm deploying everything with full IAM admin access. That's not ideal for restricted users. Ideally I'd like to split this into two steps

1. Policy required to set up the stack initially (may need to be admin because of lambda IAM user creation)
2. Policy required to update the stack with new code (should be possible to restrict more)

I'm not sure whether we're actually using SAM at all. We're using sam-proxy for local development, and we're gradually dropping SAM resources in favour of CloudFormation resources anyway to have more granular control.

Right now, shared resources (like probably the domain Hosted Zone, but also
the S3 deployment bucket etc) are either not created in CFN, or are created
multiple times.

We could solve this by having a separate "projectsetup" CFN template, which
creates shared resources, and then each developer can connect to those. It
might be a little messy to share ARNs, so that will need thinking about.

Right now we create a serverless table but we don't use it for anything. It would be good to include an example of that.