user

OVO Tech Blog

Our journey navigating the techosphere


Tagaws
Featured

aws technology Production Engineering devops open source lambda python slack

Building a simple serverless Slack bot for exporting channel messages as a timeline.

Posted on .

Moving fast and making things. This post has two goals - to share the story of a quick tool we created to solve a problem, and share a template that can be adapted easily for any Slack bot slash command to run a Python script in AWS Lambda.…

Featured

aws technology devsecops infosec networking Production Engineering devops

We made AWS cheaper, safer and more accountable - here’s how!

Posted on .

A high level overview of the problems we found with our AWS account architecture and how we solved them…

Featured

Production Engineering devops devsecops aws gcp

Cloud Networking

Posted on .

A Shared Network Connecting cloud projects together and to on-prem services is a standard problem of organisations. At OVO we use the 10.0.0.0/8 CIDR block for our internal network. This range is split into subnets for each office, AWS or GCP project, or on-pr…

Featured

Production Engineering devops aws networking

Using Route53 Resolver Rules

Posted on .

At OVO we have many cloud projects which need connectivity to services in our datacenter. We have VPNs setup to securely route connections between projects and on-prem services. One issue with this configuration is name resolution within AWS VPCs. The DHCP op…

Featured

stepfunctions lambda aws step function

Orchestrating Serverless - a step in the right direction

Posted on .

This blog post looks at our experience of using AWS Step Functions to help us migrate customers into a new OVO energy platform.…

Featured

IaC Production Engineering aws terraform devops

Complexity in Infrastructure as Code

Posted on .

As a high level concept Infrastructure as Code (IaC) is a well established practice that is helping to improve the consistency and quality of infrastructure deployments. However IaC, just like all other code, can be overly complex, use poor conventions, and can build tech debt.…