List out required ENV variables for examples?

[sheats]

I was working through chapter 2 trying to deploy the samples but didn't see a list of all the required ENV variables. When I ran make deploy serverless lists them out with warnings but would be great to have an example env file to fill out.

[brianz]

@sheats Thanks for this! I was in the middle of doing this work and stalled out. Check out the https://github.com/brianz/serverless-design-patterns/tree/feature/ch2-updates branch. I'm working at getting all the chapters cleaned up like this...but this should at least get you going for ch 2 and 3.

[brianz]

Good question...for the purposes of these examples for the book, it's easiest to simply use your default VPC. The reason is that it's faster and easier...so you can focus on just the code and wiring up everything else. If you were going to do something like this for real, I'd highly suggest creating dependent resources like VPC outside of serverless. The reason is that it's a supporting sub-system which normally isn't tied to your serverless code exclusively, and doesn't change that often. You certainly could do this 100% with the Serverless framework, but there is a *lot* to creating a new VPC with CloudFormation. Once you do all of that, your `sls deploy` commands start to take longer (since it's resolving diffs in a now larger stack) and you impact other resources within the VPC which aren't managed by Serverless. If you want an easy way to create VPCs, I'd recommend checking out Stacker or the newly release CDK <https://aws.amazon.com/blogs/developer/working-with-the-aws-cloud-development-kit-and-aws-construct-library/> from AWS.

…

On Wed, Sep 25, 2019 at 6:28 PM Tom Propst ***@***.***> wrote: I see that the branch mentioned here has been merged into master. I also see that we need to have separately created a VPC from the example environment variables. Is there any reason we can't or shouldn't use serverless to do that? I may have missed it but up through chapter 2 I didn't see this mentioned. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#14?email_source=notifications&email_token=AABOQVXM742BLQPWVAXYWHDQLP6ZDA5CNFSM4FD4II6KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7T2ZBY#issuecomment-535276679>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABOQVWRV6TVIMUO3JYYTY3QLP6ZDANCNFSM4FD4II6A> .