That Remote Life: An IT Manager’s Perspective / Chapter 1

Wayne Armstrong • February 26, 2021
Connect with us

 

Historically, working from home used to be a pipe dream that people, who were putting 60-80 hours in the office with driving to and from, would always talk about. I do not think that most people would have ever thought that this “Pipe Dream” would not only become a reality, but to have it forced upon us because of a global pandemic.


Without delving into the global impact that this pandemic caused in our Industry, from clients to IT providers, I thought I would talk about the challenges and successes that I have experienced as a parent, an employee and a leader in IT.


CHAPTER 1: ROUTINE


Often taken for granted, this past year has really hit home the basic human need for routine. I guess it did not occur to me the difference between getting up and getting ready to be out in public was so different from getting up and getting ready for your home. I come from a very traditional Irish family where my Mother’s day was built around us children and our home and I never stopped to think about her routine and how she managed herself in that environment. 


I found myself getting ready for my day out in public and the office, but to then only sit down at the Computer I normally sit at when I get home at the end of my day. I experience a very pronounced feeling of something missing. Almost like you got ready for a night out and your mind is set, for then to be told it’s cancelled. A profound feeling to be sure and a confusing one which let me know I didn’t have the experience to know how to handle it.



Here I am, getting to spend more time in my home and with my Family which I always dreamed of and realizing I was woefully not prepared for it. So the first person I thought of was my Mother, so I called her. 


TO BE CONTINUED... 


 

By Shawn Akins October 20, 2025
October 20, 2025 — Early today, Amazon Web Services experienced a major incident centered in its US‑EAST‑1 (N. Virginia) region. AWS reports the event began around 12:11 a.m. PT and tied back to DNS resolution affecting DynamoDB , with mitigation within a couple of hours and recovery continuing thereafter. As the outage rippled, popular services like Snapchat, Venmo, Ring, Roblox, Fortnite , and even some Amazon properties saw disruptions before recovering. If your apps or data are anchored to a single cloud, a morning like this can turn into a help‑desk fire drill. A multi‑cloud or cloud‑smart approach helps you ride through these moments with minimal end‑user impact. What happened (and why it matters) Single‑region fragility: US‑EAST‑1 is massive—and when it sneezes, the internet catches a cold. Incidents here have a history of wide blast radius. Shared dependencies: DNS issues to core services (like DynamoDB endpoints) can cascade across workloads that never directly “touch” that service. Multi‑cloud: practical resilience, not buzzwords For mid‑sized orgs, schools, and local government, multi‑cloud doesn’t have to mean “every app in every cloud.” It means thoughtful redundancy where it counts : Multi‑region or multi‑provider failover for critical apps Run active/standby across AWS and Azure (or another provider), or at least across two AWS regions with automated failover. Start with citizen‑facing portals, SIS/LMS access, emergency comms, and payment gateways. Portable platforms Use Kubernetes and containers, keep state externalized, and standardize infra with Terraform/Ansible so you can redeploy fast when a region (or a provider) wobbles. (Today’s DNS hiccup is exactly the kind of scenario this protects against.) Resilient data layers Replicate data asynchronously across clouds/regions; choose databases with cross‑region failover and test RPO/RTO quarterly. If you rely on a managed database tied to one region, design an escape hatch. Traffic and identity that float Use global traffic managers/DNS to shift users automatically; keep identity (MFA/SSO) highly available and not hard‑wired to a single provider’s control plane. Run the playbook Document health checks, automated cutover, and comms templates. Then practice —tabletops and live failovers. Many services today recovered within hours, but only teams with rehearsed playbooks avoided user‑visible downtime. The bottom line Cloud concentration risk is real. Outages will happen—what matters is whether your constituents, students, and staff feel it. A pragmatic multi‑cloud stance limits the blast radius and keeps your mission‑critical services online when one provider has a bad day. Need a resilience check? Akins IT can help you prioritize which systems should be multi‑cloud, design the right level of redundancy, and validate your failover plan—without overspending. Let’s start with a quick, 30‑minute review of your most critical services and RPO/RTO targets. (No slideware, just actionable next steps.)
By Shawn Akins October 13, 2025
How a Zero-Day in GoAnywhere MFT Sparked a Ransomware Wave—and What Mid-Sized IT Leaders Must Do Now
By Shawn Akins October 13, 2025
The clock is ticking: Learn your options for Windows 11 migration, Extended Security Updates, and cost‑smart strategies before support ends.
More Posts