AWS Developer Tools Blog

AWS .NET Team at AWS re:Invent 2017

Steve and I, from the AWS .NET Team, just got back from AWS re:Invent, where we met up with a lot of .NET developers doing some really cool projects on AWS. We also presented two sessions, which are online now. If you weren’t able come to re:Invent and see us, check out the videos online.

Developing applications on AWS with .NET Core

https://www.youtube.com/watch?v=IfF1E2RJ6Do

In this session, we talked about how to add AWS services to your .NET Core applications, and then covered how to deploy your applications.

We announced new Visual Studio tooling to deploy .NET Core applications as a container to Amazon Elastic Container Service (ECS). The new tooling also supports the new ECS Fargate support. Fargate enables you to run container applications in a fully managed environment, removing the responsibility for managing any Amazon EC2 instances. Expect more information and examples on how to use this new tooling soon.

We also preannounced that support for .NET Core 2.0 in AWS Lambda is coming soon. We showed a demo of the upcoming runtime executing a full ASP.NET Core application with ASP.NET Razor pages. We made the demo extra exciting by also showing off upcoming .NET Core 2.0 support for AWS X-Ray.

Extending VSTS build or release pipelines to AWS

https://www.youtube.com/watch?v=8fXDOlFWmZU

This session covered our new AWS Tools for Microsoft Visual Studio Team Services (VSTS) that we launched this summer. Steve and I drilled deep into how you can use this tool to make using AWS from VSTS and TFS simple. We covered deploying to both AWS Elastic Beanstalk and AWS CodeDeploy, in addition to using AWS CloudFormation to define our infrastructure for our AWS CodeDeploy deployments.

Right before our session, we released a new version of the tool with four new tasks:

  • Amazon Elastic Container Registry (ECR) – Pushes your Docker images to Amazon’s own container registry.
  • AWS Lambda Deploy Function – A new Lambda deploy task that supports deploying code using any of the AWS Lambda-supported runtimes.
  • AWS Systems Manager Run Command – Enables you to run a command remotely on a fleet of EC2 instances or on-premises machines.
  • AWS Systems Manager Get Parameter – Reads the value of one or more parameters from Parameter Store and adds them as variables to the current build or release definition.

We used this last task, AWS Systems Manager Get Parameter, heavily in our demos to enable us to parameterize our builds based on the deployment stage (beta, gamma, prod) that we were deploying to.

Hope to see you next year!

It was great to go to re:Invent and meet so many awesome developers. Also good for us Seattleites to get some sun this time of year! Hope to see you next year.