With AWS RoboMaker, there are no upfront charges and you only pay for the AWS resources you use. You will be billed separately for each RoboMaker capability, including use of AWS services provided through RoboMaker cloud extensions for ROS (Robot Operating System), RoboMaker development environment, RoboMaker simulation, and RoboMaker fleet management.
Cloud extensions for ROS
Use of AWS services provided through cloud extensions for ROS
AWS RoboMaker cloud extensions for ROS are free and released under the Apache Software License 2.0, a permissive license with limited restrictions on reuse. You only incur standard AWS service charges when your ROS application utilizes AWS services through these cloud extensions.
Let’s consider that you use ROS to build 50 logistics robots to automate your fulfillment centers and would like to add object recognition to these robots. You will use the Amazon Kinesis Video Streams ROS extension to stream live video data from these robots to Amazon Rekognition. Amazon Rekognition will then recognize and tag the objects in the video data and return this information back to these robots through the Amazon Rekognition ROS extension. Consider that each robot streams 60 minutes of video data per month for object recognition, at a rate of 7.50 MB of video data per minute.
Total GB of video data ingested: 7.50 MB/minute * 60 minutes/month * 50 robots = 21.97 GB
Total GB of video data consumed: 7.50 MB/minute * 60 minutes/month * 50 robots * = 21.97 GB
Amazon Kinesis Videos Streams price per GB of video data ingested or consumed: $0.0085
Amazon Kinesis Video Streams charges: 21.97 GB * $0.0085/GB + 21.97 GB * $0.0085/GB = $0.38
Total minutes of live video data analyzed: 60 minutes/month * 50 robots = 3,000 minutes
Amazon Rekognition price per minute of live video data analyzed: $0.12
Amazon Rekognition charges: 3,000 minutes * $0.12/minute = $360
Total charges: $0.38 + $360 = $360.38
AWS RoboMaker development environment runs on AWS Cloud9. Standard AWS Cloud9 rates apply and there is no additional charges for using the RoboMaker development environment. AWS Cloud9 charges for the compute and storage resources (e.g. EC2 instances and EBS volume) that are used to run and store your code.
Let’s consider that you create your RoboMaker development environment on an m4.large EC2 instance with 8 GB of EBS General Purpose SSD (gp2) volume attached. Consider that you develop your robotics application in this environment 8 hours per day and 20 days per month.
Total instance hours used: 8 hours/day * 20 days/month = 160 hours
Amazon EC2 price per hour of on-demand m4.large instance: $0.10
Amazon EC2 charges: 160 hours * $0.10/hour = $16
Total GB-month of EBS volume used: 8 GB * 1 month = 8 GB-month
Amazon EBS price per GB-month of provisioned gp2 volume: $0.10
Amazon EBS charges: 8 GB-month * $0.10/GB-month = $0.80
Total charges: $16 + $0.80 = $16.80
With AWS RoboMaker simulation, you only pay for the time your simulation job takes to run. There are no resources to manage, no upfront costs, and you are only charged when your simulation job is in “running” status. You are charged an hourly rate based on the number of Simulation Units (or SUs) required to run your simulation job. 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. For example, if your simulation job requires 1 vCPU and 4 GB of memory to run, it will require 2 SUs. A simulation job requires a minimum of 1 SU. You are billed at an hourly SU rate in increments of 1 minute, rounded up to the nearest minute.
The number of SUs required by a simulation job scales with the complexity of your robot and simulation world. A typical ground mobility robot has one camera sensor, one Lidar sensor, and two actuators. A modestly complex simulation world like a warehouse or a retail store contains about 100 modeled objects. For reference, running a simulation job with a typical robot and a modestly complex simulation world as described above requires about 7 vCPUs and 14 GB of memory, or 7 SUs.
Let’s consider that your robotics application release cycle is once a month and during each release, you use RoboMaker simulation to run 100 hours of simulations for performance testing. Consider that your robot is like a typical ground mobility robot and your simulation world is like a typical warehouse as described above. Running your simulation job will require 7 SUs.
Total SU-hours used: 100 hours/month * 7 SUs = 700 SU-hours
RoboMaker simulation price per SU per hour: $0.40
Total charges: 700 SU-hours * $0.40/SU-hour = $280
AWS RoboMaker fleet management uses AWS Greengrass for over-the-air (OTA) deployment, or remote software updates. Standard AWS Greengrass rates apply and there are no additional charges for using this capability within AWS RoboMaker fleet management. AWS Greengrass charges based on the number of active devices that interact with AWS in a given month.
Let’s consider that you have 50 robots registered with RoboMaker fleet management and update the application on them once a month.
Total number of active devices: 50 devices
AWS Greengrass price per active device per month: $0.16
Total charges: 50 devices * $0.16/device = $8