https://github.com/antoniofalcaojr/dotnet.awslambda.autoscaling
This project demonstrates the integration with AWS Auto Scaling service and .NET Core, using SAM for building and test.
https://github.com/antoniofalcaojr/dotnet.awslambda.autoscaling
autoscaling aws aws-autoscaling aws-cli aws-lambda dotnet dotnet-cli dotnet-core
Last synced: 7 months ago
JSON representation
This project demonstrates the integration with AWS Auto Scaling service and .NET Core, using SAM for building and test.
- Host: GitHub
- URL: https://github.com/antoniofalcaojr/dotnet.awslambda.autoscaling
- Owner: AntonioFalcaoJr
- Created: 2020-07-17T22:49:50.000Z (about 5 years ago)
- Default Branch: master
- Last Pushed: 2023-03-06T08:57:37.000Z (over 2 years ago)
- Last Synced: 2024-10-12T13:24:22.423Z (12 months ago)
- Topics: autoscaling, aws, aws-autoscaling, aws-cli, aws-lambda, dotnet, dotnet-cli, dotnet-core
- Language: C#
- Homepage: https://dev.to/antoniofalcao/using-net-core-in-aws-lambda-with-sam-and-building-an-auto-scaling-manager-3gjc
- Size: 224 KB
- Stars: 10
- Watchers: 1
- Forks: 1
- Open Issues: 6
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# .NET Core 3.x AWS Lambda with SAM
Auto Scaling Manager
This project demonstrates the integration with **AWS Auto-Scaling** service and **.NET Core**, using **SAM** for building and test.
This sample contains source code and supporting files for a **serverless application** that you can deploy with the **SAM CLI**.
- [`./src`](./src) - Multilayer .NET Core project for the application's Lambda function.
- [`./.events`](./.events) - Invocation events that you can use to invoke the function.
- [`./test`](./test) - Unit tests for the application code with XUnit.
- [`template.yaml`](./template.yaml) - A template that defines the application's AWS resources.
## How its works
Using a JSON as input is possible to **suspend** or **resume** processes from a specific auto-scaling by _tag name_.
> **Use case:** SUSPEND the _Terminate_ and _Launch_ processes as the initial stage from **Blue-Green Deploy** on **Code Pipeline** and then, RESUME in the final stage.
JSON sample for use at AWS or in this project.
```json5
{
"Scalings": [
{
"Tag": "tag-name-here",
"Suspend": false
}
]
}
```
Many scalings:
```json5
{
"Scalings": [
{
"Tag": "tag-name-here",
"Suspend": false
},
{
"Tag": "tag-name-here",
"Suspend": true
}
]
}
```
About **Processes**, is possible to specify, but if not it will use the default list.
```json5
{
"Scalings": [
{
"Tag": "tag-name-here",
"Suspend": false,
"Processes": [
"Terminate",
"Launch"
]
}
]
}
```
Default values are defined on file [`ProcessService.cs`](./src/Dotnet.AWSLambda.AutoScaling.Services/Processes/ProcessService.cs):
```c#
public class ProcessService : IProcessService
{
private static ProcessType LaunchProcessType => new ProcessType {ProcessName = "Launch"};
private static ProcessType ScheduledActionsProcessType => new ProcessType {ProcessName = "ScheduledActions"};
private static ProcessType TerminateProcessType => new ProcessType {ProcessName = "Terminate"};
// comment for brevity
}
```
## Function Project
This project consists of:
* [`Dotnet.AWSLambda.AutoScaling.Application.Function.cs`](./src/Dotnet.AWSLambda.AutoScaling.Application/Function.cs) - class file containing a class with a single function handler method;
* [`aws-lambda-tools-defaults.json`](./aws-lambda-tools-defaults.json) - default argument settings for use with **Rider** or **Visual Studio** and command line deployment tools for AWS.
## Amazon.Lambda.Tools:
Install Amazon.Lambda.Tools Global Tools if not already installed.
```bash
dotnet tool install -g Amazon.Lambda.Tools
```
If already installed check if a new version is available.
```bash
dotnet tool update -g Amazon.Lambda.Tools
```
## About SAM
The **Serverless Application Model Command Line Interface** (SAM CLI) is an extension of the AWS CLI that adds functionality for building and testing Lambda applications. It uses **Docker** to run your functions in an Amazon Linux environment that matches Lambda. It can also emulate your application's build environment and API.
To use the SAM CLI, you need the following tools.
* SAM CLI - [Install the SAM CLI](https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/serverless-sam-cli-install.html)
* .NET Core - [Install .NET Core](https://www.microsoft.com/net/download)
* Docker - [Install Docker community edition](https://hub.docker.com/search/?type=edition&offering=community)
## Use the SAM CLI to build and test locally
Build application with the `sam build` command.
```bash
sam build
```
The SAM CLI installs dependencies defined in `./src/Dotnet.AWSLambda.AutoScaling.Application/Dotnet.AWSLambda.AutoScaling.Application.csproj`, creates a deployment package, and saves it in the `.aws-sam/build` folder.
#### Events
Test a single function by invoking it directly with a test **event**. An event is a JSON document that represents the input that the function receives from the event source. Test events are included in the [`./.events`](./.events) folder in this project.
> [`json-event.json`](./.events/json-event.json) represents a simple json input.
> [`request-event.json`](./.events/request-event.json) represents a request json input.
Run functions locally and invoke them with the `sam local invoke` command.
```bash
sam local invoke -e json-event.json
```
OR
```bash
sam local invoke -e request-event.json
```
#### API Request
The **SAM CLI** can also emulate the application's as API. Use the `sam local start-api` to run the API locally on port 3000.
```bash
sam local start-api
```
Then, is possible to request using **cURL** or **REST Client**:
> cURL
```bash
curl --header "Content-Type: application/json" -X POST -d "{ 'Scalings': [ { 'Tag': 'your-tag-name-here', 'Suspend': false }, { 'Tag': 'your-tag-name-h', 'Suspend': true } ] }" http://127.0.0.1:3000/api
```
> REST Client
```http request
POST http://127.0.0.1:3000/api/
content-type: application/json
{
"Scalings": [
{
"Tag": "tag-name-here",
"Suspend": false
},
{
"Tag": "tag-name-here",
"Suspend": true
}
]
}
```
#### API settings
The **SAM CLI** reads the application template to determine the API's routes and the functions that they invoke.
```yaml
Events:
AutoScalingManager:
Type: Api
Properties:
Path: '/api'
Method: post
```
## Credentials
You can set credentials in the AWS credentials file on your local system. This file must be located in one of the following locations:
* `~/.aws/credentials` on Linux or macOS
* `C:\Users\USERNAME\.aws\credentials` on Windows
This file should contain lines in the following format:
```bash
[default]
aws_access_key_id = your_access_key_id
aws_secret_access_key = your_secret_access_key
```
* Environment variables – You can set the `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` environment variables.
To set these variables on Linux or macOS, use the export command:
```bash
export AWS_ACCESS_KEY_ID=your_access_key_id
export AWS_SECRET_ACCESS_KEY=your_secret_access_key
```
To set these variables on Windows, use the set command:
```bash
set AWS_ACCESS_KEY_ID=your_access_key_id
set AWS_SECRET_ACCESS_KEY=your_secret_access_key
```
If you are testing this lambda project with **SAM**, is necessary to inform the credentials on [`template.yaml`](./template.yaml):
```yaml
Environment:
Variables:
AWS_ACCESS_KEY_ID: VALUE
AWS_SECRET_ACCESS_KEY: VALUE
AWS_DEFAULT_REGION: VALUE
```
### Unit tests
Tests are defined in the `test` folder in this project.
```bash
dotnet test
```