create_dataflow_endpoint_group
async
¶
create_dataflow_endpoint_group(
endpoint_details: EndpointDetailsList,
*,
config_overrides: Optional[AsyncGroundStationClientConfig] = None,
tags: Optional[TagsMap] = None,
contact_pre_pass_duration_seconds: Optional[
DataflowEndpointGroupDurationInSeconds
] = None,
contact_post_pass_duration_seconds: Optional[
DataflowEndpointGroupDurationInSeconds
] = None,
) -> DataflowEndpointGroupIdResponse
Creates a DataflowEndpoint group containing the specified list of DataflowEndpoint objects.
The name field in each endpoint is used in your mission profile DataflowEndpointConfig to specify which endpoints to use during a contact.
When a contact uses multiple DataflowEndpointConfig objects, each Config must match a DataflowEndpoint in the same group.
Parameters:
-
endpoint_details(EndpointDetailsList) –Endpoint details of each endpoint in the dataflow endpoint group. All dataflow endpoints within a single dataflow endpoint group must be of the same type. You cannot mix AWS Ground Station Agent endpoints with Dataflow endpoints in the same group. If your use case requires both types of endpoints, you must create separate dataflow endpoint groups for each type.
-
tags(Optional[TagsMap], default:None) –Tags of a dataflow endpoint group.
-
contact_pre_pass_duration_seconds(Optional[DataflowEndpointGroupDurationInSeconds], default:None) –Amount of time, in seconds, before a contact starts that the Ground Station Dataflow Endpoint Group will be in a
PREPASSstate. A Ground Station Dataflow Endpoint Group State Change event will be emitted when the Dataflow Endpoint Group enters and exits thePREPASSstate. -
contact_post_pass_duration_seconds(Optional[DataflowEndpointGroupDurationInSeconds], default:None) –Amount of time, in seconds, after a contact ends that the Ground Station Dataflow Endpoint Group will be in a
POSTPASSstate. A Ground Station Dataflow Endpoint Group State Change event will be emitted when the Dataflow Endpoint Group enters and exits thePOSTPASSstate.
Raises:
-
DependencyException–Dependency encountered an error.
-
InvalidParameterException–One or more parameters are not valid.
-
ResourceNotFoundException–Resource was not found.
-
UnknownServiceError–The service returned an error code this client does not model.
Source code in docs_src/capo_groundstation/_services/async_ground_station.py
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 1557 1558 1559 1560 1561 1562 1563 1564 1565 1566 1567 1568 1569 1570 1571 1572 1573 1574 1575 1576 1577 1578 1579 1580 1581 1582 | |