Resolved: Adding MX Record(s) in AWS

on
 Recently, I was migrating MX records from WIX to AWS. I was using GSuite and I was unable to do the same. Then after a little bit of research, I found this stackoverflow link , which helped me resolve the problem. Here is how you should be adding the records in AWS. Record Name: @ Record Type: MX Value: <Priority> <Route Traffic to> example: 10 aspx.alt1.google.com And if you have multiple records, simply add the records in the same text area in the new line and no commas. This will resolve your problem. :)

Azure API Management - Using Client IP Address as the Counter Key for Rate Limiting Policies

on

Hey friends, How are you all?

Today, I am going to share how we can implement Rate Limit Policies and Counter by Client IP Address.

So, let's understand the problem first:

PROBLEM: 

  • We need to implement Rate Limit Policy by Client IP Address on Azure API Management. I followed this article first of all and found that I can use the following piece of code.


  • There was a second problem for me as the requests were coming through cloudflare and hence the client IP address was not available in context.Request.IpAddress

SOLUTION:
  • I was getting IPAddress as 0.0.0.0 in the app insights which is right as per GDPR, I used this link to confirm the client IP address in the pre-prod environments in App Insights.
  • I found that CloudFlare exposes the Client IP Address in the X-Forwarded-For or True-Client-IP Header to expose the client IP Address. Check out the details here.
  • I followed this link to strengethen my understanding on how to use Policy Expressions
  • The final piece: Ultimately, I used the following piece to counter by Client IP Address


Notice, the code in the counter-key, it is prettymuch C# in the razor block. For a single line statement, you can use @() and for multi-line statements, you can use Happy Coding!!!