SST v4.3.5: Amazon Distributed SQL Now Native

industry sources brings you the latest infrastructure development news: SST v4.3.5 introduces native support for Amazon Distributed SQL (Dsql) through a new AWS component. This addition streamlines how developers provision and manage distributed SQL databases within their SST applications without manual CloudFormation workarounds or external tooling.

The new Dsql component follows SST's existing pattern for AWS resources - declarative configuration, type-safe infrastructure, and integrated deployment workflows. Builders can now define distributed SQL clusters alongside their existing compute, storage, and messaging resources in a single codebase.

This is a straightforward capability addition that removes friction from a specific use case: applications requiring distributed SQL semantics across regions or availability zones. The component integrates with SST's existing secrets management, IAM role generation, and environment variable injection systems.

• Native Dsql provisioning through SST's component system
• Integrated with SST's type system and deployment pipeline
• Handles IAM, connection strings, and credential management automatically
• No breaking changes to existing SST applications

The Dsql component targets a specific builder profile: teams running distributed systems that need ACID guarantees across multiple nodes or regions. If your application fits traditional relational patterns but requires geographic distribution or horizontal scaling beyond single-node databases, Dsql addresses that gap.

Builders currently using RDS for single-region workloads don't need to migrate. Dsql makes sense when you're evaluating DynamoDB but need SQL semantics, or when you've outgrown Aurora's scaling constraints. The decision point is clear: do you need distributed transactions with strong consistency guarantees?

• Multi-region applications requiring ACID compliance
• Systems outgrowing single-node PostgreSQL/MySQL capacity
• Teams wanting SQL without operational complexity of sharded databases
• Applications built on SST infrastructure wanting consolidated database management

This release reflects AWS's push to fill the distributed SQL market segment. The addition to SST suggests Amazon sees infrastructure-as-code adoption as the distribution channel for newer database products. Rather than require builders to learn Dsql separately, embedding it in familiar tooling lowers adoption friction.

For SST users specifically, this expands the platform's utility for architecturally complex applications. SST competes on developer experience - reducing decision paralysis and manual infrastructure work. Each new AWS component that's pre-integrated makes SST more complete as an application platform choice versus generic infrastructure tools.

The timing matters too: builders are increasingly skeptical of vendor lock-in but pragmatic about consolidation. A native SST component suggests AWS understands this - they're not forcing adoption, just making it low-friction for teams already in the SST ecosystem.

If you maintain SST applications and haven't evaluated your database scaling strategy recently, now is a checkpoint moment. Audit whether your current database implementation is causing operational overhead, cost concerns, or architectural compromises. Dsql moves from 'theoretical option' to 'thing I can deploy Tuesday' - which changes the calculus.

For teams building new distributed systems on SST, add Dsql to your evaluation matrix alongside Aurora, DynamoDB, and managed Postgres solutions. Run the numbers on per-operation costs and latency across your target regions. The component exists now; the question is whether it's optimal for your workload.

Teams running multi-region applications on other infrastructure platforms (CDK, Terraform, etc.) should understand what SST's integrated approach means: faster iteration cycles, fewer configuration files, better type safety. If you're Terraform-first today but considering SST, this Dsql component is one more data point showing the platform's maturity.

The momentum in this space continues to accelerate.