Getting Rust Official Support on AWS.

Hello! I am new to Rust. I am deciding to use Rust for web backend, but what is holding me back is Rust is not officially supported (SDK and Lambda) on AWS, I would like to use services like RDS, DynamoDB, Lambda and etc. There are good projects like Rusoto. But is not it nice to have official support for Rust by AWS? As I read here AWS it self use Rust.

By getting Rust on AWS, not only we get to use Rust on AWS, but also to get more and more developers to Rust community making both Rust language and its ecosystem better and better.

What If we make a feature request to AWS to support Rust as community by using some sort of a community vote?

1 Like

Howdy, Rusoto maintainer here!

To clear things up, there’s different cases for AWS supporting a language. There’s support inside of services, like Lambda and Elastic Beanstalk. There’s support for official SDKs. There’s a more nebulous concept of support for running services inside of AWS, on EC2 or inside a container running on ECS or EKS.

For the first two types of support, the best way to request AWS officially support it is to contact your AWS account representative and give them the use case you’d like to see. From my conversation with various AWS employees, this is how they create and prioritize their roadmap.

For the last type of support, running services inside AWS, I’m not aware of any list of supported languages. One could write a service in any variety of languages and run it on their infrastructure, and AWS doesn’t keep tabs on it. For example, one could use nginx which is written in C, to serve an application written in PHP, or Ruby, or a rare language. For this case, Rust is as supported as other languages inside AWS. Which is to say it’s not really a thing. :wink: There are people using Rust on AWS right now, including production deployments.

All of these particular cases are different than AWS using Rust internally. It’s my understanding the internal, infrastructure side of AWS is separate from the customer facing side, which is one reason why AWS is using Rust but not yet supporting it in the above areas.

One of the goals of Rusoto is to drive use of Rust on and with AWS so we can get official support. My specific goal was to show there’s increasing interest in a Rust SDK for AWS.

Hope that clears up how we can work towards official support on AWS.

2 Likes

Thank you very much, very valuable info.

I am also going all in for Rust lets do this :smiley:

Keep up your good work with Rusto.

I have an idea what If we also make a feature request through AWS forum in addition to making feature request through support. What do you think?

Thanks, glad the post helped.

It’s been my experience feature requests through the AWS forum aren’t effective. I’ve seen a lot of requests get acknowledged but nothing happens for years, if ever.

From what I can tell, AWS prioritizes feature requests from paying customers telling AWS what they want through their account reps.

Rusoto sends a user-agent header on all requests to AWS, with versions of Rust, Rusoto and OS details. This change was requested and implemented by an AWS employee so they could gather metrics on Rusoto’s usage. With this data in hand they can see how much use Rusoto is getting, to see how much interest there is. See https://github.com/rusoto/rusoto/issues/379 for more info. :grinning:

I see three avenues to making Rust officially supported on AWS:

  • using Rusoto to bump those usage metrics from user-agent information
  • use Rust on AWS and be vocal about it via tweets, blog posts, etc…
  • tell AWS account representatives you’d like to see Rust supported for your use case: faster and safer Lambdas, easier deployment of Rust apps on Elastic Beanstalk, etc…
7 Likes