AWS RoboMaker now supports configurable Simulation Unit limit
AWS RoboMaker, a service that makes it easy to run robotics simulations at cloud scale, now supports configurable Simulation Unit limit, to help control robotics application testing costs. With AWS RoboMaker simulation, you only pay for the time your simulation job takes to run, and you are charged an hourly rate based on the number of Simulation Units (or SUs) required to run your simulation job – which you can now limit.
AWS RoboMaker, a service that makes it easy to run robotics simulations at cloud scale, now supports configurable Simulation Unit limit, to help control robotics application testing costs. With AWS RoboMaker simulation, you only pay for the time your simulation job takes to run, and you are charged an hourly rate based on the number of Simulation Units (or SUs) required to run your simulation job – which you can now limit.
A single SU provides 1 vCPU and 2 GB of memory, and the number of SUs required to run your simulation job is determined by the maximum resource requirement between vCPU and memory. This new capability enables you to configure the maximum amount of SUs that can be used by your simulation job so that you can easily limit the cost associated with the job. You are billed by the number of SUs consumed by the job, up to the configured limit. For details about configuring SU limit, please see the RoboMaker documentation.
AWS RoboMaker is available in US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), EU (Frankfurt), Asia Pacific (Tokyo), and Asia Pacific (Singapore) regions. To get started, please explore the RoboMaker webpage or run a sample simulation job in the RoboMaker console.