ecs-deploy
aws-extensions-for-dotnet-cli
Our great sponsors
ecs-deploy | aws-extensions-for-dotnet-cli | |
---|---|---|
1 | 7 | |
1,957 | 365 | |
0.4% | 2.2% | |
7.3 | 7.3 | |
about 1 month ago | 23 days ago | |
Shell | C# | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ecs-deploy
aws-extensions-for-dotnet-cli
-
Deploy Lambda only when there are code changes
The problem is this issue. lambda package command does not stripe timestamps from the archive, therefore this archive has a different hash each time.
- Deploying to Elastic Beanstalk from Mac M1
- how to add tags to AWS Lambda in code
-
How to add tags to AWS Lambda in dotnet application
Here’s the deploy-serverless source code which shows tags as a CommandOption. This other class appears to show available command options. I haven’t tested using the tags option since I’m posting from my phone but it looks like there is a way. Hope that helps.
-
Anyone running ASP.Net Core on AWS Lambda? Or dotnet on AWS Lambda in general?
What's your thoughts on AWS Lambda for microservices? Long story short, I'm debating converting an app I originally built in asp.net core to AWS Lambda to save money. It's currently running in a container on ECS Fargate. AWS offers a dotnet cli extension that allows me to pretty much bootstrap my api to run on Lambda while keeping the asp.net core framework: https://github.com/aws/aws-extensions-for-dotnet-cli. Honestly, the only reason I'm considering doing this is cost ... as this is a side project that I someday plan to make public. I started rewriting the api in pure NodeJS with Typescript to run on AWS Lambda and I really miss the built in functionality I get with asp.net core framework and beauty of dotnet.
-
.NET for AWS Lambda?
Some are deployed using Terraform, some using Serverless framework (which uses CloudFormation under the hood), and some using AWS Extensions for .NET CLI.
What are some alternatives?
spinnaker - Spinnaker is an open source, multi-cloud continuous delivery platform for releasing software changes with high velocity and confidence.
aws-dotnet-examples - A collection of independent .NET5 projects written in C# that demonstrate how to integrate with various AWS services using the AWS SDK for .NET
phoenix_container_example - Production-quality example for Elixir/Phoenix building, testing, and running in containers
CommandQuery - Command Query Separation for 🌐ASP.NET Core ⚡AWS Lambda ⚡Azure Functions ⚡Google Cloud Functions
aws-workflows-on-github - Workflows for automation of AWS services setup from Github CI/CD
copilot-cli - The AWS Copilot CLI is a tool for developers to build, release and operate production ready containerized applications on AWS App Runner or Amazon ECS on AWS Fargate.
containers-roadmap - This is the public roadmap for AWS container services (ECS, ECR, Fargate, and EKS).
paths-filter - Conditionally run actions based on files modified by PR, feature branch or pushed commits
ecs-refarch-continuous-deployment - ECS Reference Architecture for creating a flexible and scalable deployment pipeline to Amazon ECS using AWS CodePipeline
dotnet-nativeaot-labs - A place to learn about and experiment with .NET NativeAOT on AWS.