<a id="cli-aws-iot-create-thing"></a>

# create-thing

## Description

Creates a thing record in the registry. If this call is made multiple times using the same thing name and configuration, the call will succeed. If this call is made with the same thing name but different configuration a `ResourceAlreadyExistsException` is thrown.

#### NOTE
This is a control plane operation. See [Authorization](https://docs.aws.amazon.com/iot/latest/developerguide/iot-authorization.html) for information about authorizing control plane actions.

Requires permission to access the [CreateThing](https://docs.aws.amazon.com/service-authorization/latest/reference/list_awsiot.html#awsiot-actions-as-permissions) action.

See also: [AWS API Documentation](https://docs.aws.amazon.com/goto/WebAPI/iot-2015-05-28/CreateThing)

## Synopsis

```
  create-thing
--thing-name <value>
[--thing-type-name <value>]
[--attribute-payload <value>]
[--billing-group-name <value>]
[--cli-input-json | --cli-input-yaml]
[--generate-cli-skeleton <value>]
[--debug]
[--endpoint-url <value>]
[--no-verify-ssl]
[--no-paginate]
[--output <value>]
[--query <value>]
[--profile <value>]
[--region <value>]
[--version <value>]
[--color <value>]
[--no-sign-request]
[--ca-bundle <value>]
[--cli-read-timeout <value>]
[--cli-connect-timeout <value>]
[--cli-binary-format <value>]
[--no-cli-pager]
[--cli-auto-prompt]
[--no-cli-auto-prompt]
[--cli-error-format <value>]
[--help]
```

## Options

`--thing-name` (string) [required]

> The name of the thing to create.

> You can’t change a thing’s name after you create it. To change a thing’s name, you must create a new thing, give it the new name, and then delete the old thing.

> Constraints:

> * min: `1`
> * max: `128`
> * pattern: `[a-zA-Z0-9:_-]+`

`--thing-type-name` (string)

> The name of the thing type associated with the new thing.

> Constraints:

> * min: `1`
> * max: `128`
> * pattern: `[a-zA-Z0-9:_-]+`

`--attribute-payload` (structure)

> The attribute payload, which consists of up to three name/value pairs in a JSON document. For example:

> > `{\"attributes\":{\"string1\":\"string2\"}}`

> attributes -> (map)

> > A JSON string containing up to three key-value pair in JSON format. For example:

> > > `{\"attributes\":{\"string1\":\"string2\"}}`

> > key -> (string)

> > > Constraints:

> > > * max: `128`
> > > * pattern: `[a-zA-Z0-9_.,@/:#-]+`

> > value -> (string)

> > > Constraints:

> > > * max: `800`
> > > * pattern: `[a-zA-Z0-9_.,@/:#=\[\]-]*`

> merge -> (boolean)

> > Specifies whether the list of attributes provided in the `AttributePayload` is merged with the attributes stored in the registry, instead of overwriting them.

> > To remove an attribute, call `UpdateThing` with an empty attribute value.

> > #### NOTE
> > The `merge` attribute is only valid when calling `UpdateThing` or `UpdateThingGroup` .

Shorthand Syntax:

```
attributes={KeyName1=string,KeyName2=string},merge=boolean
```

JSON Syntax:

```json
{
  "attributes": {"string": "string"
    ...},
  "merge": true|false
}
```

`--billing-group-name` (string)

> The name of the billing group the thing will be added to.

> Constraints:

> * min: `1`
> * max: `128`
> * pattern: `[a-zA-Z0-9:_-]+`

`--cli-input-json` | `--cli-input-yaml` (string)
Reads arguments from the JSON string provided. The JSON string follows the format provided by `--generate-cli-skeleton`. If other arguments are provided on the command line, those 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. This may not be specified along with `--cli-input-yaml`.

`--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`. Similarly, if provided `yaml-input` it will print a sample input YAML that can be used with `--cli-input-yaml`. If provided with the value `output`, it validates the command inputs and returns a sample output JSON for that command. The generated JSON skeleton is not stable between versions of the AWS CLI and there are no backwards compatibility guarantees in the JSON skeleton generated.

## Global Options

`--debug` (boolean)

Turn on debug logging.

`--endpoint-url` (string)

Override command’s default URL with the given URL.

`--no-verify-ssl` (boolean)

By default, the AWS CLI uses SSL when communicating with AWS services. For each SSL connection, the AWS CLI will verify SSL certificates. This option overrides the default behavior of verifying SSL certificates.

`--no-paginate` (boolean)

Disable automatic pagination. If automatic pagination is disabled, the AWS CLI will only make one call, for the first page of results.

`--output` (string)

The formatting style for command output.

* json
* text
* table
* yaml
* yaml-stream
* off

`--query` (string)

A JMESPath query to use in filtering the response data.

`--profile` (string)

Use a specific profile from your credential file.

`--region` (string)

The region to use. Overrides config/env settings.

`--version` (string)

Display the version of this tool.

`--color` (string)

Turn on/off color output.

* on
* off
* auto

`--no-sign-request` (boolean)

Do not sign requests. Credentials will not be loaded if this argument is provided.

`--ca-bundle` (string)

The CA certificate bundle to use when verifying SSL certificates. Overrides config/env settings.

`--cli-read-timeout` (int)

The maximum socket read time in seconds. If the value is set to 0, the socket read will be blocking and not timeout. The default value is 60 seconds.

`--cli-connect-timeout` (int)

The maximum socket connect time in seconds. If the value is set to 0, the socket connect will be blocking and not timeout. The default value is 60 seconds.

`--cli-binary-format` (string)

The formatting style to be used for binary blobs. The default format is base64. The base64 format expects binary blobs to be provided as a base64 encoded string. The raw-in-base64-out format preserves compatibility with AWS CLI V1 behavior and binary values must be passed literally. When providing contents from a file that map to a binary blob `fileb://` will always be treated as binary and use the file contents directly regardless of the `cli-binary-format` setting. When using `file://` the file contents will need to properly formatted for the configured `cli-binary-format`.

* base64
* raw-in-base64-out

`--no-cli-pager` (boolean)

Disable cli pager for output.

`--cli-auto-prompt` (boolean)

Automatically prompt for CLI input parameters.

`--no-cli-auto-prompt` (boolean)

Disable automatically prompt for CLI input parameters.

`--cli-error-format` (string)

The formatting style for error output. By default, errors are displayed in enhanced format.

* legacy
* json
* yaml
* text
* table
* enhanced

`--help` (boolean)

Display help for the command/subcommand.

## Examples

#### NOTE
To use the following examples, you must have the AWS CLI installed and configured. See the [Getting started guide](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-getting-started.html) in the *AWS CLI User Guide* for more information.

Unless otherwise stated, all examples have unix-like quotation rules. These examples will need to be adapted to your terminal’s quoting rules. See [Using quotation marks with strings](https://docs.aws.amazon.com/cli/latest/userguide/cli-usage-parameters-quoting-strings.html) in the *AWS CLI User Guide* .

**Example 1: To create a thing record in the registry**

The following `create-thing` example creates an entry for a device in the AWS IoT thing registry.

```bash
aws iot create-thing \
    --thing-name SampleIoTThing
```

Output:

```json
{
    "thingName": "SampleIoTThing",
    "thingArn": "arn:aws:iot:us-west-2: 123456789012:thing/SampleIoTThing",
    "thingId": " a1b2c3d4-5678-90ab-cdef-EXAMPLE11111 "
}
```

**Example 2: To define a thing that is associated with a thing type**

The following `create-thing` example create a thing that has the specified thing type and its attributes.

```bash
aws iot create-thing \
    --thing-name "MyLightBulb" \
    --thing-type-name "LightBulb" \
    --attribute-payload '{"attributes": {"wattage":"75", "model":"123"}}'
```

Output:

```json
{
    "thingName": "MyLightBulb",
    "thingArn": "arn:aws:iot:us-west-2:123456789012:thing/MyLightBulb",
    "thingId": "a1b2c3d4-5678-90ab-cdef-EXAMPLE22222"
}
```

For more information, see [How to Manage Things with the Registry](https://docs.aws.amazon.com/iot/latest/developerguide/thing-registry.html) and [Thing Types](https://docs.aws.amazon.com/iot/latest/developerguide/thing-types.html) in the *AWS IoT Developers Guide*.

## Output

thingName -> (string)

> The name of the new thing.

> Constraints:

> * min: `1`
> * max: `128`
> * pattern: `[a-zA-Z0-9:_-]+`

thingArn -> (string)

> The ARN of the new thing.

thingId -> (string)

> The thing ID.