create_tracker
¶
create_tracker(
tracker_name: ResourceName,
*,
config_overrides: Optional[LocationClientConfig] = None,
pricing_plan: Optional[PricingPlan] = None,
kms_key_id: Optional[KmsKeyId] = None,
pricing_plan_data_source: Optional[str] = None,
description: Optional[ResourceDescription] = None,
tags: Optional[TagMap] = None,
position_filtering: Optional[PositionFiltering] = None,
event_bridge_enabled: Optional[bool] = None,
kms_key_enable_geospatial_queries: Optional[bool] = None,
) -> CreateTrackerResponse
Creates a tracker resource in your Amazon Web Services account, which lets you retrieve current and historical location of devices.
Parameters:
-
tracker_name(ResourceName) –The name for the tracker resource.
Requirements:
-
Contain only alphanumeric characters (A-Z, a-z, 0-9) , hyphens (-), periods (.), and underscores (_).
-
Must be a unique tracker resource name.
-
No spaces allowed. For example,
ExampleTracker.
-
-
pricing_plan(Optional[PricingPlan], default:None) –No longer used. If included, the only allowed value is
RequestBasedUsage. -
kms_key_id(Optional[KmsKeyId], default:None) –A key identifier for an Amazon Web Services KMS customer managed key. Enter a key ID, key ARN, alias name, or alias ARN.
-
pricing_plan_data_source(Optional[str], default:None) –This parameter is no longer used.
-
description(Optional[ResourceDescription], default:None) –An optional description for the tracker resource.
-
tags(Optional[TagMap], default:None) –Applies one or more tags to the tracker resource. A tag is a key-value pair helps manage, identify, search, and filter your resources by labelling them.
Format:
"key" : "value"Restrictions:
-
Maximum 50 tags per resource
-
Each resource tag must be unique with a maximum of one value.
-
Maximum key length: 128 Unicode characters in UTF-8
-
Maximum value length: 256 Unicode characters in UTF-8
-
Can use alphanumeric characters (A–Z, a–z, 0–9), and the following characters: + - = . _ : / @.
-
Cannot use "aws:" as a prefix for a key.
-
-
position_filtering(Optional[PositionFiltering], default:None) –Specifies 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 area 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 can reduce the effects of GPS noise when displaying device trajectories on a map, and can help control your costs by reducing the number of geofence evaluations.
This field is optional. If not specified, the default value is
TimeBased. -
-
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.
If you wish to encrypt your data using your own KMS customer managed key, then the Bounding Polygon Queries feature will be disabled by default. This is because by using this feature, a representation of your device positions will not be encrypted using the your KMS managed key. The exact device position, however; is still encrypted using your managed key.
You can choose to opt-in to the Bounding Polygon Quseries feature. This is done by setting the
KmsKeyEnableGeospatialQueriesparameter to true when creating or updating a Tracker.
Raises:
-
AccessDeniedException–The request was denied because of insufficient access or permissions. Check with an administrator to verify your permissions.
-
ConflictException–The request was unsuccessful because of a conflict.
-
InternalServerException–The request has failed to process because of an unknown server error, exception, or failure.
-
ServiceQuotaExceededException–The operation was denied because the request would exceed the maximum quota set for Amazon Location Service.
-
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/location.py
4013 4014 4015 4016 4017 4018 4019 4020 4021 4022 4023 4024 4025 4026 4027 4028 4029 4030 4031 4032 4033 4034 4035 4036 4037 4038 4039 4040 4041 4042 4043 4044 4045 4046 4047 4048 4049 4050 4051 4052 4053 4054 4055 4056 4057 4058 4059 4060 4061 4062 4063 4064 4065 4066 4067 4068 4069 4070 4071 4072 4073 4074 4075 4076 4077 4078 4079 4080 4081 4082 4083 4084 4085 4086 4087 4088 4089 4090 4091 4092 4093 4094 4095 4096 4097 4098 4099 4100 4101 4102 4103 4104 4105 4106 4107 | |