aws robomaker create-simulation-job

Creates a simulation job. After 90 days, simulation jobs expire and will be deleted. They will no longer be accessible


--client-request-token <string>Unique, case-sensitive identifier that you provide to ensure the idempotency of the request
--output-location <structure>Location for output files generated by the simulation job
--logging-config <structure>The logging configuration
--max-job-duration-in-seconds <long>The maximum simulation job duration in seconds (up to 14 days or 1,209,600 seconds. When maxJobDurationInSeconds is reached, the simulation job will status will transition to Completed
--iam-role <string>The IAM role name that allows the simulation instance to call the AWS APIs that are specified in its associated policies on your behalf. This is how credentials are passed in to your simulation job
--failure-behavior <string>The failure behavior the simulation job. Continue Restart the simulation job in the same host instance. Fail Stop the simulation job and terminate the instance
--robot-applications <list>The robot application to use in the simulation job
--simulation-applications <list>The simulation application to use in the simulation job
--data-sources <list>Specify data sources to mount read-only files from S3 into your simulation. These files are available under /opt/robomaker/datasources/data_source_name. There is a limit of 100 files and a combined size of 25GB for all DataSourceConfig objects
--tags <map>A map that contains tag keys and tag values that are attached to the simulation job
--vpc-config <structure>If your simulation job accesses resources in a VPC, you provide this parameter identifying the list of security group IDs and subnet IDs. These must belong to the same VPC. You must provide at least one security group and one subnet ID
--compute <structure>Compute information for the simulation job
--cli-input-json <string>Performs service operation based on the JSON string provided. The JSON string follows the format provided by ``--generate-cli-skeleton``. If other arguments are provided on the command line, the CLI values will override the JSON-provided values. It is not possible to pass arbitrary binary values using a JSON-provided value as the string will be taken literally
--generate-cli-skeleton <string>Prints a JSON skeleton to standard output without sending an API request. If provided with no value or the value ``input``, prints a sample input JSON that can be used as an argument for ``--cli-input-json``. If provided with the value ``output``, it validates the command inputs and returns a sample output JSON for that command