- Newest
- Most votes
- Most comments
So for starters, you don't need to use the AWS Toolkit to create or deploy the AWS Serverless Application for .NET. You can also do this from the command line. To get the project templates for the command line, install the Amazon.Lambda.Templates tool using:
dotnet new -i Amazon.Lambda.Templates
After that, you can create a new serverless ASP.NET Core Web API with:
dotnet new serverless.AspNetCoreWebAPI
or
dotnet new serverless.AspNetCoreMinimalAPI
You can deploy these serverless applications to Lambda the Amazon.Lambda.Tools global tool.
You can install that tool using this command:
dotnet tool install -g Amazon.Lambda.Tools
After that, you can deploy your serverless application to Lambda using:
dotnet lambda deploy-serverless
To answer your other question, about environments: the AWS Toolkit is meant for deploying to test or dev environments, and not for production deployments. If you want to deploy to a different AWS account, choose a different profile. In your screenshot, you are using your "default" profile. You can create multiple profiles that have credentials for multiple AWS accounts, or even for the same account but associated with different IAM users. To deploy to another account, just re-deploy the Lambda, selecting a profile that is associated with another AWS account.
See the AWS docs for the .NET Core CLI for more details.
Relevant content
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago