DEV Community

Rishi for AWS Community Builders

Posted on

AWS Blocks: A New Way to Build on AWS

AWS Blocks

Just explored AWS Blocks today, and the idea is quite interesting.

If you've ever built a full-stack application on AWS, you know how quickly things get out of hand.

A simple Todo app can easily turn into creating DynamoDB tables >> wiring Lambda functions >> configuring API Gateway routes >> setting up Cognito >> debugging IAM permissions >> LocalStack for local testing

Before you've even written much business logic, you've already wired together half a dozen AWS services.

AWS Blocks aims to solve this with a concept called Infrastructure From Code (IFC). No separate infrastructure files. Infrastructure is inferred from the code you write.

AWS Blocks Explained

Instead of writing application code in one place and infrastructure definitions in CDK/Terraform somewhere else, you work with higher-level building blocks such as:

• KVStore
• DistributedTable
• Auth
• Realtime
• FileBucket
• Agent

During local development, these blocks are simulated locally.

When deployed, the same blocks are translated into actual AWS resources such as DynamoDB, Cognito, S3, API Gateway, Bedrock, and more.

Have you tried AWS Blocks yet? What are your thoughts on Infrastructure From Code?

Top comments (0)