update_tracker
async
¶
update_tracker(
tracker_name: ResourceName,
*,
config_overrides: Optional[AsyncLocationClientConfig] = None,
pricing_plan: Optional[PricingPlan] = None,
pricing_plan_data_source: Optional[str] = None,
description: Optional[ResourceDescription] = None,
position_filtering: Optional[PositionFiltering] = None,
event_bridge_enabled: Optional[bool] = None,
kms_key_enable_geospatial_queries: Optional[bool] = None,
) -> UpdateTrackerResponse
Updates the specified properties of a given tracker resource.
Parameters:
-
tracker_name(ResourceName) –The name of the tracker resource to update.
-
pricing_plan(Optional[PricingPlan], default:None) –No longer used. If included, the only allowed value is
RequestBasedUsage. -
pricing_plan_data_source(Optional[str], default:None) –This parameter is no longer used.
-
description(Optional[ResourceDescription], default:None) –Updates the description for the tracker resource.
-
position_filtering(Optional[PositionFiltering], default:None) –Updates the position filtering for the tracker resource.
Valid values:
-
TimeBased- Location updates are evaluated against linked geofence collections, but not every location update is stored. If your update frequency is more often than 30 seconds, only one update per 30 seconds is stored for each unique device ID. -
DistanceBased- If the device has moved less than 30 m (98.4 ft), location updates are ignored. Location updates within this distance are neither evaluated against linked geofence collections, nor stored. This helps control costs by reducing the number of geofence evaluations and historical device positions to paginate through. Distance-based filtering can also reduce the effects of GPS noise when displaying device trajectories on a map. -
AccuracyBased- If the device has moved less than the measured accuracy, location updates are ignored. For example, if two consecutive updates from a device have a horizontal accuracy of 5 m and 10 m, the second update is ignored if the device has moved less than 15 m. Ignored location updates are neither evaluated against linked geofence collections, nor stored. This helps educe the effects of GPS noise when displaying device trajectories on a map, and can help control costs by reducing the number of geofence evaluations.
-
-
event_bridge_enabled(Optional[bool], default:None) –Whether to enable position
UPDATEevents from this tracker to be sent to EventBridge.You do not need enable this feature to get
ENTERandEXITevents for geofences with this tracker. Those events are always sent to EventBridge. -
kms_key_enable_geospatial_queries(Optional[bool], default:None) –Enables
GeospatialQueriesfor a tracker that uses a Amazon Web Services KMS customer managed key.This parameter is only used if you are using a KMS customer managed key.
Raises:
-
AccessDeniedException–The request was denied because of insufficient access or permissions. Check with an administrator to verify your permissions.
-
InternalServerException–The request has failed to process because of an unknown server error, exception, or failure.
-
ResourceNotFoundException–The resource that you've entered was not found in your AWS account.
-
ThrottlingException–The request was denied because of request throttling.
-
ValidationException–The input failed to meet the constraints specified by the AWS service.
-
UnknownServiceError–The service returned an error code this client does not model.
Source code in docs_src/capo_location/_services/async_location.py
4227 4228 4229 4230 4231 4232 4233 4234 4235 4236 4237 4238 4239 4240 4241 4242 4243 4244 4245 4246 4247 4248 4249 4250 4251 4252 4253 4254 4255 4256 4257 4258 4259 4260 4261 4262 4263 4264 4265 4266 4267 4268 4269 4270 4271 4272 4273 4274 4275 4276 4277 4278 4279 4280 4281 4282 4283 4284 4285 4286 4287 4288 4289 4290 4291 4292 4293 4294 4295 4296 4297 4298 4299 4300 4301 4302 4303 4304 4305 4306 4307 4308 4309 4310 4311 4312 4313 | |