Platform engineering, system design and infrastructure shape.
38 items · all topics
When would you scale vertically instead of horizontally?
Go vertical when the bottleneck doesn't split: database buffer cache, cache memory, network bandwidth on one node, a single-threaded lock. Go horizontal when the work partitions cleanly. The real question isn't which is better, it's whether the thing that's saturated can be divided across machines at all.
What happens if an Auto Scaling instance never becomes healthy?
Auto Scaling terminates and replaces an instance that never passes health checks, which is fine once and expensive in a loop. How long you burn depends on the grace period, the check thresholds, and which health check type the group is actually using. The fix is working out why it's unhealthy: usually startup config, a wrong health endpoint, or a grace period shorter than boot time.
Two engineers changed the same Terraform file and Git reports a conflict. How do you resolve it?
Resolve the text conflict, then prove the result is actually correct with terraform validate and a plan. A clean Git merge only means the file parses in a human's head, it says nothing about whether the merged config destroys a database.
Your deployment system needs to know exactly which Git commit is running in production. How do you design that?
Stamp the commit SHA into the artifact at build time and expose it at runtime. Build once per commit, tag and deploy by digest, and serve a /version endpoint, so the answer to "what's live?" comes from the running process itself, not from a pipeline log someone has to go dig up.
Your 5 GB monorepo has code, binaries, Terraform and Helm charts, and clones are slow. What do you do?
Measure what the 5 GB actually is: big blobs, deep history, and a wide tree are three different problems with three different fixes. Work through them in order of cost, artifacts out of Git, binaries into LFS, partial clone and sparse checkout for developers, and treat splitting the repo as the last resort rather than the first idea.
Your organization wants production deployments to be reproducible six months later. How does Git help?
Git pins the source exactly and that's all it pins. Real reproducibility also needs locked dependencies, versioned infrastructure, immutable artifacts, and a stored record linking a deployment to its digest, plus keeping the actual artifact, because rebuilding it later is rarely byte-identical.
Nobody knows which Git branch or tag corresponds to production. How would you fix the release process?
Establish one unbroken chain of identity from commit to running process, then make the pipeline the only way anything reaches production. Start by discovering what's actually deployed today, you can't design a release process around a system you can't describe.
A compliance review finds that an existing Amazon EBS volume attached to a production EC2 instance is unencrypted. The data on the volume must be encrypted at rest with an AWS KMS key. Which sequence of steps achieves this?
You cannot turn encryption on for an existing EBS volume in place. The supported path is to snapshot it, copy the snapshot with encryption enabled, create a new volume from the encrypted copy, and swap it onto the instance.
A company uses AWS Organizations with all features enabled. For compliance reasons, workloads may only run in two approved AWS Regions. Account administrators in member accounts currently hold the AdministratorAccess policy. The company must prevent resources from being created in any other Region. What should a solutions architect do?
A service control policy is the only control that an account administrator cannot remove, because it caps what identities in a member account may do no matter what their IAM policies say. IAM policies and permissions boundaries can both be edited by the very administrators you are trying to constrain.
A public web application runs on Amazon EC2 instances behind an Application Load Balancer and is fronted by Amazon CloudFront. The application has been targeted by SQL injection attempts and by volumetric network floods. A solutions architect must reduce exposure to both. Which TWO actions should the architect take?
These are two different attacks and they need two different controls. AWS WAF inspects HTTP requests and stops injection attempts, while AWS Shield Advanced adds managed protection and cost protection against large network floods. Security groups and network ACLs operate below the layer where SQL injection is visible.
An ecommerce application sends order events to a processing service. During sales events the processing service is overwhelmed and drops orders. Orders for a given customer must be processed in the sequence they were submitted, and no order may be processed twice. Which solution meets these requirements?
Two requirements in the stem, ordering and no duplicates, point at exactly one service. An SQS FIFO queue guarantees first-in-first-out delivery within a message group and provides exactly-once processing through deduplication. A standard queue gives neither.
A colleague asks what a Terraform provider actually is, given that Terraform can manage AWS, GitHub and PagerDuty without knowing anything about them. What is the accurate answer?
A provider is a plugin that Terraform downloads and runs. It defines the resource and data source types for one platform and makes the API calls that create, read, update and destroy them.
A company runs a business-critical application in one AWS Region. The disaster recovery plan requires a recovery time objective of 10 minutes and a recovery point objective of 1 minute in a second Region. The company wants to avoid paying for a full duplicate of the production fleet. Which disaster recovery strategy should a solutions architect choose?
RTO and RPO in minutes rule out backup and restore and pilot light, because both require standing infrastructure up before traffic can move. Warm standby keeps a scaled-down copy always running, which is what buys minutes instead of hours without paying for a second full fleet.
A media company stores original video files in an Amazon S3 bucket in us-east-1. Regulators require that a copy of every new file exists in a second AWS Region within 15 minutes of upload, and that no file can be permanently deleted by mistake. Which TWO actions should a solutions architect take?
Cross-Region Replication copies new objects to a bucket in another Region automatically, and versioning is its prerequisite as well as the control that makes deletion recoverable. The pair answers both halves of the requirement with one dependency between them.
A content management application runs on Amazon EC2 Linux instances spread across three Availability Zones. All instances must read and write the same set of files using standard file system semantics, and the storage must grow automatically as content is added. Which storage solution should a solutions architect recommend?
Multiple Linux instances, multiple Availability Zones, shared file system semantics and automatic growth describe Amazon EFS exactly. EBS attaches to a single Availability Zone, and S3 is object storage without file system semantics.
A company is migrating a Windows application to AWS. The application requires shared storage accessed over the SMB protocol, with Windows NTFS permissions and integration with the company's Active Directory. Which AWS service meets these requirements?
SMB, NTFS permissions and Active Directory together name exactly one AWS service. Amazon FSx for Windows File Server is the managed Windows file system, and the other FSx variants and EFS all serve different protocols.
A multiplayer game server runs on Amazon EC2 instances behind Network Load Balancers in three AWS Regions. Players connect over UDP. The company needs to route each player to the lowest-latency healthy Region, to fail over within seconds if a Region becomes unhealthy, and to publish a fixed set of IP addresses that players' firewalls can allow. Which solution meets these requirements?
UDP, static IP addresses and fast regional failover all point at AWS Global Accelerator rather than CloudFront. Global Accelerator gives you anycast static IPs, carries traffic over the AWS backbone, and reroutes without waiting for DNS to expire anywhere.
Deployment Strategies Explained: Choosing the Right Approach for Your Production Systems
Deploying to production is risky. This guide breaks down the most common deployment strategies with visual animations, real-world examples, and practical advice on when to use each approach.
Stop Learning Every AWS Service - Start With These 20
AWS has hundreds of services, but you don't need to know them all. Learn which 20 services actually matter for real projects and how to think about AWS architecture like a pro.
10 AWS and DevOps Roles That Matter in 2026 - What Each One Actually Does
Not all AWS and DevOps roles are the same. From Cloud Engineers to Platform Engineers to SREs, each role has different responsibilities. Here's what companies actually expect from each one and where they fit in modern organizations.
Will AI Replace DevOps and AWS Engineers? What You Should Actually Focus On
AI is not replacing DevOps and AWS engineers. But it is changing what the work looks like. Here's the realistic answer about AI's impact and exactly what you should focus on to remain valuable in 2026 and beyond.
AWS Well-Architected Framework: What You Actually Need to Understand
The AWS Well-Architected Framework is a proven approach to evaluating and improving cloud architectures. Learn the six pillars and how to apply them to build systems that are secure, reliable, efficient, and cost-effective.
Linux for DevOps: The Commands You Actually Use, and When to Reach for Them
A day of real Linux work comes down to a few dozen commands. This guide covers what each one actually tells you and the gotchas that trip people up. It ends with the command sequences to run when a box is slow, a disk is full, or a service refuses to start.