aws / aws/aws-toolkit-visual-studio

Publish to AWS: I could not deploy to an existing cloud app

Open
#467 2 comments 1 reaction 0 assignees View on GitHub
dotnet-deploy publish
Dominant language
No language data
Stars
135
Forks
37
PR merge metrics
No merged PRs in 30d

Description

In Publish to AWS, the Existing Targets list did not show my project. I expected to see it there.

Toolkit: 1.58.0.0
Visual Studio: 17.10.5

I've created an ElasticBeanstalk application on the AWS console.

In my visual studio, I used the SSO option to configure my AWS access -- and I can see the Elastic Beanstalk application in the AWS Explorer. But when I right click on my ASP.NET .NET 8 (minimal API) application to publish to AWS -- it does not recognise elastic beanstalk resources.

Maybe this is relevant - my account is a federated account where I have been granted admin rights.

Contributor guide

Open the contributing guide

Research direction

Start in the Publish to AWS flow at the Existing Targets list, comparing its resource discovery with the AWS Explorer view. Reproduce with Toolkit 1.58.0.0, Visual Studio 17.10.5, an ASP.NET .NET 8 minimal API, an existing Elastic Beanstalk application, and the reported federated SSO account. Done means the existing application appears as a publish target.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.