Incorporate AWS into your Mendix Development

Incorporate AWS into your Mendix Development | The Big Dev Theory | S5 | Ep.1

Stuart Clark
Amazon Employee
Published Nov 14, 2023
Last Modified Apr 18, 2024
In this episode of The Big Dev Theory on Twitch, we are joined by Ryan Mocke from the Mendix Developer Relations team. Learn how you can secure your Mendix App using the Authentication connector and session-based credentials for robust user data protection. Dive into Sigv4 Headers, understanding their significance for mastering AWS capabilities. Then, get hands-on with Amazon Lambda, effortlessly configuring the AWS Authentication Connector, and seamlessly integrating all of this into your Mendix App. Unleash the potential of advanced image and video analysis at your fingertips, enhancing your Mendix development with AWS expertise!

Links Shared in the stream

  • Check out The community-sourced publication for low-code - https://medium.com/mendix / https://www.mendix.com/developer-center/blog/
  • Browse the documentation for Mendix products, read about latest releases, and make contributions for the Mendix community - https://docs.mendix.com/
Each episode, we chat with AWS partners and bring experts with specialized knowledge in various areas of technology to provide informative and engaging live streams that help developers stay up-to-date with the latest trends and tools.


Stuart Clark, Senior Developer Advocate @ AWS
Adrian SanMiguel, Principal Solutions Architect, Strategic Partner Engagements @ AWS

What is the The Big Dev Theory?

The Big Dev Theory is a live stream broadcast every week on the AWS Twitch channel. Our live streams are designed to help developers learn about the advantages of our partner technologies and AWS, these events provide developers with the opportunity to learn from some of the top minds in the industry and connect with other developers who are working on similar projects. A key part of its mission to help developers build and innovate with confidence.

Any opinions in this post are those of the individual author and may not reflect the opinions of AWS.