Document vCPUs required for full range setup about cyberrange HOT 4 CLOSED

@mstair - Thanks for identifying this. I was unaware of the potential issue with vCPU limits yet I am aware of the instance-type quota increase.

Here is the service-quota link... https://docs.aws.amazon.com/servicequotas/latest/userguide/request-increase.html#first-concept-chapter

I performed vCPU research. From what I understand, according to Amazon's on-demand instance limit guidance - there is a calculator that will estimate/calculate the vcpu's needed.

I currently have a limit of 4,704 vcpu's yet plugging in 30 t2.medium instances suggests I need to increase this by at least 60. I do not run the range 24x7x365 - perhaps this is why I have not experienced this issue.

Looking forward - I'm aiming for 50 assets to be running within the range, this suggests a possible limit of 4,804 vCPUs.

Adding a documentation label to this so I get it into the wiki / markup docs. Thanks!

from cyberrange.

I've been in touch with Amazon about this and it appears that we only need to ask for 60 vCPU's. The calculation above assumes all instances running across all region's at the same time.

From AWS support...

"Based on the use case in the link you provided, to run 30 t2.medium instances you only need 60 vCPU's and you should only submit a request for 60 vCPU's.

The 4704 vCPU displayed in the link is for all region combined and the 4764 vCPU would be the new combined limit should the 60 vCPU's be approved.

Lets say for example, you intent to run 50 t2.medium instances in Northern Virginia, you would only require 100 vCPU's and the 200 vCPU that has been approved for you account will be more that sufficient."

from cyberrange.

reviewing open issues/notes. Thanks @shannonmcmurtrey updating this. I'd consider this an operations / administrative item solved via documentation given it is a 1-time request to AWS for quota update. Yet leaving it open to comments in case others think of a better way of handling this

from cyberrange.

I added a note to this issue in the getting started markup. There is currently a Pull request for a bunch of changes in my personal fork. I'm working through CICD updates to ensure greater test coverage. Closing this out

https://docs.aws.amazon.com/general/latest/gr/aws_service_limits.html

from cyberrange.