Optimizing Nested Resource Structure in API Gateway

I have a REST API set up in AWS API Gateway, and I'm trying to streamline the endpoint structure for improved performance and manageability. My API serves various resources under a nested path, specifically /rest/workspaces/coveragestores/coverages. Here's how I currently have to structure my resources to make this work: ) Each of these paths is set up as a separate resource, and I need to define methods (like GET, POST, etc.) for each one. This structure is becoming complex and cumbersome to manage, especially as more nested resources and methods are added. I appreciate any guidance or resources you could point me to, including documentation, tutorials, or personal experiences with similar API setups.

Thank you for your time and assistance!