What I dont get is that AWS SAM uses a toml file as a parameter configuration artifact when CloudFormation uses a json file to basically do the same thing. They're not compatible, in my case I have to use both. One for local development and one that is used on my online CodePipeline.
![AWS re:Invent 2017: [REPEAT] Serverless Authentication and Authorization: Identity M (SRV403-R)](http://i.ytimg.com/vi/VZqG7HjT2AQ/mqdefault.jpg)
36:55 Globals
37:49 Policy Templates
39:06 Best Practices 1
41:13 Best Practices 2
What I dont get is that AWS SAM uses a toml file as a parameter configuration artifact when CloudFormation uses a json file to basically do the same thing. They're not compatible, in my case I have to use both. One for local development and one that is used on my online CodePipeline.
anyone has those slides?? looks rich.
Is it normal that I cannot see the policy_templates.json?
6:24 At 1.8 GB, you get two cores....good to know!