AppStream Concurrent Users for SaaS Application/Service Quota Issue

0

Hello,

We plan to use AppStream 2.0 to offer our Windows based application in a streaming context. We have everything setup and running in AppStream at present. We've been using an Elastic Fleet of type stream.standard.medium for reasons I will describe below. There is only one application that we are streaming, in App view.

Our use case is unique. We can't know, at any given time, the exact number of streaming instances (i.e., unique users connected to the service) there will be at one time. We have yet to deploy publicly, as we are still testing. We use the AWS API createStreamingURL action to deliver the fleet, stack, app, and userID then receive the streaming URL. This works nicely.

According to the service quotas and follow ups with AWS, it seems the maximum number of concurrent users for an Elastic Fleet of stream.standard.medium type is 10. Even though it says adjustable, AWS support said it is locked at 10.

I see that with an always on or on demand fleet, the max concurrency is 50, also with the option to request an increase (but I haven't tried this yet).

My question is: There are many resources online that describe Saas use cases of AppStream (including many written by AWS themselves) that makes it seem that AppStream is a good option for Saas (given our Windows based application). They also have documentation to describe how small companies and educational institutions can use AppStream to deploy their apps or desktops. In any of these cases, 10 instances (or even 50) limit is incompatible with a popular Saas. Our market will primarily be higher education students and researchers. At any given moment, we could see 50 users wanting to access our AppStream app simultaneously, or it could be 100. Or it could be 25, or it could be 250.

How have others done this? I cannot seem to get any real answers - everything points back to service quotas and asking for increases. Is this to push people away from Elastic Fleets to the more expensive Always on or On Demand fleet options? Even then, with scaling policies enforced, can I make Appstream work for my use case of an unknown number of users at various times throughout the day, from 5 to 150 users at any given moment? It's unclear to me how this works, but given the amount I have read online about successful Saas application using AppStream, it must be possible. Any advice would be greatly appreciated.

已提問 10 個月前檢視次數 285 次
1 個回答
0
已接受的答案

It's not locked at 10. That would be an absurdly limited solution that they rolled out especially given it's a quota per region, not per fleet. We requested our service quota be upped and we have 50 concurrent users logging in to one application, and 20, 30, 40 logging into others.

Our current quota is 200.

已回答 9 個月前
profile picture
專家
已審閱 2 個月前
  • Hi There DDennehy - thank you! I struggled with AWS staff to get an initial increase to 50. The first agent said it's not possible. After getting connected to a different agent, they increased for me without issue. I am happy to hear you are at 200. I can hope my SaaS will rise that that concurrency level - but will start with 50 for now.

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南