AWS RoboMaker

What authentication does the AWS RoboMaker API use?

AWS RoboMaker uses AWS Signature Version 4 HMAC signing with an access key ID and secret access key, optionally with a session token. Through Jentic, those credentials live in your Jentic One instance and the agent never handles raw secrets - Jentic signs each request server-side.

Can I run my own custom simulator with AWS RoboMaker, or only Gazebo?

RoboMaker accepts a SimulationApplication that you build and upload (typically a containerised ROS + simulator bundle), so you are not restricted to Gazebo. The simulation application is registered via CreateSimulationApplication and referenced from CreateSimulationJob - but note AWS announced RoboMaker is on a deprecation path, so check current service status before adopting it for new workloads.

What are the rate limits for the AWS RoboMaker API?

AWS does not publish a fixed RPS in the spec; standard AWS API throttling applies. Long-running operations such as CreateSimulationJob also have concurrency limits per account and region - overage returns LimitExceededException, so production agents should poll capacity and queue jobs accordingly.

How do I launch a simulation job with the AWS RoboMaker API through Jentic?

Search Jentic for 'launch a RoboMaker simulation job', load the CreateSimulationJob operation schema, and call POST /createSimulationJob with your robotApplications, simulationApplications, and IAM role ARN. Then poll DescribeSimulationJob until status reaches Completed. Install the SDK first with pip install jentic.

Can the AWS RoboMaker API train ML models, or only run simulations?

RoboMaker itself runs simulations and generates synthetic worlds - it does not train models. The typical pipeline is: generate worlds with CreateWorldGenerationJob, export to S3 with CreateWorldExportJob, then train with Amazon SageMaker on that data. RoboMaker is the simulation and data-generation layer, not the training layer.

Can I limit what my agent is allowed to do with the AWS RoboMaker API?

Yes. Because you run Jentic One yourself, your own rules decide which RoboMaker operations and which AWS credentials the agent may use. Since job, fleet, and robot definitions travel in the request body rather than the URL path, you can allow only the operations the agent needs, such as CreateSimulationJob and CreateWorldGenerationJob, while withholding operations like CancelSimulationJob or fleet deletion. Those operations are callable only when you explicitly grant them.