create_wireless_gateway
async
¶
create_wireless_gateway(
lo_ra_wan: LoRaWANGateway,
*,
config_overrides: Optional[AsyncIoTWirelessClientConfig] = None,
name: Optional[WirelessGatewayName] = None,
description: Optional[Description] = None,
tags: Optional[TagList] = None,
client_request_token: Optional[ClientRequestToken] = None,
) -> CreateWirelessGatewayResponse
Provisions a wireless gateway.
When provisioning a wireless gateway, you might run into duplication errors for the following reasons.
-
If you specify a
GatewayEuivalue that already exists. -
If you used a
ClientRequestTokenwith the same parameters within the last 10 minutes.
To avoid this error, make sure that you use unique identifiers and parameters for each request within the specified time period.
Parameters:
-
name(Optional[WirelessGatewayName], default:None) –The name of the new resource.
The following special characters aren't accepted:
<>^#~$ -
description(Optional[Description], default:None) –The description of the new resource.
-
lo_ra_wan(LoRaWANGateway) –The gateway configuration information to use to create the wireless gateway.
-
tags(Optional[TagList], default:None) –The tags to attach to the new wireless gateway. Tags are metadata that you can use to manage a resource.
-
client_request_token(Optional[ClientRequestToken], default:None) –Each resource must have a unique client request token. The client token is used to implement idempotency. It ensures that the request completes no more than one time. If you retry a request with the same token and the same parameters, the request will complete successfully. However, if you try to create a new resource using the same token but different parameters, an HTTP 409 conflict occurs. If you omit this value, AWS SDKs will automatically generate a unique client request. For more information about idempotency, see Ensuring idempotency in Amazon EC2 API requests.
Raises:
-
AccessDeniedException–User does not have permission to perform this action.
-
ConflictException–Adding, updating, or deleting the resource can cause an inconsistent state.
-
InternalServerException–An unexpected error occurred while processing a request.
-
ThrottlingException–The request was denied because it exceeded the allowed API request rate.
-
ValidationException–The input did not meet the specified constraints.
-
UnknownServiceError–The service returned an error code this client does not model.
Source code in docs_src/capo_iot_wireless/_services/async_io_t_wireless.py
1487 1488 1489 1490 1491 1492 1493 1494 1495 1496 1497 1498 1499 1500 1501 1502 1503 1504 1505 1506 1507 1508 1509 1510 1511 1512 1513 1514 1515 1516 1517 1518 1519 1520 1521 1522 1523 1524 1525 1526 1527 1528 1529 1530 1531 1532 1533 1534 1535 1536 1537 1538 1539 1540 1541 1542 1543 1544 1545 1546 1547 1548 1549 1550 1551 1552 1553 1554 1555 1556 | |