DEV Community: sunilkumarmedium

AWS Systems Manager Hands-On

sunilkumarmedium — Thu, 10 Dec 2020 12:11:24 +0000

Introduction

Systems Manager management service helps you automatically collect
software inventory, apply OS patches and automate administration tasks and complex workflows.

You will also see how to eliminate the need for bastion hosts to manage your resources. You will review the below Systems Manager capabilities

Run Command
State Manager
Inventory
Patch Manager
Maintenance Window
Automation
Parameter Store
Session Manager
OpsCenter
Explorer
Change Calendar
Distributor

Pre-requisites
you will need:
✓ An AWS Account

If you don't have an account visit https://aws.amazon.com and click Sign Up.

Key Benefits

Hybrid
Cross-Platform Support
Scalable
AWS Optimized
No Complex Licensing Model
Partner Benefits

Systems Manager Building Blocks

SSM Agent installed in EC2 instances
Documents – series of steps executed in sequence. Versioned and shared across and used in run command, session manager, state manager

Registering instances in systems manager

Systems Manager Quick Setup
In AWS Management Console Search for Systems Manager this will take you to the home screen. In the left menu click on the Quick Setup for configuration.

Select the default roles to create or use the existing roles

Configuration Options

Targets

Manual Configuration

Create a role with Managed Policies attached and configure the IAM role to the EC2 instance

Run Command
Remotely and securely run configurations actions at scale
Accessible via console, CLI, and SDK

Monitoring
On-demand Patching
run bootstrap scripts on applications

State Manager
Used to Enable or Disable Services

Collecting Inventory
Running Anti-virus Scans
Running Scripts in Managed Windows or Linux Instances

Parameter Store
Provides secure and hierarchical storage for configuration data and secrets data

stores passwords, database strings, license codes
Can be stored encrypted or plain text

Inventory
Collects instance details and OS details

Applications Installed
Network Configuration
Updates installed
Monitor Windows Services and roles
Monitor Windows Registry Keys
Billing Information
Custom Inventory
Integrated with AWS Config

Patch Manager
Simplifies Operating System and application patching process and controls instance reboots

Define approval rules
Select patches to deploy ( blacklist or whitelist patches)
Specify timings to roll out patches
Report Patching Compliance

Maintenance Window
Scheduling the tasks based on the user-defined specified timings

Patching and OS
Updating Drivers
Installing Softwares
Creating AMI's

Automation
Automation is a platform to orchestrate Operational Playbooks and integrates with AWS Config and AWS Service Catalog

orchestrate dynamic playbooks
Manage AWS resources across accounts/regions
Standardize and share playbooks across the organization

Session Manager
Interactive, one-click browser-based shell eliminates to maintain the bastion hosts or SSH keys to connect to managed instances

Centralised access control
No bastion host
Port forwarding
Hybrid
Cross-Platform
Logging and auditing Session Activities

Distributor
Securely store and distribute software packages

Install-on-demand or on schedule
central repository with version control
Share with other AWS accounts
Control access package via IAM

Explorer
Provides a summary of EC2 instances and patch summary compliance state

Integrates with AWS Organization
View Operations data across accounts/regions

AWS Config

Settings
Specify the types of AWS resources you want AWS Config to record, the Amazon S3 bucket to which it sends files, and the Amazon SNS topic to which it sends notifications.

AWS Config rules

AWS Config can check the configuration of your resources against the rules that you define. Choose one or more of the following rules to get started. After setting up AWS Config, you can customize these rules, set up other rules provided by AWS Config, or create your own rules.

Summary
AWS Systems Manager provides more insight into your managed instances and using the SNS Notifications you can get notified if any failure happens during the patching process or running commands or installing software. These compliance data can be stored in S3 buckets for further analysis.

Happy Coding!

Build a Serverless Dotnet Core Web API with AWS Lambda and API Gateway

sunilkumarmedium — Tue, 01 Dec 2020 12:04:30 +0000

Introduction
In this article, we are going to deploy the ASP.NET Core Web API in AWS Lambda and AWS API Gateway.

AWS Lambda
AWS Lambda lets you run code without managing servers. you pay only for the compute time you consume.

With Lambda, you can run code for virtually any type of application or backend service - all with zero administration. Just upload your code and Lambda takes care of everything required to run and scale your code with high availability.
You can set up your code to automatically trigger from other AWS services or call it directly from any web or mobile app.

API Gateway
Amazon API Gateway is a fully managed service that makes it easy for developers to create, publish, maintain, monitor, and secure APIs at any scale. APIs act as the "front door" for applications to access data, business logic, or functionality from your backend services.

Using API Gateway, you can create RESTful APIs and WebSocket APIs that enable real-time two-way communication applications. API Gateway supports containerized and serverless workloads, as well as web applications.

AWS Architecture:
Below is the AWS services we are going to use for the deployment of Web API.

Pre-requisites
To complete this learning path, you will need:
✓ An AWS Account
✓ An IAM user with access key credentials
✓ Visual Studio Code or Visual Studio 2019+ for Windows

If you don't have an account visit https://aws.amazon.com and click Sign Up.
You must have a set of valid AWS credentials, consisting of an access key and a secret key, which are used to sign programmatic requests to AWS. You can obtain a set of account credentials when you create your account, although we recommend you do not use these credentials and instead create an IAM user and use those credentials.

Installing the AWS CLI:
Install the AWS CLI for Windows, Mac, or Linux: https://aws.amazon.com/cli/

Once installed, you can configure the CLI by running the aws configure command in a terminal or command-line window.

When prompted, enter your AWS Access Key ID and press Enter.

Enter your AWS Secret Access Key when prompted and then press Enter.

For the default region name you should enter your chosen region code (e.g. eu-west-1)

Finally, for the default output format you can just press Enter.

Installing the AWS Lambda Tools:

dotnet tool install -g Amazon.Lambda.Tools
dotnet tool install --global Amazon.Lambda.TestTool-3.1

Read the below articles for creating the postgres RDS instance and managing the connection string using Systems Manager
Creating the AWS RDS Instance for PostgreSQL
AWS Systems Manager Parameter Store and retrieving using C#

sunilkumarmedium / CleanArchitectureApp

Clean Architecture Application Design from Scratch using Dotnet Core 5 WebApi and Angular 11 FrontEnd

CleanArchitectureApp

Clean Architecture Application Design from Scratch using Dotnet Core 5 WebApi and Angular 11 FrontEnd

Technologies

ASP.NET Core 5
NHibernate
Angular 11
Angular CLI 11
Clean Architecture
Swashbuckle.AspNetCore.Swagger
Design Pattern: Command Query Responsibility Segregation (CQRS)
Fluent Validation
WebAPI Global Exception Middleware
Login, Logout and Forgot Password using JWT tokens
Microsoft Sql Server and Postgresql supported
AWS Postgres RDS
AWS Lambda
AWS Systems Manager
AWS Simple Storage Service (S3)
Docker

Pre-requisites

.Net core 5 SDK
Visual studio 2019 OR VSCode with C# extension
NodeJs (Latest LTS)
Microsoft SQL Server (Optional: If MS SQL server required instead of Sqlite during development)
POSTGRESQL

Configuration

Clone the repo: git clone https://github.com/sunilkumarmedium/CleanArchitectureApp.git
Execute the sql scripts available in the folder /sql/
- MSSQL use CleanArchitectureDB.sql
- POSTGRES use CleanArchitectureDB-Postgres
Change the database connectionstring in appsettings.json
- Path : CleanArchitectureApp.WebApi/appsettings.Development.json or appsettings.json
- "DBProvider": "MSSQL" , Use MSSQL to connect to Microsoft SqlServer Or POSTGRES to connect to PostgreSQL…

View on GitHub

Creating the AWS Lambda Web Api Project using command line

dotnet new --help will display the installed AWS project templates

To create a serverless project run the below command
dotnet new serverless.AspNetCoreWebAPI -n CleanArchitectureApp

Adding Lambda Support to existing ASP.NET Core Web API Project

Below are the steps to add AWS Lambda support for existing projects

Step 1: In csproj file add the below tag
<AWSProjectType>Lambda</AWSProjectType>

Include the below AWS package references to the projects

<PackageReference Include="AWSSDK.Extensions.NETCore.Setup" Version="3.3.101" />
<PackageReference Include="Amazon.Lambda.AspNetCoreServer" Version="5.2.0" />

Step 2: Create a c# file with name "LambdaEntryPoint.cs" and inherit the appropriate class based on your requirement. Below are some details

API Gateway REST API -> Amazon.Lambda.AspNetCoreServer.APIGatewayProxyFunction
API Gateway HTTP API payload version 1.0 -> Amazon.Lambda.AspNetCoreServer.APIGatewayProxyFunction
API Gateway HTTP API payload version 2.0 -> Amazon.Lambda.AspNetCoreServer.APIGatewayHttpApiV2ProxyFunction
Application Load Balancer -> Amazon.Lambda.AspNetCoreServer.ApplicationLoadBalancerFunction

Call the Startup.cs in the override method.

 protected override void Init(IWebHostBuilder builder)
        {
            builder
                .UseStartup<Startup>();
        }

Step 3: Create a json file "aws-lambda-tools-defaults.json" to read the default lambda configuration.

Step 4: create a serverless declarative template "serverless.template" and this will be used by the AWS Cloud Formation for creating the required resources during the Lambda deployment.

Specify the dotnet core runtime, lambda handler, memory and policies

 "Resources": {
    "AspNetCoreFunction": {
      "Type": "AWS::Serverless::Function",
      "Properties": {
        "Handler": "CleanArchitectureApp.WebApi::CleanArchitectureApp.WebApi.LambdaEntryPoint::FunctionHandlerAsync",
        "Runtime": "dotnetcore3.1",
        "CodeUri": "",
        "MemorySize": 256,
        "Timeout": 30,
        "Role": null,
        "Policies": [
          "AWSLambdaFullAccess", "AmazonSSMFullAccess","AWSLambdaVPCAccessExecutionRole"
        ],

Below is the full implementation

Deploying the WebApi to AWS Lambda

Open the command line on Windows and change the repository working directory to:
cd D:\GitHub_Projects\CleanArchitectureApp\CleanArchitectureApp.WebApi

Enter the below command and hit enter
dotnet lambda deploy-serverless --template serverless.template

Cloud Formation Stack Creation In Progress

Lambda Function Deployed

Lambda function permissions for connecting to RDS instance

API Gateway Resource Creation

Hit the API gateway endpoint
https://xxxx.execute-api.ap-south-1.amazonaws.com/Prod/swagger

Cloud Watch Logs:

Summary
You can implement the Warmer function for faster ColdStart(startup) of Lambda Function.

Happy Coding!

PostgreSQL Database Instance Creation and Configuration in AWS RDS

sunilkumarmedium — Sat, 28 Nov 2020 03:45:05 +0000

In this article, we will see the step by step instructions for configuring the Postgres DB instance in AWS RDS.

Pre-requisites
To complete this learning, you will need:
✓ An AWS Account (Free Tier)

If you don't have an account visit https://aws.amazon.com and click Sign Up.

Amazon RDS is available on several database instance types - optimized for memory, performance or I/O

Amazon Aurora
PostgreSQL
MySQL
MariaDB
Oracle
SQL Server

PostgreSQL on EC2

You can manage your own DB instance by provisioning the EC2 instance and installing the Postgres Database.

Managed PostgreSQL on RDS

Managed RDS Service can handle the patching, backup, recovery, provisioning the resources, availability.

In this article, we focus on using the managed services AWS RDS for creating PostgreSQL Database Instance

Working with Amazon RDS via the AWS Management Console Step by Step Instructions

Step 1: Log in to AWS Management Console and search with the keyword 'RDS'. You will be redirected to the RDS Home Page

Step 2: Click on the Create Database and Select Postgres

Step 3: DB Instance Settings

Step 4: DB Instance Size and Storage. For the Free tier, you will get 'db.t2.micro' instance.

Step 5: Instance Connectivity

Step 6: Additional Configuration

Step 7: Backups Configuration

Step 8: Click On Create Database you will see the resource creation progress. It will take some time for provisioning the resources

Step 9: To view Connection Details click on the View Credential Details Button

Step 10: Connect to AWS RDS Instance from your Local and execute the DB Scripts

Working with the AWS Command Line Interface
To control and automate Amazon RDS resources from the command line, use the AWS Command Line Interface (CLI)

Summary
You can see the detailed implementation and connecting the API to the RDS instance in below github project

sunilkumarmedium / CleanArchitectureApp

Clean Architecture Application Design from Scratch using Dotnet Core 3.1 WebApi and Angular 11 FrontEnd

CleanArchitectureApp

Clean Architecture Application Design from Scratch using Dotnet Core 3.1 WebApi and Angular 11 FrontEnd

Technologies

ASP.NET Core 3.1
NHibernate
Angular 11
Angular CLI 11
Clean Architecture
Swashbuckle.AspNetCore.Swagger
Design Pattern: Command Query Responsibility Segregation (CQRS)
Fluent Validation
WebAPI Global Exception Middleware
Login, Logout and Forgot Password using JWT tokens
Microsoft Sql Server and Postgresql supported.

Pre-requisites

.Net core 3.1 SDK
Visual studio 2019 OR VSCode with C# extension
NodeJs (Latest LTS)
Microsoft SQL Server (Optional: If MS SQL server required instead of Sqlite during development)
POSTGRESQL

Configuration

Clone the repo: git clone https://github.com/sunilkumarmedium/CleanArchitectureApp.git
Execute the sql scripts available in the folder /sql/
- MSSQL use CleanArchitectureDB.sql
- POSTGRES use CleanArchitectureDB-Postgres
Change the database connectionstring in appsettings.json
- Path : CleanArchitectureApp.WebApi/appsettings.Development.json or appsettings.json
- "DBProvider": "MSSQL" , Use MSSQL to connect to Microsoft SqlServer Or POSTGRES to connect to PostgreSQL database
- "ConnectionStrings": { "MSSQLConnection": "Data Source=DESKTOP-SUNILBO;Initial Catalog=CleanArchitectureDB;User ID=sa;Password=xxx;MultipleActiveResultSets=True", "PostgresConnection": "Server=127.0.0.1;Port=5432;Database=CleanArchitectureDB;User Id=postgres;Password=xxx;Timeout=30;TimeZone=UTC" }'
cd to…

View on GitHub

AWS Systems Manager Parameter Store for Managing Configuration and Retrieve at Runtime using C#

sunilkumarmedium — Sat, 28 Nov 2020 01:51:15 +0000

Introduction

One common challenge in application development is ensuring that any configuration data liable to change across deployments is separated from the code, allowing a single release to be configured for multiple environments.

AWS's solution for storing configuration data is called AWS Systems Manager Parameter Store.

Parameter Store provides a mechanism to store and manage configuration data, encrypted or plain text, using a hierarchical structure.

Parameter Store is ideal for storing passwords, database strings, and all other types of general configuration values.

Pre-requisites
To complete this learning, you will need:
✓ An AWS Account
✓ An IAM user with access key credentials
✓ Visual Studio Code or Visual Studio 2019+ for Windows

If you don't have an account visit AWS and click Sign Up.

You must have a set of valid AWS credentials, consisting of an access key and a secret key, which are used to sign programmatic requests to AWS. You can obtain a set of account credentials when you create your account, although we recommend you do not use these credentials and instead create an IAM user and use those credentials.

Installing the AWS CLI:

Install the AWS CLI for Windows, Mac, or Linux: https://aws.amazon.com/cli/

Once installed, you can configure the CLI by running the aws configure command in a terminal or command-line window.

When prompted, enter your AWS Access Key ID and press Enter.

Enter your AWS Secret Access Key when prompted and then press Enter.

For the default region name you should enter your chosen region code (e.g. ap-south-1)

Finally, for the default output format you can just press Enter.

Creating Parameter Store data using AWS CLI

To create an entry in the Parameter Store, execute the following command in the terminal or command-line window:

aws ssm put-parameter --name "/CleanArchitectureAppWebApi/postgresconnection" --type String --value "ConnectionString"

Adding Secure String

aws ssm put-parameter --name "secure-parameter-name" --type "SecureString" --value "secure-parameter-value"

The above command will create the parameter in the region you specified as your default profile configured.
To create a parameter in a different region, add the --region parameter, for example --region ap-south-1.

We can retrieve the parameter created by running the following command in the terminal or command-line window:

aws ssm get-parameter --name "/CleanArchitectureAppWebApi/postgresconnection"

To delete data from Parameter Store execute the following command in a terminal or command-line window:

aws ssm delete-parameter --name "/CleanArchitectureAppWebApi/postgresconnection"

Creating Parameter Store data using AWS Console

Log-in to the AWS Management Console
search for 'Systems Manager' and Click on Create Parameter

Retrieving the parameter using C#

Now that you have created a configuration value, it's time to create a basic .NET C# application that can retrieve the data at runtime.

Create C# console or Web application
Reference the AWS SDK SimpleSystemsManager Package using nuget package console <PackageReference Include="AWSSDK.SimpleSystemsManagement" Version="3.5.5.6" />
Add the below Assembly references using Amazon.SimpleSystemsManagement; using Amazon.SimpleSystemsManagement.Model;

var request = new GetParameterRequest()
{
     Name = "/CleanArchitectureAppWebApi/postgresconnection"
                    };

                    using (var client = new AmazonSimpleSystemsManagementClient(Amazon.RegionEndpoint.GetBySystemName("ap-south-1")))
                    {
                        var response =  client.GetParameterAsync(request).GetAwaiter().GetResult();
                        connectionString = response.Parameter.Value;
                    }

The Name and the Region can be read from the appsettings.json configuration.

You can see the implementation in the below Github project

sunilkumarmedium / CleanArchitectureApp

Clean Architecture Application Design from Scratch using Dotnet Core 5 WebApi and Angular 11 FrontEnd

CleanArchitectureApp

Clean Architecture Application Design from Scratch using Dotnet Core 5 WebApi and Angular 11 FrontEnd

Technologies

ASP.NET Core 5
NHibernate
Angular 11
Angular CLI 11
Clean Architecture
Swashbuckle.AspNetCore.Swagger
Design Pattern: Command Query Responsibility Segregation (CQRS)
Fluent Validation
WebAPI Global Exception Middleware
Login, Logout and Forgot Password using JWT tokens
Microsoft Sql Server and Postgresql supported
AWS Postgres RDS
AWS Lambda
AWS Systems Manager
AWS Simple Storage Service (S3)
Docker

Pre-requisites

.Net core 5 SDK
Visual studio 2019 OR VSCode with C# extension
NodeJs (Latest LTS)
Microsoft SQL Server (Optional: If MS SQL server required instead of Sqlite during development)
POSTGRESQL

Configuration

Clone the repo: git clone https://github.com/sunilkumarmedium/CleanArchitectureApp.git
Execute the sql scripts available in the folder /sql/
- MSSQL use CleanArchitectureDB.sql
- POSTGRES use CleanArchitectureDB-Postgres
Change the database connectionstring in appsettings.json
- Path : CleanArchitectureApp.WebApi/appsettings.Development.json or appsettings.json
- "DBProvider": "MSSQL" , Use MSSQL to connect to Microsoft SqlServer Or POSTGRES to connect to PostgreSQL…

View on GitHub

Happy Coding!

Building Single Page Application Using Angular 11 — FrontEnd

sunilkumarmedium — Mon, 23 Nov 2020 07:23:57 +0000

In this post, we will focus on building the Angular frontend integrating with WebApi

Overview

Building Angular Single Page Application integrating with backend ASP.NET WebAPI.

Setting up Angular 11 for Local Development

To install angular the following pre-requisites installations is required

NodeJs active LTS
NPM package Manager Installing the Angular CLI > The Angular CLI is a command-line interface tool that you use to initialize, develop, scaffold, and maintain Angular applications.

npm install -g @angular/cli

Verify the version of angular using the below command
ng — version
Angular Version installed in my local development environment

Creating an Angular App

Run the CLI command ng and provide the name of the app as shown below
ng new myapp

Run the App

To run the application navigate to the app folder created and run the below command
cd myapp npm install ng serve — open

The ng serve command launches the server watches your files and rebuilds the app as you make changes to those files.

In this application, we are going to use the ng bootstrap CSS. To install run the below command in the terminal

npm install — save @ng-bootstrap/ng-bootstrap

Angular App Structure

Using visual studio code editor for building the application. Below is the application structure

Project code is available on Github

sunilkumarmedium / CleanArchitectureApp

Clean Architecture Application Design from Scratch using Dotnet Core 3.1 WebApi and Angular 11 FrontEnd

CleanArchitectureApp

Clean Architecture Application Design from Scratch using Dotnet Core 3.1 WebApi and Angular 11 FrontEnd

Technologies

ASP.NET Core 3.1
NHibernate
Angular 11
Angular CLI 11
Clean Architecture
Swashbuckle.AspNetCore.Swagger
Design Pattern: Command Query Responsibility Segregation (CQRS)
Fluent Validation
WebAPI Global Exception Middleware
Login, Logout and Forgot Password using JWT tokens
Microsoft Sql Server and Postgresql supported.

Pre-requisites

.Net core 3.1 SDK
Visual studio 2019 OR VSCode with C# extension
NodeJs (Latest LTS)
Microsoft SQL Server (Optional: If MS SQL server required instead of Sqlite during development)
POSTGRESQL

Configuration

Clone the repo: git clone https://github.com/sunilkumarmedium/CleanArchitectureApp.git
Execute the sql scripts available in the folder /sql/
- MSSQL use CleanArchitectureDB.sql
- POSTGRES use CleanArchitectureDB-Postgres
Change the database connectionstring in appsettings.json
- Path : CleanArchitectureApp.WebApi/appsettings.Development.json or appsettings.json
- "DBProvider": "MSSQL" , Use MSSQL to connect to Microsoft SqlServer Or POSTGRES to connect to PostgreSQL database
- "ConnectionStrings": { "MSSQLConnection": "Data Source=DESKTOP-SUNILBO;Initial Catalog=CleanArchitectureDB;User ID=sa;Password=xxx;MultipleActiveResultSets=True", "PostgresConnection": "Server=127.0.0.1;Port=5432;Database=CleanArchitectureDB;User Id=postgres;Password=xxx;Timeout=30;TimeZone=UTC" }'
cd to…

View on GitHub

Creating project folders
Inside the “app” folder, let’s create the folders “_models”, “_components”, “_shared” “_services”.
In the “_models” folder we will place our entities, like User:

Creating Components

Components are the main building block for Angular applications. Each component consists of:

An HTML template that declares what renders on the page
A Typescript class that defines the behavior
A CSS selector that defines how the component is used in a template Optionally, CSS styles applied to the template

Sample Login Component

Services
Services can be used to have business logic in one place and can be injected into components when required.

Dependency Injection in Angular

Dependency injection (DI), is an important application design pattern. Angular has its own DI framework, which is typically used in the design of Angular applications to increase their efficiency and modularity.

To create a service, run the below command in the terminal window
ng generate service _services/authentication

Below is the sample Service

Interceptors

Intercepting requests and responses, With interception, you declare interceptors that inspect and transform HTTP requests from your application to a server. The same interceptors can also inspect and transform a server’s responses on their way back to the application. Multiple interceptors form a forward-and-backward chain of request/response handlers.

In our application, We have created JwtInteceptor to add the JWT token to every request that hits to web API. Below is the code implementation.

Global Error Handler

Handling exceptions in common service that implements ErrorHandler.

AuthGuard

AuthGuard can be used to restrict the user from viewing unauthorized pages or Components. Below is the AuthGuard Implementation.

Running the Application in Visual Studio Code
Open the project folder in the visual studio code and click on the run tab and select the projects to run as shown in the below screenshot

Angular Application and WebAPI are running in URL's below

WebAPI: http://localhost:5001
AngularWeb: http://localhost:5003 Test User to Login
Username: system
Password: admin@123

Conclusion
Hope you enjoyed the post and please feel free to play around with code

Happy Coding!

Series Links
Building an ASP.NET Core WebAPI using Clean Architecture

Building Clean Architecture Application using ASP.NET Core Web API and Angular 11 — Backend | by Sunil Kumar | Nov, 2020 | Medium

Sunil Kumar ・ Nov 22, 2020 ・ 3 min read
sunil-kumar-60226.Medium

Building an Angular 11 Application integrated with WebAPI

Building Single Page Application Using Angular 11 — FrontEnd | by Sunil Kumar | Nov, 2020 | Medium

Sunil Kumar ・ Nov 22, 2020 ・ 4 min read
sunil-kumar-60226.Medium

Building Clean Architecture Application using ASP.NET Core Web API and Angular 11 — Backend

sunilkumarmedium — Mon, 23 Nov 2020 06:40:37 +0000

In this article, we are going to learn building a Clean Architecture application using ASP.NET Core Web API and Angular 11 Front End.

Overview
Building an ASP.NET Core WebAPI using Clean Architecture
Features:

ASP.NET Core 3.1 Web API.
API Versioning
Swagger UI.
JWT Token Authentication
Global Error Handler Middleware
CQRS ( Command Query Responsibility Segregation)
MediatR
NHibernate ORM
Generic Repository Pattern
Fluent Validation
SQLSERVER

Github Project
You can refer to the below GitHub project for complete implementation.

sunilkumarmedium / CleanArchitectureApp

Clean Architecture Application Design from Scratch using Dotnet Core 3.1 WebApi and Angular 11 FrontEnd

CleanArchitectureApp

Clean Architecture Application Design from Scratch using Dotnet Core 3.1 WebApi and Angular 11 FrontEnd

Technologies

ASP.NET Core 3.1
NHibernate
Angular 11
Angular CLI 11
Clean Architecture
Swashbuckle.AspNetCore.Swagger
Design Pattern: Command Query Responsibility Segregation (CQRS)
Fluent Validation
WebAPI Global Exception Middleware
Login, Logout and Forgot Password using JWT tokens
Microsoft Sql Server and Postgresql supported.

Pre-requisites

.Net core 3.1 SDK
Visual studio 2019 OR VSCode with C# extension
NodeJs (Latest LTS)
Microsoft SQL Server (Optional: If MS SQL server required instead of Sqlite during development)
POSTGRESQL

Configuration

Clone the repo: git clone https://github.com/sunilkumarmedium/CleanArchitectureApp.git
Execute the sql scripts available in the folder /sql/
- MSSQL use CleanArchitectureDB.sql
- POSTGRES use CleanArchitectureDB-Postgres
Change the database connectionstring in appsettings.json
- Path : CleanArchitectureApp.WebApi/appsettings.Development.json or appsettings.json
- "DBProvider": "MSSQL" , Use MSSQL to connect to Microsoft SqlServer Or POSTGRES to connect to PostgreSQL database
- "ConnectionStrings": { "MSSQLConnection": "Data Source=DESKTOP-SUNILBO;Initial Catalog=CleanArchitectureDB;User ID=sa;Password=xxx;MultipleActiveResultSets=True", "PostgresConnection": "Server=127.0.0.1;Port=5432;Database=CleanArchitectureDB;User Id=postgres;Password=xxx;Timeout=30;TimeZone=UTC" }'
cd to…

View on GitHub

Onion Architecture

Clean Architecture
The architecture defines where the application performs its core functionality and how that functionality interacts with things like the database and the user interface. Clean architecture refers to organizing the project so that it’s easy to understand and easy to change as the project grows.

Command Query Responsibility Segregation is a design pattern to separate the read and write processes of your application. Read operations are called Queries and write operations are called Commands.

Project Structure

Swagger UI Setup
The swagger object model and middleware exposes the JSON objects as Endpoints

Installing Swagger packages using NuGet package console with the below command.

Install-Package Swashbuckle.AspNetCore -Version 5.6.3

Swagger Configuration with Bearer token Authentication

JWT Token Implementation

The JWT Bearer Token is used for accessing the WebApi endpoints securely. Below is the JWT configuration

Token Generation On Successful Login

Global Error Middleware

Server Internal Error Exceptions and Business Validation Exceptions are handled and the response is returned for use of displaying these validations in UI.

NHibernate ORM and Generic Repository Pattern

NHibernate is used to interact with the database. Singleton Session factory is implemented. Below is the Persistence Layer Service Extension.

User Entity

UserMap

Fluent Validation
Package Reference:

<PackageReference Include=”FluentValidation.DependencyInjectionExtensions” Version=”9.3.0" />

To define a set of validation rules for a particular object, you will need to create a class that inherits from AbstractValidator, where T is the type of class that you wish to validate.

Below is the sample Create User Validations.

Summary
Hope enjoyed my first article please feel free to download the code and play around. Next article we will get in touch with Angular 11.

Series Links
Building an ASP.NET Core WebAPI using Clean Architecture

Building Clean Architecture Application using ASP.NET Core Web API and Angular 11 — Backend | by Sunil Kumar | Nov, 2020 | Medium

Sunil Kumar ・ Nov 22, 2020 ・ 3 min read
sunil-kumar-60226.Medium

Building an Angular 11 Application integrated with WebAPI

DEV Community: sunilkumarmedium

AWS Systems Manager Hands-On

Build a Serverless Dotnet Core Web API with AWS Lambda and API Gateway

sunilkumarmedium / CleanArchitectureApp

Clean Architecture Application Design from Scratch using Dotnet Core 5 WebApi and Angular 11 FrontEnd

CleanArchitectureApp

Technologies

Pre-requisites

Configuration

PostgreSQL Database Instance Creation and Configuration in AWS RDS

sunilkumarmedium / CleanArchitectureApp

Clean Architecture Application Design from Scratch using Dotnet Core 3.1 WebApi and Angular 11 FrontEnd

CleanArchitectureApp

Technologies

Pre-requisites

Configuration

AWS Systems Manager Parameter Store for Managing Configuration and Retrieve at Runtime using C#

sunilkumarmedium / CleanArchitectureApp

Clean Architecture Application Design from Scratch using Dotnet Core 5 WebApi and Angular 11 FrontEnd

CleanArchitectureApp

Technologies

Pre-requisites

Configuration

Building Single Page Application Using Angular 11 — FrontEnd

sunilkumarmedium / CleanArchitectureApp

Clean Architecture Application Design from Scratch using Dotnet Core 3.1 WebApi and Angular 11 FrontEnd

CleanArchitectureApp

Technologies

Pre-requisites

Configuration

Building Clean Architecture Application using ASP.NET Core Web API and Angular 11 — Backend | by Sunil Kumar | Nov, 2020 | Medium

Sunil Kumar ・ Nov 22, 2020 ・ 3 min read sunil-kumar-60226.Medium

Building Single Page Application Using Angular 11 — FrontEnd | by Sunil Kumar | Nov, 2020 | Medium

Sunil Kumar ・ Nov 22, 2020 ・ 4 min read sunil-kumar-60226.Medium

Building Clean Architecture Application using ASP.NET Core Web API and Angular 11 — Backend

sunilkumarmedium / CleanArchitectureApp

Clean Architecture Application Design from Scratch using Dotnet Core 3.1 WebApi and Angular 11 FrontEnd

CleanArchitectureApp

Technologies

Pre-requisites

Configuration

Building Clean Architecture Application using ASP.NET Core Web API and Angular 11 — Backend | by Sunil Kumar | Nov, 2020 | Medium

Sunil Kumar ・ Nov 22, 2020 ・ 3 min read sunil-kumar-60226.Medium

Building Single Page Application Using Angular 11 — FrontEnd | by Sunil Kumar | Nov, 2020 | Medium

Sunil Kumar ・ Nov 22, 2020 ・ 4 min read sunil-kumar-60226.Medium

Sunil Kumar ・ Nov 22, 2020 ・ 3 min read
sunil-kumar-60226.Medium

Sunil Kumar ・ Nov 22, 2020 ・ 4 min read
sunil-kumar-60226.Medium

Sunil Kumar ・ Nov 22, 2020 ・ 3 min read
sunil-kumar-60226.Medium

Sunil Kumar ・ Nov 22, 2020 ・ 4 min read
sunil-kumar-60226.Medium