How We're Bypassing AWS Complexity

Cover image

Our mission.. to empower Rust developers by providing tooling that bypasses the need to interact with complicated AWS infrastructure or infrastructure files when the requirement is to move fast.

When you're self-hosting, using a VPS, or on the cloud, you have control over everything. It can also be very complex: anything related to AWS, Terraform files, Dockerfiles... the list goes on. If you’re also playing the part as a Software Engineer, this can use up quite a lot of time, especially in cases where moving fast is a higher priority than having control over everything. What you end up with is:

  • Spending time context-switching which interrupts your flow.
  • Ending up with responsibilities that you may not specialize in, potentially spending more time debugging your work.
  • Needing to figure out Cloud consoles; they solve a lot of problems, but are also very complex to use.

Old man yelling at cloud

Other solutions aim to solve this problem by dockerizing your applications for you. However, on those platforms Rust is typically treated as a second-class citizen, requiring you to write your own Dockerfile to deploy on the platform. You may also hit errors that you normally wouldn’t with other languages.

Our aim is to enhance the Rust development experience. We've built our open-source platform with Rust, and we strive to use Rust for our internal tools wherever feasible. Our goal is to provide Rust developers with a smooth and efficient deployment process comparable to what JavaScript developers enjoy with platforms like Vercel, emphasizing ease-of-use with minimal setup.

What are we doing currently?

1. Providing tooling that simplifies deployments

We provide tooling that simplifies deployment by allowing users to add our Shuttle runtime macro to their applications. This means all you need to do is run cargo shuttle deploy and your web service gets sent to the Shuttle servers, containerized, and started. No further steps are required!

Check the video below for a short example:

2. Making resource provisioning as easy as possible

You shouldn’t need to set up YAML files just to get your application going. When using our runtime, you can simply pass in annotation macros that provision resources for you. Whether you need a database, key-value store, or some metadata about your project, we can provide that! By doing this, it allows a seamless experience between getting the infra stuff that you want and then going straight back to writing good code.

What we’re doing in 2024

There are several updates we’re looking forward to announcing this year. Most notably, our upcoming builder service which will allow many more use cases and bring additional platform stability. We are also planning on adding more integrations like Redis, S3 object storage, and more so keep an eye out for our 2024 product roadmap which will have more information!

Feedback is always welcome at if there’s anything you’d like us to know!

This blog post is powered by shuttle - The Rust-native, open source, cloud development platform. If you have any questions, or want to provide feedback, join our Discord server!
Share article

Build the Future of Backend Development with us

Join the movement and help revolutionize the world of backend development. Together, we can create the future!