Urgent.News

What's breaking now, across thousands of outlets.

Tech

How I Cut a Days-Long Malware-Scanning Build to Under an Hour

A build that used to take days of console work now takes one Terraform apply, in under an hour. And when the policy changes, it no longer means a rebuild. Here's how I got there, and what real environments taught me along the way. The problem: the requirements kept moving Every file that enters a secure network has to be scanned before anyone uses it. My team calls the system that does this the…

A multi-day malware scanning build has been reduced to an hour-long process using Terraform. The system automatically scans all files entering a secure network before they are used. Initially, the washing machine had to be shared across all enclaves, but later it was designed to be either shared or per-enclave based on the policy.

GuardDuty Malware Protection for S3 scans new objects in a landing bucket and tags the result. Two AWS Lambda functions in private subnets handle the transfer of clean files and quarantine of those that cannot be scanned. An Amazon EventBridge rule sends the result to these Lambda functions, and Amazon CloudWatch alarms monitor for Lambda errors.

The code is built using a single Terraform module, allowing for easy deployment in shared or individual enclave accounts. Guardrails were implemented to exempt the GuardDuty scan role from access denials, and VPC endpoints were added to handle private subnets. A test virus, the EICAR test file, was uploaded after every deployment to ensure the pipeline was working correctly.

Using Terraform has resulted in faster reviews, as reviewers can now read the code and plan instead of looking at screenshots. The default template for every new enclave has been created, resulting in faster deployment times and increased trust from customers.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

What can happen after a payment platform already received your payout

A factual account of a USD 330 hold, what freelancers can do next, and why I built a small awareness site with open comments.

  • Freelance freelancer's USD 330 payout held after receipt by Skydo on Nov 13, 2026
  • Payment marked received but delayed due to routine due diligence checks on Nov 16
  • Additional document requests and delayed release keep payout held until Nov 17

Uniface 10 field triggers - leaveField compiles, but loseFocus is what runs

A customer app built in Uniface 10 got a quick entry form: while the user moves from field to field, the form tidies names, checks the e-mail address, fills in the city from the postal code and lists…

  • Uniface 10 renamed interactive field triggers
  • "leaveField" trigger replaced with "loseFocus"
  • Proper trigger names crucial for Uniface 10 functionality

Your Contact Form Says Thanks, Then Loses the Lead. Here Is a Next.js Handler That Cannot Drop One

Picture the failure mode that worries me most on a service business site. A homeowner fills out the contact form, clicks Submit, and sees a green "Thanks, we will be in touch." Behind that message…

  • Contact forms are critical for service-based websites to capture leads.
  • Failure to store submissions first can lead to lost leads and false expectations.
  • Storing leads in controlled storage before notifying third-party services prevents silent loss.

More from Monday 16 November →