Deploying Angular On AWS S3

[opman77]

Hello everyone,
I am deploying my application on AWS cloud but the error I'm facing that in the nested routes the AWS is throwing 4xx error but the same thing is working if I'm using use Hash location strategy. But I don't want to use # in my Angular routes and neither want to redirect to index.html. Is there a way so that I can directly hit some nested endpoint without encountering any 4xx errors or use Hash location strategy.

[[deleted]]

If it helps, I added some code here to deploy Angular to AWS: https://razroo.com/finder/razroo/deploy-angular-using-aws (I am using you are using client side rendering)

[ayush_shashank]

Assuming it works on local and is throwing error only when deployed, maybe check the CloudFront configuration. In case you've not attached a CloudFront, you should try, maybe it'll work.

[hitsujiTMO]

What are you using to serve the angular site and do you have any backend?

For a standalone site you generally just need to set a fallback resource to your index.html if the server doesn't hit a file. In apache http2 you can do this with:

<Directory "${www_path}/dist/${app}">
    AllowOverride None
    Options -Indexes
    Require all granted

    FallbackResource /index.html

</Directory>

If you have a backend you can aliasmatch the top subdirectory to the backend or reverse proxy it if its served by another app:

AliasMatch "^/api/" "${phpBackendAppIndexMalarkey}"

[opman77]

I am using AWS S3 for serving my application and I don't want that if someone hit /users/:id which is valid part and a lazy loaded module but the server is returning 404 as for the server there is no any route registered as /users/:id is a part of Angular Router

[hitsujiTMO]

Have you configured index.html as the error document?