# infrastructure as code (IAC)

Infrastructure as code (IaC) is the practice of provisioning and managing computing infrastructure with code rather than manual processes.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Pulumi Context API: query your infrastructure as a graph

DevFeed: [Pulumi Context API: query your infrastructure as a graph](<https://devfeed.tech/articles/pulumi-context-api-query-your-infrastructure-as-a-graph-19022.md>)

Original publisher: [Read original article](<https://www.pulumi.com/blog/pulumi-context-api/>)

Author: Levi Blackstone

Published: 2026-08-26T00:00:00Z

Content type: release

Language: en

Sources: [Pulumi](<https://devfeed.tech/sources/pulumi.md>)

Topics: [API](<https://devfeed.tech/topics/api.md>), [Graphs](<https://devfeed.tech/topics/graphs.md>), [Cloud APIs](<https://devfeed.tech/topics/cloud-apis.md>), [infrastructure as code (IAC)](<https://devfeed.tech/topics/infrastructure-as-code-iac.md>), [Command-line interface](<https://devfeed.tech/topics/cli.md>), [JSON](<https://devfeed.tech/topics/json.md>), [pulumi-neo](<https://devfeed.tech/topics/pulumi-neo.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [api](<https://devfeed.tech/tags/api.md>), [cli](<https://devfeed.tech/tags/cli.md>), [features](<https://devfeed.tech/tags/features.md>), [graph](<https://devfeed.tech/tags/graph.md>), [iac](<https://devfeed.tech/tags/iac.md>), [infrastructure-as-code-iac](<https://devfeed.tech/tags/infrastructure-as-code-iac.md>), [json](<https://devfeed.tech/tags/json.md>), [product](<https://devfeed.tech/tags/product.md>), [pulumi](<https://devfeed.tech/tags/pulumi.md>), [pulumi-cloud](<https://devfeed.tech/tags/pulumi-cloud.md>), [pulumi-neo](<https://devfeed.tech/tags/pulumi-neo.md>), [rest-api](<https://devfeed.tech/tags/rest-api.md>)

### AI overview

Pulumi is launching the Context API, a read-only API that connects Pulumi-managed and discovered resources, stacks, and their relationships into a graph. Available in public preview for Enterprise and Business Critical organizations, it supports infrastructure-impact, coverage, and cleanup queries through the Pulumi CLI or REST API. Pulumi Neo uses it out of the box, and other authenticated agents can access its schema and query guidance.

### Source excerpt

Every platform team fields the same questions: What is running? What breaks if we change this? What can we safely delete? The answers exist, but they're scattered across state files, cloud consoles, and the memories of whoever set things up. Today we're launching the Pulumi Context API, a read-only API that connects Pulumi-managed and discovered resources, stacks, and their relationships into a graph. It's designed agent-first: Pulumi Neo, our infrastructure agent, uses it out of the box, and other agents can fetch the current graph vocabulary and query guidance on demand. It's available in public preview for organizations on the Enterprise and Business Critical editions. Answers that follow infrastructure relationships Pulumi already records the resources your programs manage, their dependencies, how stacks consume each other's outputs, and the resources Pulumi Discovery finds outside infrastructure as code (IaC). The Context API connects this data so you can ask questions that depend on the relationships: Impact: Which stacks are affected if we upgrade this provider? If this stack changes, what consumes its outputs? Coverage: How much of our infrastructure lives outside IaC, and in which accounts? Cleanup: Which stacks have no dependents and are candidates for retirement? A query is a JSON document with a handful of clauses. anchor names the starting nodes, traverse follows relationships from there, and return chooses what comes back. You can run a query through the Pulumi CLI or REST API. Here's a selector that starts from AWS provider instances older than version 7.0.0 and follows incoming provided_by relationships back to the visible resources they manage: { "anchor": { "nodeType": "resource", "match": { "type": "pulumi:providers:aws", "fields": { "provider_version": { "op": "lt", "value": "7.0.0" } } } }, "traverse": [ { "edgeTypes": ["provided_by"], "direction": "in", "alias": "managed" } ], "return": { "select": ["anchor", "managed"] } } A response for one m

## Terraform module to manage Oxbow Lambda and its components

DevFeed: [Terraform module to manage Oxbow Lambda and its components](<https://devfeed.tech/articles/terraform-module-to-manage-oxbow-lambda-and-its-components-22561.md>)

Original publisher: [Read original article](<https://tech.scribd.com/blog/2025/terraform-oxbow-module.html>)

Author: Oleh Motrunych

Published: 2025-03-14T00:00:00Z

Content type: release

Language: en

Sources: [Scribd Tech](<https://devfeed.tech/sources/scribd-tech.md>)

Topics: [Terraform](<https://devfeed.tech/topics/terraform.md>), [AWS Lambda](<https://devfeed.tech/topics/aws-lambda.md>), [infrastructure as code (IAC)](<https://devfeed.tech/topics/infrastructure-as-code-iac.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [AWS Glue](<https://devfeed.tech/topics/aws-glue.md>), [Amazon Simple Queue Service (SQS)](<https://devfeed.tech/topics/amazon-simple-queue-service-sqs.md>), [data-processing](<https://devfeed.tech/topics/data-processing.md>), [event driven](<https://devfeed.tech/topics/event-driven.md>), [DynamoDB](<https://devfeed.tech/topics/dynamodb.md>), [Amazon S3](<https://devfeed.tech/topics/amazon-s3.md>)

Tags: [aws](<https://devfeed.tech/tags/aws.md>), [aws-glue](<https://devfeed.tech/tags/aws-glue.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [aws-s3](<https://devfeed.tech/tags/aws-s3.md>), [deltalake](<https://devfeed.tech/tags/deltalake.md>), [dynamodb](<https://devfeed.tech/tags/dynamodb.md>), [event-driven](<https://devfeed.tech/tags/event-driven.md>), [iac](<https://devfeed.tech/tags/iac.md>), [oxbow](<https://devfeed.tech/tags/oxbow.md>), [rust](<https://devfeed.tech/tags/rust.md>), [security](<https://devfeed.tech/tags/security.md>), [sqs](<https://devfeed.tech/tags/sqs.md>), [terraform](<https://devfeed.tech/tags/terraform.md>)

### AI overview

The article introduces terraform-oxbow, an open-source Terraform module for deploying and managing an Oxbow AWS Lambda workflow and its supporting components. It describes configurable integrations including AWS Glue, Kinesis Data Firehose, SQS, DynamoDB, IAM policies, and S3 notifications, while noting AWS notification limits and least-privilege considerations.

### Source excerpt

Oxbow is a project to take an existing storage location which contains Apache Parquet files into a Delta Lake table. It is intended to run both as an AWS Lambda or as a command line application. We are excited to introduce terraform-oxbow, an open-source Terraform module that simplifies the deployment and management of AWS Lambda and its supporting components. Whether you're working with AWS Glue, Kinesis Data Firehose, SQS, or DynamoDB, this module provides a streamlined approach to infrastructure as code (IaC) in AWS.

## Move Fast and "Branch" Things

DevFeed: [Move Fast and "Branch" Things](<https://devfeed.tech/articles/move-fast-and-branch-things-5584.md>)

Original publisher: [Read original article](<https://neon.com/blog/move-fast-and-branch-things>)

Author: Stephen Siegert

Published: 2024-04-15T16:38:10Z

Content type: article

Language: en

Sources: [Blog -- Neon Docs](<https://devfeed.tech/sources/blog-neon-docs.md>)

Topics: [Databases](<https://devfeed.tech/topics/databases.md>), [infrastructure as code (IAC)](<https://devfeed.tech/topics/infrastructure-as-code-iac.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>), [autoscaling](<https://devfeed.tech/topics/autoscaling.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>), [Provisioning](<https://devfeed.tech/topics/provisioning.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>)

Tags: [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [autoscaling](<https://devfeed.tech/tags/autoscaling.md>), [availability](<https://devfeed.tech/tags/availability.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [community](<https://devfeed.tech/tags/community.md>), [database](<https://devfeed.tech/tags/database.md>), [iam](<https://devfeed.tech/tags/iam.md>), [infrastructure-as-code-iac](<https://devfeed.tech/tags/infrastructure-as-code-iac.md>), [networking](<https://devfeed.tech/tags/networking.md>), [provisioning](<https://devfeed.tech/tags/provisioning.md>), [serverless](<https://devfeed.tech/tags/serverless.md>)

### AI overview

Neon presents scalable Postgres with database branching, autoscaling, and serverless scale to zero as a way to reduce infrastructure complexity from development through production. The article contrasts this approach with traditional AWS RDS and Google Cloud SQL setups that require extensive infrastructure-as-code, networking, access management, high availability, scaling, backup, and cost planning.

### Source excerpt

Neon simplifies the use of scalable Postgres, changing how you handle your database infrastructure from development through production. This is a fundamental shift in how to leverage your Postgres infrastructure. Instead of spending time on Infrastructure as code (IaC) and cloud-...