AWS IoT Core now supports caching of responses returned by customer’s Custom Authorizer Lambdas when using HTTP connections

You can now cache responses returned by your Custom Authorizer Lambdas when using AWS IoT Core Custom Authentication workflow for HTTP connections. Customers can now define a caching duration (i.e. refreshAfterInSecs) for responses returned by customers’ custom authorizer lambdas when using long-lived HTTP connections. Customers can set a “refreshAfterInSecs” between 5 mins and 24 hours to reduce custom authorizer lambda invocations. This feature enhancement helps customers reduce their custom authorizer lambda cost and makes the behavior for HTTP match with that of other protocols supported by AWS IoT Core.

AWS IoT Core is a managed cloud service that lets connected devices easily and securely interact with cloud applications and other devices. With Custom Authentication workflow, AWS IoT Core lets you define custom authorizers so that you can manage your own client authentication and authorization. This is useful when you need to use authentication mechanisms other than the ones that AWS IoT Core natively supports. For more information about the natively supported mechanisms, see Client authentication documentation.

You can visit the AWS IoT Core Custom Authentication documentation to learn more.