Options and guidelines to deploy code on AWS

[McDoit]

Would be nice to have some options to deploy a C# project on AWS

Maybe something like .DeployAsLambda, .DeployAsAppRunner, .DeployAsFargate etc

They can in turn use the CDK way of adding stacks or constructs to the AppHost

Or have I missed some more obvious way to do this?

[normj]

We haven't gotten as far as thinking about deployment yet but I can see do something like that on the project resources adding an extension method that gave manifest and later CDK hints what should be used as the compute target.

[davidfowl]

We have a model for this in the manifest that was invented for Aspire 9. project.v1 and container.v1 resources can have a nested "deployment" section that can embed a cloudformation or azure.bicep resource type.

e.g.
https://github.com/dotnet/aspire/blob/c0ff16dff269c0d3409c790e287e54e766ba89d9/playground/AzureContainerApps/AzureContainerApps.AppHost/aspire-manifest.json#L108-L124

The deployment tool uses this to deploy this compute resource using the underlying deployment resource type.

[jamescarter-le]

I think it would be great to be able to generate a CDK 'Stack' from the AppHost definition, Aspire is a nice tool to get things together locally for some testing of connectivity, but without being able to deploy or generate CDK files from it, it's just easier to write a docker-compose file for everything locally, and write the CDK the traditional way.

However, the C# CDK is pretty unweildly anyway even when used directly, it's unlikely that we would be able to just use Aspire > AWS directly, especially when you consider VPCs, subnets, ECS definitions, Roles/Policies.