Maintaining multiple accounts in AWS is an utter pain. If you have effectively separated your accounts for things like Dev/Test, Production that's not too bad, 2 IAM users, with 2FA shouldn't be too difficult. However, if you throw into that, separating operations infrastructure (build and deployment services, Monitoring, alerting, etc), then think about customer separation, … Continue reading Opinionated Approach to AWS Account Separation
Delegating Subdomain management in Route53
One of the common patterns in AWS setup is to use different "accounts" for different functions in the business. These account then get "consolidated" when you're charged (the exorbitant) the fees for your services. This presents a problem when you need to have externally accessible services, that live under a single domain. One way around … Continue reading Delegating Subdomain management in Route53
FaaS are NOT cheaper
This is a little bit of a frustration of mine. I'm hearing this more and more often, as an argument to rewrite into one of those platforms. However, it's simply not true. It's a different pricing model, that has definite benefits in a lot of usecases, but NOT all. To be clear, with the right … Continue reading FaaS are NOT cheaper
AWS Loadbalancer Logs and Lambda – Part 3 – .NET Core Parsing
Lambda Log Parsing Series: AWS Loadbalancer Logs and Lambda – Part 1 – Background AWS Loadbalancer Logs and Lambda – Part 2 – AWS Setup AWS Loadbalancer Logs and Lambda - Part 3 - .NET Core Parsing When AWS Lambda started support .NET Core back in December last year, it made the barrier to entry for … Continue reading AWS Loadbalancer Logs and Lambda – Part 3 – .NET Core Parsing
AWS Loadbalancer Logs and Lambda – Part 2 – AWS Setup
Lambda Log Parsing Series: AWS Loadbalancer Logs and Lambda – Part 1 – Background AWS Loadbalancer Logs and Lambda – Part 2 – AWS Setup AWS Loadbalancer Logs and Lambda – Part 3 – .NET Core Parsing You only need 2 things setup in order to analyze the logs. Elastic Search cluster Load balancer logs … Continue reading AWS Loadbalancer Logs and Lambda – Part 2 – AWS Setup
AWS Loadbalancer Logs and Lambda – Part 1 – Background
Lambda Log Parsing Series: AWS Loadbalancer Logs and Lambda – Part 1 – Background AWS Loadbalancer Logs and Lambda – Part 2 – AWS Setup AWS Loadbalancer Logs and Lambda – Part 3 – .NET Core Parsing If you're hosting in AWS, you're likely using an EC2 Load balancer (Application or Classic), and if you're running … Continue reading AWS Loadbalancer Logs and Lambda – Part 1 – Background
Introducing Grok.NET
What is grok? it's a well established way of parsing, using Regular Expressions, files with single lines (e.g. Log files). Why Create a .NET version? Speed, the ability to use it in AWS Lambda, and because dotnetcore is my preferred language. Syntax Performance? So far, I'm seeing ~0.0002ms for complex patterns sure AWS ELB logs. … Continue reading Introducing Grok.NET
