AWS Infrastructure Setup For a .Net6 Project ( Containerised Microservices Project ) -- 2

Objective: Set up AWS infrastructure for the "OneStop" project (Technologies involved Angular 13 & .Net6 technologies, Project includes 2 separate GitHub repositories).

Note: We tried to list out key points. This list is likely to have many missing elements, Need your help in identifying missing elements. Open to discuss better options compared to the listed items below

Requirements:

->AWS Architect the infrastructure

->Create the infrastructure using CloudFormation(YAML) scripting to provision AWS Infrastructure, Split into multiple files based on services for a easy readability

->Add friendly (Non-Technical) comments to the individual set of script. (Ex: Script related to ECS, Script related to ECR, Script related to Fargate....etc)

->Setting Up Jenkins / Octopus / AWS Code Pipeline (CI/CD) / GitHub Actions / Terraform cloud hub such a way that manually someone would push a particular build version to a particular environment(Dev/QA/Stg/Prod)

->Set up image creation for the code checked-in to the GitHub (Ex: Docker Image)

->Docker Hub / ECR connectivity

->Setup AWS ECS and Fargate set up for .net containerized applications such a way that auto scaling takes place based on the load/traffic to the website

->Setup AWS RDS across all environments (Dev, QA, Stg, Prod). Save daily back copy appropriately (Ex: S3). <Let's discuss this in details....>

->Fully secure all the AWS features, services to an industry standard(Ex: Policies, VPCs, Subnets, IAM policies, Load balancing, NAT Gateway,Internet Gateway,Subnets, Security Groups, Route Tables, Route 53 and CIDR Ranges.....etc)

->Secure the infrastructure from vulnerable attacks & hacking

->Setup Environment variables, secure key and value pairs that will be referred in the application (Ex: In CI/CD engine level, AWS Secrets manager)

->Configure S3, EBS for all backup to be saved & for anything else that need to be saved

->Logs would be in CloudWatch

->AWS-SES

"At the end,

In Production environment -> Url would be in [login to view URL](We will supply the actual) format

In Staging environment -> Url would be in [login to view URL](We will supply the actual) format

In QA environment -> Url would be in [login to view URL](We will supply the actual) format

In Dev environment -> Url would be in [login to view URL](We will supply the actual) format "

.NET Przetwarzanie w chmurze Amazon Web Services

Numer ID Projektu: #33253251

O projekcie