---
title: "Matt Martz (@martzmakes) | Hashnode"
description: "AWS Community Builder. Read the latest articles by Matt Martz on Hashnode."
url: "https://hashnode.com/@martzmakes"
---

@martzmakes

# Matt Martz

@martzmakes · Burke, VA · Joined October 2020

AWS Community Builder

## Comments

[Thanks!](https://hashnode.com/posts/how-to-automatically-generate-request-models-from-typescript-interfaces/5f9c625a65cd015fab581392/comment/641a0090e592dd06478de2ca#reply-641a15097b483d01e1b3f3f7)

Reply · Article · Mar 21, 2023 · [How to Automatically Generate Request Models from TypeScript Interfaces](https://hashnode.com/posts/how-to-automatically-generate-request-models-from-typescript-interfaces/5f9c625a65cd015fab581392)

[Thanks! I prefer the code-first approach. I hate writing specs and would much rather the code generate them. I talk about this a little bit in the next article: https://matt.martz.codes/openapi-specs-from-cdk-stack-without-deploying-first But I have since moved more towards Event Driven Documentation: https://matt.martz.codes/automate-documenting-api-gateways-in-eventcatalog Both still rely on converting typescript interfaces to json schemas... but in the more recent post I shift to downloading the spec from the deployed version of the API Gateway. Thanks for the feedback though, that's totally a valid approach... just not my preferred one.](https://hashnode.com/posts/how-to-automatically-generate-request-models-from-typescript-interfaces/5f9c625a65cd015fab581392/comment/63d1b73b2086bff3543caee5#reply-63dafa71f5b65869f5efdecc)

Reply · Article · Feb 1, 2023 · [How to Automatically Generate Request Models from TypeScript Interfaces](https://hashnode.com/posts/how-to-automatically-generate-request-models-from-typescript-interfaces/5f9c625a65cd015fab581392)

[No, there aren't any credentials in the DDB key. The IAM policy that the Lambda uses to get read access to DDB includes a constraint that restricts what it can see. In the example above you can see the PK is just simply Tenant#1. The JWT includes the tenant number so the condition in the policy: 'dynamodb:LeadingKeys': \[\`Tenant#${who}\`\], means that when the lambda is invoked where "who" is 1... they'd only see the Tenant#1 records.](https://hashnode.com/posts/lock-down-dynamodb-with-iam-policy-conditions/6006e59c094f2b30301dd952/comment/61c97b5d1de80a7fb227ffb1#reply-61ca35c98787d923bc663318)

Reply · Article · Dec 27, 2021 · [Lock Down DynamoDB with IAM Policy Conditions](https://hashnode.com/posts/lock-down-dynamodb-with-iam-policy-conditions/6006e59c094f2b30301dd952)
