Routes being generated for Lambda deployment #2159

Qkessler · 2024-01-04T15:24:53Z

Qkessler
Jan 4, 2024

Hi there!

I have been using leptos for a personal project at Amazon, trying at the same time to get a better grasp of Web development in Rust. So far, local development has been great, loved having cargo-leptos for hot-reloading and more.

Once I had something quick locally (just a main page), wanted to move to deploy it in a Lambda, and I was able to do so, by using cargo-leptos and cargo-lambda with the example start-aws. No issue there. The question comes around understanding what are the routes being defined when deployed this way.

When running cargo leptos watch, my localhost on the main path shows the HomePage and I would expect it to be the same way when deploying to Lambda. To avoid the XY Problem:

I have a Route53 domain connected to an API Gateway that connects to the Lambda I deployed with my Leptos code base. When contacting the Route53 domain (also tested the API Gateway directly), I see that the Lambda is invoked, but it returns an 404 page.

<script type="module">
    function idle(c) {
        if ("requestIdleCallback" in window) {
            window.requestIdleCallback(c);
        } else {
            c();
        }
    }
idle(() => {
    import('/pkg/amzn-gota-a-gota.js')
        .then(mod => {
            mod.default('/pkg/amzn-gota-a-gota.wasm').then(() => mod.hydrate());
        })
});
</script>
    
</head><body><!--hk=0-0-0-4--><!--hk=0-0-0-6--><!--hk=0-0-0-8--><!--hk=0-0-0-9--><main data-hk="0-0-0-12"><h1 data-hk="0-0-0-18">Error</h1><h2 data-hk="0-0-0-21">404 Not Found</h2><p data-hk="0-0-0-22">Error: Not Found</p><!--hk=0-0-0-20--><!--hk=0-0-0-23--><!--hk=0-0-0-19--><!--hk=0-0-0-17--><!--hk=0-0-0-16--><!--hk=0-0-0-15--><!--hk=0-0-0-13--></main><!--hk=0-0-0-11--><!--hk=0-0-0-10--><!--hk=0-0-0-2--><!--hk=0-0-0-1--><script>__LEPTOS_PENDING_RESOURCES = [];__LEPTOS_RESOLVED_RESOURCES = new Map();__LEPTOS_RESOURCE_RESOLVERS = new Map();__LEPTOS_LOCAL_ONLY = [];</script></body></html>

Following that set up, I thought that Leptos would set up the "" route to be pointing to the HomePage (haven't modified that, it's part of the start-aws example), hence the connection directly with a GET method to the root method would return that page.

Any guidance / pointers? I'll keep investigating whether the API Gateway is changing the method to contact the Lambda.

Qkessler · 2024-01-04T15:28:15Z

Qkessler
Jan 4, 2024
Author

Some logs:

2024-01-04T16:09:13.924+01:00	2024-01-04T15:09:13.924Z INFO [lambda_runtime] Lambda runtime invoke; requestId="113cbf64-9cfc-4b15-8037-89e2dc197199" xrayTraceId="Root=1-6596ca19-3a9659764a89a1371d977e26;Parent=6cc497fb35185750;Sampled=0;Lineage=12f4e23c:0"
2024-01-04T16:09:13.924+01:00	2024-01-04T15:09:13.924Z DEBUG [hyper::proto::h1::decode] incoming chunked header: 0xB05 (2821 bytes)
2024-01-04T16:09:13.924+01:00	2024-01-04T15:09:13.924Z DEBUG [hyper::proto::h1::conn] incoming body completed
2024-01-04T16:09:13.924+01:00	2024-01-04T15:09:13.924Z DEBUG [hyper::client::pool] pooling idle connection for ("http", 127.0.0.1:9001)
2024-01-04T16:09:13.925+01:00	2024-01-04T15:09:13.925Z INFO [leptos_axum] render_app_to_stream;
2024-01-04T16:09:13.925+01:00	2024-01-04T15:09:13.925Z INFO [leptos_axum] render_app_to_stream_with_context;
2024-01-04T16:09:13.925+01:00	2024-01-04T15:09:13.925Z INFO [leptos_axum] render_app_to_stream_with_context_and_replace_blocks;
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z INFO [leptos_axum] generate_response;
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z INFO [tracing::span] render_to_stream_with_prefix_undisposed_with_context_and_block_replacement;
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z DEBUG [tracing::span] provide_context;
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z DEBUG [tracing::span] provide_context;
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z DEBUG [tracing::span] provide_context;
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z DEBUG [tracing::span] provide_context;
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z DEBUG [tracing::span] provide_context;
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z DEBUG [tracing::span] provide_context;
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z INFO [tracing::span] <App />;
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z DEBUG [tracing::span] use_context;
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z INFO [tracing::span] <Stylesheet />;
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z INFO [tracing::span] <Link />;
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z DEBUG [tracing::span] use_context;
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z DEBUG [tracing::span] use_context;
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z INFO [tracing::span] <() />;
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z INFO [tracing::span] <() />;
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z INFO [tracing::span] <Script />;
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z DEBUG [tracing::span] use_context;
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z DEBUG [tracing::span] use_context;
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z INFO [tracing::span] <() />;
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z INFO [tracing::span] <() />;
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z INFO [tracing::span] <Script />;
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z DEBUG [tracing::span] use_context;
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z DEBUG [tracing::span] use_context;
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z INFO [tracing::span] <() />;
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z INFO [tracing::span] <() />;
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z INFO [tracing::span] <Title />;
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z DEBUG [tracing::span] use_context;
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z INFO [tracing::span] <() />;
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z INFO [tracing::span] <() />;
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z INFO [tracing::span] <Router />;
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z DEBUG [tracing::span] use_context;
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z DEBUG [leptos_reactive::memo] Memo::run(); defined_at=/Users/enrikes/.cargo/registry/src/index.crates.io-6f17d22bba15001f/leptos_router-0.5.4/src/history/location.rs:22:20 ty=alloc::string::String
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z DEBUG [leptos_reactive::memo] Memo::run(); defined_at=/Users/enrikes/.cargo/registry/src/index.crates.io-6f17d22bba15001f/leptos_router-0.5.4/src/history/location.rs:10:15 ty=leptos_router::history::url::Url
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z DEBUG [tracing::span] provide_context;
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z DEBUG [tracing::span] provide_context;
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z INFO [tracing::span] <Routes />;
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z INFO [tracing::span] Routes;
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z DEBUG [tracing::span] use_context;
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z INFO [tracing::span] <Route />;
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z INFO [tracing::span] Route;
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z INFO [tracing::span] define_route;
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z INFO [tracing::span] create_routes;
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z DEBUG [tracing::span] use_context;
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z DEBUG [tracing::span] provide_context;
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z INFO [tracing::span] <DynChild />;
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z DEBUG [leptos_reactive::memo] Memo::run(); defined_at=/Users/enrikes/.cargo/registry/src/index.crates.io-6f17d22bba15001f/leptos_router-0.5.4/src/components/routes.rs:469:21 ty=core::option::Option<leptos_dom::View>
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z DEBUG [tracing::span] provide_context;
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z DEBUG [leptos_reactive::memo] Memo::run(); defined_at=/Users/enrikes/.cargo/registry/src/index.crates.io-6f17d22bba15001f/leptos_router-0.5.4/src/components/routes.rs:354:5 ty=leptos_router::components::routes::RouterState
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z DEBUG [leptos_reactive::memo] Memo::run(); defined_at=/Users/enrikes/.cargo/registry/src/index.crates.io-6f17d22bba15001f/leptos_router-0.5.4/src/components/routes.rs:344:9 ty=alloc::rc::Rc<alloc::vec::Vec<leptos_router::matching::RouteMatch>>
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z DEBUG [tracing::span] provide_context;
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z INFO [tracing::span] <ErrorTemplate />;
2024-01-04T16:09:13.941+01:00	Errors: [
2024-01-04T16:09:13.941+01:00	NotFound,
2024-01-04T16:09:13.941+01:00	]
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z DEBUG [tracing::span] use_context;
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z INFO [tracing::span] #text;
2024-01-04T16:09:13.941+01:00	2024-01-04T15:09:13.941Z INFO [tracing::span] <For />;
2024-01-04T16:09:13.942+01:00	2024-01-04T15:09:13.941Z INFO [tracing::span] For;
2024-01-04T16:09:13.942+01:00	2024-01-04T15:09:13.941Z INFO [tracing::span] <Each />;
2024-01-04T16:09:13.942+01:00	2024-01-04T15:09:13.942Z INFO [tracing::span] #text;
2024-01-04T16:09:13.942+01:00	2024-01-04T15:09:13.942Z INFO [tracing::span] #text;
2024-01-04T16:09:13.942+01:00	2024-01-04T15:09:13.942Z INFO [leptos_dom::components] <Component />; name=ErrorTemplate
2024-01-04T16:09:13.942+01:00	2024-01-04T15:09:13.942Z INFO [tracing::span] Option<T>;
2024-01-04T16:09:13.942+01:00	2024-01-04T15:09:13.942Z INFO [tracing::span] Option<T>;
2024-01-04T16:09:13.942+01:00	2024-01-04T15:09:13.942Z INFO [leptos_dom::components] <Component />; name=Routes
2024-01-04T16:09:13.942+01:00	2024-01-04T15:09:13.942Z INFO [leptos_dom::components] <Component />; name=Router
2024-01-04T16:09:13.942+01:00	2024-01-04T15:09:13.942Z INFO [leptos_dom::components] <Component />; name=App
2024-01-04T16:09:13.942+01:00	2024-01-04T15:09:13.942Z INFO [tracing::span] render_to_string;
2024-01-04T16:09:13.942+01:00	2024-01-04T15:09:13.942Z DEBUG [tracing::span] use_context;
2024-01-04T16:09:13.942+01:00	2024-01-04T15:09:13.942Z INFO [leptos_axum] forward_stream;
2024-01-04T16:09:13.942+01:00	2024-01-04T15:09:13.942Z DEBUG [tracing::span] use_context;
2024-01-04T16:09:13.942+01:00	2024-01-04T15:09:13.942Z INFO [tracing::span] render_to_string;
2024-01-04T16:09:13.942+01:00	2024-01-04T15:09:13.942Z INFO [tracing::span] render_to_string;
2024-01-04T16:09:13.942+01:00	2024-01-04T15:09:13.942Z INFO [tracing::span] render_to_string;

0 replies

Qkessler · 2024-01-04T15:28:57Z

Qkessler
Jan 4, 2024
Author

I'm specially curious about the Memo::run() invocation, where we seem to be calling a route that was present in my local machine?

0 replies

gbj · 2024-01-04T20:55:53Z

gbj
Jan 4, 2024
Maintainer

So, I haven't ever really used AWS lambdas so I might not be very useful. The HTML you put in your first post is very clearly a Leptos app rendering a 404 page; don't know more about your setup, but this is coming from some Leptos code, not a vendor 404 (see the data-hk bits on the <h2> and so on)

Some of the logs are clearly set to levels too high inside Leptos (yikes)

The Memo::run() isn't calling a route; it has a defined_at field that says where in your code that memo was defined. In this case it's inside the leptos_router package, which is why it's giving the URL of the downloaded cargo package.

9 replies

Qkessler Jan 5, 2024
Author

Wasn't able to make it work, maybe because I'm missing context on how the ServerIntegration context is generated. I added it inside HomePage and App to see if it would make a difference, but none of them have the context defined:

    if let Some(serverIntegration) = use_context::<ServerIntegration>() {
        log::info!("serverIntegration: {}", serverIntegration.path);
    };

Just to make sure, my idea with this is to see the path being contacted, say, what is the path that comes on the event to show the pages, to find why we are returning a NotFound.

CC @gbj

Qkessler Jan 5, 2024
Author

Was able to do it with RouterIntegrationContext, which is the one that is provided, here: https://github.com/leptos-rs/leptos/blob/main/integrations/axum/src/lib.rs#L967, though the issue is that the location whenever I try to log it (tried with create_effect as well) is the default one provided on the RouterIntegrationContext.

[amzn_gota_a_gota::components::pages] routerIntegration: LocationChange { value: "http://leptos.dev/", replace: false, scroll: true, state: State(None) }

That log is thrown inside the HomePage, but not running the use_context inside the view! macro, doing it outside.

gbj Jan 5, 2024
Maintainer

Oh sorry I probably gave you the wrong type, RouterIntegrationContext is correct.

I don't have enough insight into how AWS lambdas work to understand what's going on here. It might be helpful to add some kind of middleware here to try to log out the current request and what req.uri().path() is

https://github.com/leptos-rs/start-aws/blob/d477aab827e7c035cc8abb0d1324022714d5c34f/src/main.rs#L43-L47

Qkessler Jan 5, 2024
Author

That was a good idea, thanks so much! I did so with a Tower::Layer and here's the request:

2024-01-05T19:01:29.235Z INFO  [amzn_gota_a_gota::log_layer] request = Request { method: GET, uri: https://gamma.gota-a-gota.kindle.amazon.dev/prod/, version: HTTP/1.1, headers: {"accept": "*/*", "host": "gamma.gota-a-gota.kindle.amazon.dev", "user-agent": "curl/8.1.2", "x-amzn-trace-id": "Root=1-65985209-6bddf6bf1d4d3a234dd4d794;Parent=4564d5a54a0189d0;Sampled=0;Lineage=85ef7daa:0|92566622:0", "x-forwarded-for": "84.124.214.85", "x-forwarded-port": "443", "x-forwarded-proto": "https"}, body: Empty }, target =

From there I see that we are making a request to /prod/. For leptos_router, is that the same as defining a Route with prod? Do we need to have the trailing and preceding slash?

gbj Jan 5, 2024
Maintainer

Oh okay great! Making progress. There's been some recent discussion about trailing slashes (issue below), but as I understand it yes, in Axum /prod/ should be the same as defining a Route with /prod

#2154

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Routes being generated for Lambda deployment #2159

{{title}}

Replies: 3 comments 9 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

Select a reply

Routes being generated for Lambda deployment #2159

Qkessler Jan 4, 2024

Replies: 3 comments · 9 replies

Qkessler Jan 4, 2024 Author

Qkessler Jan 4, 2024 Author

gbj Jan 4, 2024 Maintainer

Qkessler Jan 5, 2024 Author

Qkessler Jan 5, 2024 Author

gbj Jan 5, 2024 Maintainer

Qkessler Jan 5, 2024 Author

gbj Jan 5, 2024 Maintainer

Qkessler
Jan 4, 2024

Replies: 3 comments 9 replies

Qkessler
Jan 4, 2024
Author

Qkessler
Jan 4, 2024
Author

gbj
Jan 4, 2024
Maintainer

Qkessler Jan 5, 2024
Author

Qkessler Jan 5, 2024
Author

gbj Jan 5, 2024
Maintainer

Qkessler Jan 5, 2024
Author

gbj Jan 5, 2024
Maintainer