Hot off the press: aws.amazon.com/about-aws/…/aws-lambda-90-minute-function

https://packagemain.tech/p/gitignore-everything-by-default

Radical idea

https://engineering.atspotify.com/2026/9/portal-by-spotify-cut-my-claude-code-token-usage-by-90

https://nvd.nist.gov/vuln/detail/cve-2026-85046

aws.amazon.com/about-aws/…/aws-lambda-full-iam-resource-based-policies

This security improvement lets you edit a Lambda function's resource-based policy. Before, you had to call the lambda:AddPermission API method to add single statements, and all those did was Allow specific principals to lambda:InvokeFunction . For an analogy, compare the expressiveness of security group rules (allow only) and Network Access Control List rules (allow or deny).

CloudFormation: AWS::Lambda::Permission → AWS::Lambda::ResourcePolicy

Terraform: aws_lambda_permission → aws_lambda_policy (proposed in terraform-provider-aws issue 49691 ; not implemented as of v6.62 ; you could use terraform-provider-awscc for now)

Benefits:

• You can use IAM condition keys to intelligently target principals that can invoke a Lambda function.
• You can make permission to invoke a Lambda function exclusive (for example, exclusive to the event source mapping from one particular SQS queue) by adding a Deny statement to complement an Allow statement in the same resource policy or in an identity-based (IAM user or role) policy. Before, you would have needed a Service Control Policy to prevent unintended IAM users and roles from invoking particular Lambda functions.
Exclusive permission to invoke a Lambda function is now practical, but I need to check whether old restrictions on role trust (assume role) policies for the Lambda service have been relaxed so it's practical to make an IAM role exclusive to a Lambda function.

https://www.tomshardware.com/software/linux/california-lawmakers-unanimously-pass-linux-exemption-from-age-verification-law-software-distributed-under-the-gpl-mit-bsd-and-apache-licenses-are-exempt

https://openai.com/index/our-decision-on-cursor-following-its-acquisition-by-spacex/

https://0ver.org/

https://ducklabs.com/news/2026/08/26/ducklabs-to-join-aws

https://x.com/vicky_grok/status/2092263750300790995?s=46&t=hxmjEyu5OyUbWbc_cO5EPQ

https://www.linkedin.com/posts/joshpollara_terraform-activity-7497989985753767936-0EEV

Terraform module registries are dying.

People can just ask AI to write a local module, and it's actually pretty good at it. Claude has reduced the time it takes to write a module to nearly zero.

An interesting discussion that promises to get more interesting. I'm curious whether there are discernible changes in module download rates.

2 projects came out that implement scalable git hosting just by using an s3 bucket as the data plane thanks to the somewhat new conditional PUT primitive supported by S3: gitwal.io by Scott Chacon and github.com/tobi/walgit by Tobi Lutke. Implementations of cursor.com/blog/git-at-any-scale. Makes for a nice reading and I'm sure we'll see many new projects around that.

https://omarchy.org/news/2026/08/omacom-foundation-funding-hits-10m

https://thenextweb.com/news/slack-code-ai-coding-channels-launch

https://github.blog/news-insights/company-news/the-august-17-outage-and-the-work-ahead/

this one is wicked good! agentsview.io
thanks for sharing 🫡

TIL: KYAML is a thing?

kubernetes.io/blog/…/how-to-pretty-print-kubernetes-yaml-as-kyaml

GitHub post mortem https://www.githubstatus.com/incidents/zkxwbgr0cnmx

aws.amazon.com/about-aws/…/iam-policy-autopilot-now-supports-terraform-plan-files

Hot off the press! I will enjoy testing this one. It could bring some of the discipline of (template-specific) CloudFormation execution roles to Terraform.

https://www.rickmanelius.com/p/aidr-ai-didnt-read

AI;DR is the new TL;DR

https://www.bloomberg.com/news/articles/2026-08-16/stripe-nears-deal-to-buy-ai-firm-openrouter-for-over-7-billion

I was pleasantly surprised to see that TFLint created an OPA plugin! In the past, I've wanted to create a custom TFLint plugin with my own rulesets, but the overhead of maintaining it over time seemed pretty daunting. I played around with the OPA ruleset and it makes it exponentially easier to write Rego for the things I care about. I wrote a little blog on how I configured and incorporated it into my pipelines and pre-commit hooks! Wire it up to Atmos and you have a little compliance as code framework baked right next to your IaC
rosesecurity.dev/2026/08/12/terraform-opa-the-easy-way.html

https://github.com/anchore/grype

https://www.linkedin.com/pulse/stop-being-code-review-bottleneck-posthog-8rqwc?utm_source=share&utm_medium=member_ios&utm_campaign=share_via

https://developers.googleblog.com/why-go-is-an-ideal-language-for-ai-assisted-software-engineering/

https://research.meta.ai/blog/introducing-muse-glimmer-open-agentic-model

Didn't realize you can run OPA with TFLint!

github.com/terraform-linters/tflint-ruleset-opa/blob/…/README.md

https://www.docker.com/products/docker-sandboxes/

https://www.reddit.com/r/kubernetes/comments/1vh4our/zerodowntime_node_drains_for_singlereplica/

https://masterpoint.io/blog/aws-adaptive-retry-mode-terraform-throttled-api-requests/

https://discourse.nixos.org/t/the-nixpkgs-core-team-has-disbanded/79413

https://blog.cloudflare.com/kitesurf/