Source: aws.amazon.com
Automated CI/CD pipeline for .NET Core Lambda functions using AWS extensionCategory: Business, github, yaml
The trend of building AWS Serverless applications using AWS Lambda is increasing at an ever-rapid pace. Common use cases for AWS Lambda include data processing, real-time file processing, and extract, transform, and load (ETL) for data processing, web backends, internet of things (IoT) backends, and mobile backends.
CodeCommit stores the source code for .NET Core Lambda functions and triggers CodeBuild when a new code change is published.
You have multiple options for creating .NET Core Lambda function projects, such as using Visual Studio 2019, Visual Studio Code, and .NET Core CLI.
If you no longer need the following resources, delete them to avoid incurring further charges: In this post, you implemented an automated CI/CD for .NET Core Lambda functions using two stages of CodePipeline: CodeCommit and CodeBuild.
CodeCommit stores the source code for .NET Core Lambda functions and triggers CodeBuild when a new code change is published.
You have multiple options for creating .NET Core Lambda function projects, such as using Visual Studio 2019, Visual Studio Code, and .NET Core CLI.
If you no longer need the following resources, delete them to avoid incurring further charges: In this post, you implemented an automated CI/CD for .NET Core Lambda functions using two stages of CodePipeline: CodeCommit and CodeBuild.
Related Articles
Community Partners
DevOps Careers