If you manage many AWS accounts in an enterprise environment, you probably feel the need for better user management and federate it with IdP (in my case with Azure Active Directory). In 2017 AWS has introduced a new way how to federate access – with an AWS SSO service. In this post, I would like to describe some properties of the solution you need to count on.
In case you want to send HTML content as HTTP response directly from .NET Azure Functions, you can use following code snippet to reduce your work.
For hosting a static website on Azure Storage Account with custom domain, you are required to use Azure CDN/Azure Front Door service, but there are limited options to protect your origin from bypassing CDN/WAF. Microsoft recently introduced a killer feature, which enables high-level protection of any origin including Storage Account, AppService or even some service running on VMs.
Caching data with distributed caches like Azure Redis Cache is easy – but how to easily cache whole response from your Web API (response code+body) describes this post.
When you need to run some executable file/console application in cloud, you don’t want to run to take care about a VM/container. A lot of workloads can be made totally serverless with Azure Functions only – with tricks described in this post.