My Tech Rambling

One of the application development team had a requirement to read emails sent to a specific email address so that they can parse the same and act on them. We use Office365 and app team wanted to open up IMAP ports and the Security team and Email Admin teams had said "NO". I didn't want to travel back in time. The easier way would be to use Microsoft Flow with HTTP. We use TYK API Gateway on our production network which is accessible on the internet and it is being used, but you can also any of your internet accessible endpoints like the app by itself or AWS API Gateway, etc. Also, keep in mind the licensing requirements imposed by Microsoft for using Flow. From what I read, one should be able to do this from a shared mailbox as well. Here are the high-level steps that I recommended the app team 1) Login into the Flow . 2) Create a new Flow ( Automated Flow from Blank ) 3) Provide a name for the flow and select when a new email arrives as the trigger. ...

TYK API Gateway  does not provide a simple integration for invoking Lambda and I remember reading Kong does.  In any case, this is about how to securely integrate TYK with Lambda - Or in general, consuming internal/private AWS Api gateway in your application. Here are the high-level steps  1) Create a VPC Endpoint for API Gateway - with a security group that allows 443 from the TYK Node/application nodes ( Security-group in the source is the best choice). Note the Endpoint ID (used  for API Gateway Resource Policy) and DNS Name (not the individual AZ but the generic one - to be used for API definition on TYK API Gateway ) 2) Create a Private AWS API gateway - with a nicely tied security group and the resource policy would look something like this ( replace highlighted place holders with your configurations)  {     "Version": "2012-10-17",     "Statement": [         {             "...