aws-location: Map, PlaceIndex and RouteCalculator constructs should be marked as legacy

[mazyu36]

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

• I may be able to implement this feature request
• This feature might incur a breaking change

CDK version used

2.173.4

Environment details (OS name and version, etc.)

All

[ashishdhingra]

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.

[mazyu36]

Thank you for the reply.
The new enhanced Places, Routes, and Maps utilize AWS-managed resources, eliminating the need for users to create resources themselves.
Therefore, no separated resources exist.

Given this, there is currently no need to use the constructs related to Places, Routes, and Maps.
However, I suggest we keep these constructs for backward compatibility and propose documenting them as legacy in the docs.