create_dimension
async
¶
create_dimension(
name: DimensionName,
type: DimensionType,
string_values: DimensionStringValues,
client_request_token: ClientRequestToken,
*,
config_overrides: Optional[AsyncIoTClientConfig] = None,
tags: Optional[TagList] = None,
) -> CreateDimensionResponse
The IoT Device Defender detect feature will no longer be available to new customers starting August 31, 2026. If you would like to use the detect feature, sign up prior to August 31, 2026. To learn about alternatives to IoT Device Defender detect, see IoT Device Defender detect feature availability change in the IoT Device Defender Developer Guide. There is no change to IoT Device Defender audit availability.
Create a dimension that you can use to limit the scope of a metric used in a security profile for IoT Device Defender. For example, using a TOPIC_FILTER dimension, you can narrow down the scope of the metric only to MQTT topics whose name match the pattern specified in the dimension.
Requires permission to access the CreateDimension action.
Parameters:
-
name(DimensionName) –A unique identifier for the dimension. Choose something that describes the type and value to make it easy to remember what it does.
-
type(DimensionType) –Specifies the type of dimension. Supported types:
TOPIC_FILTER. -
string_values(DimensionStringValues) –Specifies the value or list of values for the dimension. For
TOPIC_FILTERdimensions, this is a pattern used to match the MQTT topic (for example, "admin/#"). -
tags(Optional[TagList], default:None) –Metadata that can be used to manage the dimension.
-
client_request_token(ClientRequestToken) –Each dimension must have a unique client request token. If you try to create a new dimension with the same token as a dimension that already exists, an exception occurs. If you omit this value, Amazon Web Services SDKs will automatically generate a unique client request.
Raises:
-
InternalFailureException–An unexpected error has occurred.
-
InvalidRequestException–The request is not valid.
-
LimitExceededException–A limit has been exceeded.
-
ResourceAlreadyExistsException–The resource already exists.
-
ThrottlingException–The rate exceeds the limit.
-
UnknownServiceError–The service returned an error code this client does not model.
Source code in docs_src/capo_iot/_services/async_io_t.py
2438 2439 2440 2441 2442 2443 2444 2445 2446 2447 2448 2449 2450 2451 2452 2453 2454 2455 2456 2457 2458 2459 2460 2461 2462 2463 2464 2465 2466 2467 2468 2469 2470 2471 2472 2473 2474 2475 2476 2477 2478 2479 2480 2481 2482 2483 2484 2485 2486 2487 2488 2489 2490 2491 2492 2493 2494 2495 2496 2497 2498 2499 | |