Amazon GuardDuty now tags attack sequences with five new indicator types—MALICIOUS_PACKAGE, MISCONFIGURATION, REACHABILITY, SENSITIVE_DATA, and VULNERABILITY—making it easier to spot the full picture of threats in your cloud environment. As a cloud engineer, you should review your GuardDuty findings to leverage these richer signals and catch attack chains earlier before they escalate.
source: [aws/security-blog]
Learn how to enforce ML-DSA algorithm policies across your AWS environment using SCPs and IAM to prevent non-compliant cryptographic choices. This practical guide helps you balance post-quantum security requirements with signature size constraints while keeping your infrastructure locked down.
source: [aws/security-blog]
AWS just dropped Lambda Web Functions, letting your code handle HTTP requests directly using familiar frameworks like Express or Hono—no adapters needed. You're getting Node.js support across five regions (US East/West, Tokyo, Ireland) with pay-per-active-CPU pricing, multi-region routing, and native HTTP streaming that'll make your AI endpoints and SSR apps way snappier.
source: [aws/whats-new]
AWS now lets US customers sign up and pay invoices directly from their bank accounts using ACH direct debit—no credit card needed. Both new and existing customers can link their USD bank accounts through secure authentication, making payment management smoother and more flexible.
source: [aws/whats-new]
AWS Security Hub just dropped native CSV and JSON export to S3, so you can skip building custom extraction pipelines for compliance reports and audit trails. Grab findings from any view—Threats, Vulnerabilities, Posture Management, you name it—and have them land in your S3 bucket on demand. This is live across all AWS regions where Security Hub operates.
source: [aws/whats-new]