AWS location documentation change
Summary
Updated security section with IAM policy link, added new sections for resource management/billing/quotas, and modified API reference links
Security assessment
The change enhances security documentation by adding IAM policy guidance and PII handling warnings, but doesn't address a specific vulnerability. Security improvements are preventive best practices.
Diff
diff --git a/location/latest/developerguide/best-practices.md b/location/latest/developerguide/best-practices.md similarity index 57% rename from /root/aws-docs-changes/docs/2025-12-22_00-00-03/location/latest/developerguide/best-practices.md rename to /root/aws-docs-changes/docs/2025-12-25_00-00-05/location/previous/developerguide/best-practices.md index a41f29f2a..de79e8f7e 100644 --- a//location/latest/developerguide/best-practices.md +++ b//location/previous/developerguide/best-practices.md @@ -1 +1 @@ -[](/pdfs/location/latest/developerguide/amazon-location-developer-guide.pdf#best-practices "Open PDF") +[](/pdfs/location/previous/developerguide/amazon-location-developer-guide.pdf#best-practices "Open PDF") @@ -3 +3 @@ -[Documentation](/index.html)[Amazon Location Service](/location/index.html)[Developer Guide](what-is.html) +[Documentation](/index.html)[Amazon Location Service](/location/index.html)[Developer Guide](what-is-previous.html) @@ -5 +5 @@ -Security +SecurityResource managementBilling and cost managementQuotas and usage @@ -14,0 +15,6 @@ This topic provides best practices to help you use Amazon Location Service. Whil + * Resource management + + * Billing and cost management + + * Quotas and usage + @@ -24 +30 @@ To help manage or even avoid security risks, consider the following best practic - * Follow the Principle of Least Privilege to grant only the minimum required access to your Amazon Location Service resources. + * Follow the Principle of Least Privilege to grant only the minimum required access to your Amazon Location Service resources. For more information, see [Managing access using policies](./security-iam.html#security_iam_access-manage). @@ -65 +71 @@ Always use encrypted connections, such as those that begin with `https://` to ke -When you create custom policies to Amazon Location resources, grant only the permissions required to perform a task. It's recommended to start with a minimum set of permissions and grant additional permissions as needed. Implementing least privilege access is essential to reducing the risk and impact that could result from errors or malicious attacks. For more information, see [Use AWS Identity and Access Management to authenticate](./security-iam.html). +When you create custom policies to Amazon Location resources, grant only the permissions required to perform a task. It's recommended to start with a minimum set of permissions and grant additional permissions as needed. Implementing least privilege access is essential to reducing the risk and impact that could result from errors or malicious attacks. For more information, see [Identity and Access Management for Amazon Location Service](./security-iam.html). @@ -86 +92,42 @@ Use the following conventions for device IDs. -When sending device updates (for example, using [DevicePositionUpdate](https://docs.aws.amazon.com/location/latest/APIReference/API_DevicePositionUpdate.html)), do not include personally-identifiable information (PII) such as phone number or email address in the `PositionProperties`. +When sending device updates (for example, using [DevicePositionUpdate](https://docs.aws.amazon.com/location/previous/APIReference/API_DevicePositionUpdate.html)), do not include personally-identifiable information (PII) such as phone number or email address in the `PositionProperties`. + +## Resource management + +To help effectively manage your location resources in Amazon Location Service, consider the following best practices: + + * Use regional endpoints that are central to your expected user base to improve their experience. For information about region endpoints, see [Amazon Location regions and endpoints](./location-regions.html). + + * For resources that use data providers, such as map resources and place index resources, make sure to follow the terms of use agreement of the specific data provider. For more information, see [Data providers](./what-is-data-provider.html). + + * Minimize the creation of resources by having one resource for each configuration of map, place index, or routes. Within a region, you typically need only one resource per data provider or map style. Most applications use existing resources, and do not create resources at run time. + + * When using different resources in a single application, such as a map resource and a route calculator, use the same data provider in each resource to ensure that the data matches. For example, that a route geometry you create with your route calculator aligns with the streets on the map drawn using the map resource. + + + + +## Billing and cost management + +To help manage your costs and billing, consider the following best practice: + + * Use monitoring tools, such as Amazon CloudWatch, to track your resource usage. You can set alerts that notify you when usage is about to exceed your specified limits. For more information, see [Creating a Billing Alarm to Monitor Your Estimated AWS Charges](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/monitor_estimated_charges_with_cloudwatch.html) in the _Amazon CloudWatch User Guide_. + + + + +## Quotas and usage + +You AWS account includes quotas that set a default limit your usage amount. You can set up alarms to alert you when your usage is getting close to your limit, and you can request a raise to a quota, when you need it. For information about how to work with quotas, see the following topics. + + * [Amazon Location Service quotas](./location-quotas.html) + + * [Use CloudWatch to monitor usage against quotas](./monitoring-using-cloudwatch.html#alarms-on-quotas) + + * [ Visualizing your service quotas and setting alarms](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-Quotas-Visualize-Alarms.html) in the _Amazon CloudWatch User Guide_. + + + + +You can create alarms to give you advance warning when you are close to exceeding your limits. We recommend setting alarms for each quota in each AWS Region where you use Amazon Location. For example, you can monitor your use of the `SearchPlaceIndexForText` operation, and create an alarm when you exceed 80 percent of your current quota. + +When you get an alarm warning about your quota, you must decide what to do. You might be using additional resources because your customer base has grown. In that case you may want to request an increase to your quota, such as a 50 percent increase in the quota for an API call in that Region. Or, maybe there's an error in your service that causes you to make additional unnecessary calls to Amazon Location. In that case you'd want to solve the problem in your service.