We want talks grounded in real experience. Production, hands-on, and honest. Tell us what you built and why it mattered, how you deployed it, what broke and how you fixed it, what worked and what did not, and the decisions you would make differently. The pattern or lesson that stuck with you is often the most valuable part of the talk.

Acceptable topics

We welcome sessions covering the fundamentals as well as deep dives across AWS services and practices, including but not limited to:

• Production incidents and war stories (the honest kind, not the sanitised kind)
• Containers and orchestration (ECS, EKS, scaling, real-world patterns)
• Serverless (Lambda, API Gateway, Step Functions, lessons at scale)
• Databases (RDS, DynamoDB, choosing and migrating, performance tuning)
• DevOps and SRE (CI/CD, monitoring, observability, on-call, incident response)
• Infrastructure as Code (Terraform, CloudFormation, managing infra at scale)
• AI and ML (SageMaker, training, deployment, MLOps in production)
• Generative AI (Bedrock, agents, RAG, LLMs in real applications)
• Data and Analytics (pipelines, lake architecture, cost optimisation)
• Security and Compliance (IAM design, real challenges, what actually works)
• Cost optimisation (how you actually reduced your AWS bill, with numbers where you can share them)
• Cloud migration (legacy to cloud, real challenges, what you would do differently)
• Open Source on AWS (tools you built, patterns you shared, community projects)

The rule is simple: if you have deployed it, implemented it, or debugged it in production, it is fair game.

A strong submission is specific (not "scaling on AWS" but "how we scaled DynamoDB from 100 to 10k RCUs and what that taught us"), honest about what did not work, grounded in real numbers and constraints, and useful enough that attendees walk out with something they can try. You do not need to be perfect. The failures are often the most interesting story.

Please refrain from marketing pitches and vendor content, purely theoretical talks with no deployment experience, and filler with no real insight. Such submissions will not be received well and will be rejected.

Session formats

• Regular session: 30 minutes, including 5 minutes for Q&A.
• Lightning talk: 15 minutes.

Live demos are encouraged. Show us what you built, walk through the code, show the failure and how you fixed it. We recommend recording your demo in advance for smooth delivery.

Levels of expertise

Tell us the level of your talk and we will schedule it for the right audience:

• Introductory (100): fundamentals, getting started, common pitfalls
• Intermediate (200): best practices, architectural patterns, production considerations
• Advanced (300): deep dives, optimisation, lessons from scale
• Expert (400): emergent patterns and the hard edges

Target audience

Our audience is builders from Nagpur and across central India: backend and full-stack developers, DevOps and SRE engineers, cloud and solution architects, data and ML practitioners, engineering managers, tech leads, and startup technologists, many from small teams and growing companies. They are hands-on and they know what shipping looks like, so talk to them as peers.

Code of Conduct

All speakers and attendees agree to follow our Code of Conduct. In short: be respectful and inclusive, with no discrimination, harassment, or exclusion. We are here to learn from each other and build together. 

This is a community-run event. Travel and accommodation reimbursement are not provided, so please make your own arrangements.

Event fee

Free for speakers.

Questions

For any questions, please reach out to the event organizers at awsugngp@gmail.com