Urgent.News

What's breaking now, across thousands of outlets.

Tech

Amazon’s Black Friday ‘Deals’ Were Mostly Decoys – What That Means for Cloud Engineers

1. What was released / announced Groundwork Collaborative’s investigation (see the link above) revealed that nearly 1 in 3 Amazon Black Friday and Cyber Monday deals advertised on the retail site offered no savings to shoppers, and almost 1 in 10 were outright price hikes. The study scraped thousands of product listings, compared advertised discounts to historic price data, and found that a large…

An investigation by Groundwork Collaborative found that around a third of Amazon’s Black Friday and Cyber Monday deals advertised on its site didn’t actually provide any savings to customers, while nearly one in ten were price increases. The study analyzed thousands of product listings, comparing advertised discounts to historical price data and discovered that many of the “deal” banners were merely marketing hype.

This matters for DevOps/AI‑infrastructure engineers who frequently purchase cloud resources, such as GPUs, SSDs, or networking gear, from Amazon. If the discounts claimed by Amazon are deceptive, engineers may end up over-budgeting or over-provisioning resources they thought were inexpensive. Three concrete consequences can arise from this:

1. Budget forecasting – Teams that rely on holiday-season sales to justify capital expenditure spikes may find their quarterly forecasts unreliable if the numbers are fake.

2. Security & compliance – Procuring hardware based on inaccurate pricing can lead to rushed purchasing decisions, raising the risk of bypassing vendor security questionnaires.

3. Automation pipelines – Scripts that pull the latest prices from Amazon’s API to decide whether to spin up spot instances or buy reserved ones may propagate bad decision-making downstream if they rely on false price data.

To detect fake deals programmatically, a Python script can be used to query the Amazon Product Advertising API or scrape the public page (if API access isn’t available) to obtain the current “list price” and the “deal price.” The script then compares the deal price to the historical median price obtained from a public price‑tracking service like Keepa.

If the deal price is at or above the median price, it is considered a genuine discount; otherwise, it is flagged as a deceptive promotion. This script can be integrated into CI/CD pipelines to prevent illusory deals from being purchased, set up as a cost‑alert bot in Slack, or incorporated as a Terraform external data source for automated infrastructure management.

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

Secure Your APIs: OAuth2 and JWT for Beginners

Repository with the companion code for the tutorial APIs are frequent targets for bad actors since they expose data and functionality.

  • OAuth 2.0 handles authorization delegation, while JWT provides secure token format
  • JWT includes identity info and acts as authorization ID once issued
  • OAuth2 and JWT complement each other in a system with four key roles

The Agents Are Capable Enough — This Week's Research Is About Catching How They Fail

This edition of the AI Agents Digest covers what's new for agent builders between 2026-11-10 and 2026-11-17: a dense week of security audits, failure-mode benchmarks, memory research, and…

  • Researchers identify risky fallback patterns violating safety boundaries
  • New architectures separate reasoning from execution
  • Multi-LLM agentic AI optimized for edge computing

Git Branch Naming Conventions: Patterns and a CI Check

Originally published on DevToolHub . The git branch naming conventions I would use are a lowercase type/short-description pattern, such as fix/empty-password-crash , with an optional ticket number.

  • Git branch names follow a lowercase type/short-description pattern
  • Optional ticket number can be included in branch names
  • CI check validates branch name format for consistency

More from Tuesday 17 November →