create_campaign
¶
create_campaign(
name: campaignName,
signal_catalog_arn: arn,
target_arn: arn,
collection_scheme: CollectionScheme,
*,
config_overrides: Optional[IoTFleetWiseClientConfig] = None,
description: Optional[description] = None,
start_time: Optional[timestamp] = None,
expiry_time: Optional[timestamp] = None,
post_trigger_collection_duration: Optional[uint32] = None,
diagnostics_mode: Optional[DiagnosticsMode] = None,
spooling_mode: Optional[SpoolingMode] = None,
compression: Optional[Compression] = None,
priority: Optional[priority] = None,
signals_to_collect: Optional[SignalInformationList] = None,
data_extra_dimensions: Optional[DataExtraDimensionNodePathList] = None,
tags: Optional[TagList] = None,
data_destination_configs: Optional[DataDestinationConfigs] = None,
data_partitions: Optional[DataPartitions] = None,
signals_to_fetch: Optional[SignalFetchInformationList] = None,
) -> CreateCampaignResponse
Creates an orchestration of data collection rules. The Amazon Web Services IoT FleetWise Edge Agent software running in vehicles uses campaigns to decide how to collect and transfer data to the cloud. You create campaigns in the cloud. After you or your team approve campaigns, Amazon Web Services IoT FleetWise automatically deploys them to vehicles.
For more information, see Collect and transfer data with campaigns in the Amazon Web Services IoT FleetWise Developer Guide.
Access to certain Amazon Web Services IoT FleetWise features is currently gated. For more information, see Amazon Web Services Region and feature availability in the Amazon Web Services IoT FleetWise Developer Guide.
Parameters:
-
name(campaignName) –The name of the campaign to create.
-
description(Optional[description], default:None) –An optional description of the campaign to help identify its purpose.
-
signal_catalog_arn(arn) –The Amazon Resource Name (ARN) of the signal catalog to associate with the campaign.
-
target_arn(arn) –The ARN of the vehicle or fleet to deploy a campaign to.
-
start_time(Optional[timestamp], default:None) –The time, in milliseconds, to deliver a campaign after it was approved. If it's not specified,
0is used.Default:
0 -
expiry_time(Optional[timestamp], default:None) –The time the campaign expires, in seconds since epoch (January 1, 1970 at midnight UTC time). Vehicle data isn't collected after the campaign expires.
Default: 253402214400 (December 31, 9999, 00:00:00 UTC)
-
post_trigger_collection_duration(Optional[uint32], default:None) –How long (in milliseconds) to collect raw data after a triggering event initiates the collection. If it's not specified,
0is used.Default:
0 -
diagnostics_mode(Optional[DiagnosticsMode], default:None) –Option for a vehicle to send diagnostic trouble codes to Amazon Web Services IoT FleetWise. If you want to send diagnostic trouble codes, use
SEND_ACTIVE_DTCS. If it's not specified,OFFis used.Default:
OFF -
spooling_mode(Optional[SpoolingMode], default:None) –Determines whether to store collected data after a vehicle lost a connection with the cloud. After a connection is re-established, the data is automatically forwarded to Amazon Web Services IoT FleetWise. If you want to store collected data when a vehicle loses connection with the cloud, use
TO_DISK. If it's not specified,OFFis used.Default:
OFF -
compression(Optional[Compression], default:None) –Determines whether to compress signals before transmitting data to Amazon Web Services IoT FleetWise. If you don't want to compress the signals, use
OFF. If it's not specified,SNAPPYis used.Default:
SNAPPY -
priority(Optional[priority], default:None) –A number indicating the priority of one campaign over another campaign for a certain vehicle or fleet. A campaign with the lowest value is deployed to vehicles before any other campaigns. If it's not specified,
0is used.Default:
0 -
signals_to_collect(Optional[SignalInformationList], default:None) –A list of information about signals to collect.
If you upload a signal as a condition in a data partition for a campaign, then those same signals must be included in
signalsToCollect. -
collection_scheme(CollectionScheme) –The data collection scheme associated with the campaign. You can specify a scheme that collects data based on time or an event.
-
data_extra_dimensions(Optional[DataExtraDimensionNodePathList], default:None) –A list of vehicle attributes to associate with a campaign.
Enrich the data with specified vehicle attributes. For example, add
makeandmodelto the campaign, and Amazon Web Services IoT FleetWise will associate the data with those attributes as dimensions in Amazon Timestream. You can then query the data againstmakeandmodel.Default: An empty array
-
tags(Optional[TagList], default:None) –Metadata that can be used to manage the campaign.
-
data_destination_configs(Optional[DataDestinationConfigs], default:None) –The destination where the campaign sends data. You can send data to an MQTT topic, or store it in Amazon S3 or Amazon Timestream.
MQTT is the publish/subscribe messaging protocol used by Amazon Web Services IoT to communicate with your devices.
Amazon S3 optimizes the cost of data storage and provides additional mechanisms to use vehicle data, such as data lakes, centralized data storage, data processing pipelines, and analytics. Amazon Web Services IoT FleetWise supports at-least-once file delivery to S3. Your vehicle data is stored on multiple Amazon Web Services IoT FleetWise servers for redundancy and high availability.
You can use Amazon Timestream to access and analyze time series data, and Timestream to query vehicle data so that you can identify trends and patterns.
-
data_partitions(Optional[DataPartitions], default:None) –The data partitions associated with the signals collected from the vehicle.
-
signals_to_fetch(Optional[SignalFetchInformationList], default:None) –A list of information about signals to fetch.
Raises:
-
InternalServerException–The request couldn't be completed because the server temporarily failed.
-
AccessDeniedException–You don't have sufficient permission to perform this action.
-
ConflictException–The request has conflicting operations. This can occur if you're trying to perform more than one operation on the same resource at the same time.
-
LimitExceededException–A service quota was exceeded.
-
ResourceNotFoundException–The resource wasn't found.
-
ThrottlingException–The request couldn't be completed due to throttling.
-
ValidationException–The input fails to satisfy the constraints specified by an Amazon Web Services service.
-
UnknownServiceError–The service returned an error code this client does not model.
Source code in docs_src/capo_iotfleetwise/_services/io_t_fleet_wise.py
973 974 975 976 977 978 979 980 981 982 983 984 985 986 987 988 989 990 991 992 993 994 995 996 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 1025 1026 1027 1028 1029 1030 1031 1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 | |