awslabs/aws-blog-net-exploring-aspnet-core

This repository is for exploring the new ASP.NET Core platform with AWS. On the AWS .NET blog site there are a series of posts talking about the code in this repository. For any questions or ideas about ASP.NET Core on AWS feel free to open a GitHub issue. That will help us in determining future blog content.

Exploring ASP.NET Core on AWS

This repository goes along with a series of blogs discussing how to deploy ASP.NET Core applications to AWS. Each will have its code in its own branch. with master including the the latest post's code.

If you wish to discuss topics about ASP.NET Core on AWS feel free to open up an issue.

Posts in the series

• Exploring ASP.NET Core Part 2: Continuous Delivery
  • Build a continuous delivery system for ASP.NET Core using CodeDeploy and CodePipelines.
• Exploring ASP.NET Core Part 1: Deploying from GitHub
  • Discuss how you can take advantage of ASP.NET Core's ability to run from source and deploy straight from GitHub.

aws-blog-net-exploring-aspnet-core's Issues

Working with EF and RDS

Almost every app has data and RDS could be a good alternative.
With new AspNet it's coming new Entity Framework as well.
Making a sample that shows how to work with Entity Framework core and RDS (at least MSSQL & MySQL) in an AspNet core app would be very helpful for developers.

Multi project solution - deploy in docker containers

Was a bit confuse how to build docker image in a VS solution with several projects, like a web project with two class library projects (like data access, business logic, or external api callings).
So building a sample like this and deploying in docker containers (EC2 CS) would be helpful for several scenarios.

Working with SQS

While AspNet Core is opening big horizon of several application types, not just web apps / sites, but console apps as well.
A "worker" style or listener app for Simple Queue Service queues would be an ideal sample while there are several architectural cases using messaging and AWS together.
Having an opinion from AWS .Net team would be very good jumpstart for developers.