asp.net core 6 app - Access Denied
Before opening, please confirm:
- [X] I have checked to see if my question is addressed in the FAQ.
- [X] I have searched for duplicate or closed issues.
- [X] I have read the guide for submitting bug reports.
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
App Id
d34fcwfeedlxri
Region
us-east-1
Amplify Hosting feature
Access control
Describe the bug
When I open the app url https://prod.d34fcwfeedlxri.amplifyapp.com, it gives access denied error.
Expected behavior
it should open the app.
Reproduction steps
- I uploaded a zip file containing build output of asp.net core 6 site.
- Deployment succeeded.
- Got this url - https://prod.d34fcwfeedlxri.amplifyapp.com/
- When I go to this irl, it gives me access denied error
AccessDenied
Build Settings
No response
Additional information
No response
Hi @paresh-bhatewra 👋🏽 it looks like you removed your app so I'm not able to further investigate. Did you navigate into the build output folder and zip the contents? If you just zip the folder itself you can run into this error. Please see our Manual Deploy documentation for more details on this error: https://docs.aws.amazon.com/amplify/latest/userguide/manual-deploys.html
Hey,
I had gone through that article before raising the ticket, and I confirm that I created the zip in correct way as mentioned. I have again deployed the same zip with same error.
https://prod.d2ethzgr24y9e0.amplifyapp.com//
Let me know what I am doing wrong.
@hloriana - any update?
@paresh-bhatewra 👋 , thanks for reaching out. The 404 error can occur if the index.html file is not present or is nested under a directory in the zip file. To get started with deploying .NET apps on Amplify Hosting, refer to this blog post: https://aws.amazon.com/blogs/devops/deploy-net-blazor-webassembly-application-to-aws-amplify/.
This issue is now closed. Comments on closed issues are hard for our team to see. If you need more assistance, please open a new issue that references this one.
This issue has been automatically locked.