Publish an Angular with .NET CORE app to IIS on AWS Cloud EC2 instance

I faced a few challenges while publishing my application(Front end on Angular 13, Backend is .NET CORE 6) to IIS on AWS EC2 instance using Custom Identity. So I thought of sharing this post which will help you to fix the issue quickly.

It is a straight forward process to publish an application to IIS without using custom identity and many are already aware of this process. When we create an Application Pool by default it uses Application Pool Identity. In many cases we can not use Application Pool Identity. For example if your application is accessing web share or network share then your application needs to have required permission to access these shares. In this case you will have to create a Service Account and provide necessary permission to your Service Account to access these shares. Then you need to use this Service Account as Identity instead of Application Pool Identity to set up your application.

However if you want to use another identity then we have to make sure your new identity has the required permissions to access the app's folder and configuration. 

Follow the below steps to host Angular with .NET Core application on Amazon EC2 instance using custom identity (ServiceAccount).

1.      Open IIS using inetmgr command.

2.      Create a new application pool using the Add Application pool option.

3.      Open Advanced Settings option. Change Identity from Application Pool Identity to Custom Identity. Use the Service Account which you have already created for your application. (Note: Application Pool Identity may not have required permission to access web share if you are using web share in your application. Hence it is recommended to use your own application specific Service Accounts)

4.      Go to Sites Click on Add Website from the contextual menu.

5.      Enter Site Name and select the Application Pool which you created in the previous steps.

6.      Set the Physical path to the app's deployment folder that you created. It’s recommended to use inetpub/wwwroot folder for deployment folder for .NET CORE applications.

7.      Provide the Binding configuration and create the website by selecting OK. Don’t use port number 80, this can open up your app to security vulnerabilities.

8.      Verify that your service account (custom identity) has the required permissions to access the app’s folder.

9.      To verify the permission of your identity, go to wwwroot/yourappfolder and open the properties dialog and go to Security Tab and check your service account is listed there.

10.   If your service account is not listed then click on Edit and Add your Service Account and give required permission.

11.   You should be able to launch your application from Browser now.

12.   If you are getting 500 internal server errors you have to do the following to fix it.

·        Go to IIS and click on your Web site

·        Double click on the Authentication button and then click on Anonymous Authentication.

·        Click on Edit option under Actions section

·        Set Specific User as your Service Account user.

·        This should fix the 500 internal server errors.

13.   If you are getting “The current identity (NW\SVCAccountName) does not have write access to 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files'” error follow the below steps to fix it.

·        Open a command prompt window "as administrator"

·        Run the below command C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Aspnet_regiis.exe -ga server\user

Replace server\user with the username that your application pool runs under. This gives that identity access to the IIS configuration and other directories used by ASP.NET.


Comments

Post a Comment

Popular posts from this blog

Belekeri, Karwar Beach Photos

Image
Belekeri Beach : Situated 8 kms away from Ankola is an old port of Belekin with the long stretches of unexplored beaches. Situated at the bay of the river Belekin. The place has two temples of Jenubeera and Ishwara and also an old inscription dating back to the 15th century. Belekeri Port was a good port during the time of British, and managenese ore was being exported from here. The beautiful beach here attracts many tourists
Read more

Micro-front end, future of frontend architecture.

Before moving into Micro frontend lets understand the evolution of software architecture. Software usually contains 3 layers. frontend, backend and storage (DB). Front end will be in the form of a user interface, And the backend will normally have your main business logic. Storage is where the data is stored.   Earlier we used to have a monolithic application where your front and backend used to be bundled in one application. They used to reside in a single code repository. This entire application used to be maintained by 1 large team. For changing anything in the application you need to test the entire application because even a small change can break any part of the application that is unrelated to the change. Industry soon realized the need to split the front end and back-end part of the code. This enabled a specialized team for frontend and backend.  Later backend services started using Microservices to decouple the code and improve scaling. Microservices architect...
Read more

Handle errors in ASP.NET Core web APIs

Image
Handle errors in ASP.NET Core web APIs Exception handling is one of the critical areas in modern web application development. If exceptions are not handled properly, the whole app can be terminated, causing severe issues for users and developers. Try-catch blocks are widely used in apps to handle exceptions. They are the most basic way of handling exceptions. ​ The above example is a typical case where we use try-catch block to handle the exception. The try-catch block method is ideal for novice developers, and it is something that every developer should be aware of. However, this technique has a disadvantage when working with massive projects with complex architectures. In such cases we have to use Exception Handling Middleware to handle the exceptions. Exception handler In Program.cs, call UseExceptionHandler to add the Exception Handling Middleware: ​ Configure a controller action to respond to the /error route: ​ Add [ApiExplorerSettings] attribute and set its IgnoreApi property t...
Read more