-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
aws-location: Map, PlaceIndex and RouteCalculator constructs should be marked as legacy #32722
Comments
Unsure if there is separated resource specification for new enhanced Places, Routes, and Maps (these are not available as separated resources via CloudFormation or schema as of now). If these would be available as separate resources, we should mark existing ones as legacy. |
Comments on closed issues and PRs are hard for our team to see. |
1 similar comment
Comments on closed issues and PRs are hard for our team to see. |
… now legacy in README (aws#32871) Closes aws#32722. Amazon Location Service launches Enhanced Places, Routes, and Maps on Nov 8, 2024 ([Ref](https://aws.amazon.com/about-aws/whats-new/2024/11/amazon-location-service-enhanced-places-routes-maps/?nc1=h_ls)). New APIs for Maps, Places and Routes are launched and account-bound resources are no longer required. Therefore, I think it’s better to mention in the README that the constructs related to these are considered legacy. * Add a section for legacy resources in the README. * Move the descriptions related to Map, PlaceIndex, and RouteCalculator to that section. None None - [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
… now legacy in README (aws#32871) Closes aws#32722. Amazon Location Service launches Enhanced Places, Routes, and Maps on Nov 8, 2024 ([Ref](https://aws.amazon.com/about-aws/whats-new/2024/11/amazon-location-service-enhanced-places-routes-maps/?nc1=h_ls)). New APIs for Maps, Places and Routes are launched and account-bound resources are no longer required. Therefore, I think it’s better to mention in the README that the constructs related to these are considered legacy. * Add a section for legacy resources in the README. * Move the descriptions related to Map, PlaceIndex, and RouteCalculator to that section. None None - [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Describe the feature
Amazon Location Service launches Enhanced Places, Routes, and Maps on Nov 8, 2024 (Ref).
New APIs for Maps, Places and Routes are launched and account-bound resources are no longer required.

This is noted in the management console's feature spotlight.
Therefore Map, PlaceIndex and RouteCalculator constructs are now considered legacy.
I suggest marking these constructs as legacy in the docs.
Use Case
When use new Amazon Location APIs.
Proposed Solution
Add a note in the docs that these constructs are legacy.
Other Information
https://aws.amazon.com/blogs/aws/announcing-new-apis-for-amazon-location-service-routes-places-and-maps/
Acknowledgements
CDK version used
2.173.4
Environment details (OS name and version, etc.)
All
The text was updated successfully, but these errors were encountered: