In the Python developer community, a new AWS infrastructure management tool called Stelvio is gaining attention as developers seek alternatives to existing solutions. Currently in early alpha, Stelvio aims to simplify cloud deployment for Python developers by allowing them to define AWS infrastructure using pure Python code rather than JSON configurations or other languages.
The Fragmented Landscape of Python AWS Tools
The current ecosystem for Python developers working with AWS serverless architecture is notably fragmented. Developers in the community have highlighted a range of existing solutions including Zappa, Chalice, Serverless Framework, AWS CDK, CloudFormation, and AWS SAM—each with their own limitations. Many of these tools are either abandoned, poorly maintained, require non-Python configuration, or aren't specifically designed with Python developers in mind.
I think it's amazing the python community has like 5 half baked solutions to this problem, all of which are either abandoned, poorly monetized, or have a janky UI.
This sentiment reflects the frustration many Python developers feel when trying to deploy serverless applications to AWS. The recent rug pull by Serverless Framework—which changed to a paid model in version 4—has further intensified the search for reliable alternatives, with some developers mentioning community-maintained forks like osls as temporary solutions.
Current Python AWS Deployment Tools Mentioned in Discussion:
- Stelvio (Early alpha) - Python-native infrastructure as code
- Zappa - Uses JSON configuration
- Chalice - Appears abandoned, mixes infrastructure with application code
- Serverless Framework - Recently switched to paid model in v4
- osls - Open-source Serverless Framework replacement
- AWS CDK - More verbose but comprehensive
- CloudFormation - Low-level AWS template language
- AWS SAM - Simplified CloudFormation for serverless
- Mangum - Wraps ASGI apps for Lambda deployment
Stelvio Current Features:
- AWS Lambda support
- Amazon DynamoDB integration
- API Gateway configuration
- Automated IAM role/policy management
- Python-native configuration
Upcoming in Stelvio v0.2.0 (April 2025):
- Lambda dependencies & layers
- DynamoDB indexes
- CORS support
- API Gateway authorizers
Stelvio's Developer-First Approach
Stelvio distinguishes itself by focusing specifically on Python developers rather than infrastructure experts. The tool's creator, Michal, explains that while AWS CDK was a significant improvement over CloudFormation and Terraform, infrastructure tools can still be made more developer-friendly.
Stelvio's approach emphasizes minimal boilerplate code through intelligent defaults. For example, creating a DynamoDB table with API Gateway integration requires just a few lines of Python code, automatically handling the creation of IAM policies, roles, API Gateway resources, methods, integrations, and CloudWatch log groups—tasks that would require substantially more code in AWS CDK.
A key design principle of Stelvio is the separation of infrastructure code from application code, unlike some alternatives that mix them through decorators or other mechanisms. This clean separation aligns with software engineering best practices while maintaining the simplicity Python developers expect.
Current Capabilities and Future Roadmap
Currently, Stelvio supports AWS Lambda, Amazon DynamoDB, API Gateway, and automated IAM configuration. According to the developer, version 0.2.0 is expected in April 2025 with support for lambda dependencies and layers, DynamoDB indexes, CORS, and API Gateway authorizers. Version 0.3.0 will introduce a dedicated CLI tool.
While the current implementation focuses on serverless components, the developer has indicated plans for broader AWS service coverage beyond the initial Lambda/API/DynamoDB offerings, potentially including VPC configuration, NAT gateways, and security groups. There are also mentions of possible expansion beyond AWS to services like Cloudflare.
Community Reception and Ongoing Debate
The reception among Python developers has been generally positive, with many expressing interest in a tool that simplifies AWS infrastructure management using familiar Python syntax. Some developers who currently struggle with API Gateway creation have indicated they would adopt Stelvio when it reaches production readiness.
However, the community discussion also reveals ongoing debates about architectural choices. Some developers question the focus on Lambda and DynamoDB, suggesting that traditional servers and relational databases might better serve applications as they mature and requirements evolve. Others inquire about the decision to build on Pulumi rather than directly using boto3, to which the developer cited benefits like state management and multi-cloud potential.
As cloud infrastructure continues to grow in complexity, tools like Stelvio represent attempts to make deployment more accessible to developers who want to focus on building applications rather than managing infrastructure details. Whether Stelvio will succeed where other tools have struggled remains to be seen, but its Python-native approach and focus on developer experience appear to address genuine pain points in the community.
Reference: Stelvio