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

[acmesoft-arg]

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

Just set image tag as "latest" and point to ECR browsed from the list myapp.api (is the name)
Toolkit: 1.43.0.0
Visual Studio: 17.7.6

[coanpape]

I encountered the same behavior and compared a working case to a non-working case. I noted that the non working case was using Linux 2023 as opposed to Linux 2... Linux 2023 environment is new default behavior, via the AWS create environment wizard. I tried creating a new environment using ".NET Core running on 64bit Amazon Linux 2/2.6.2" and that worked. I also tried creating an environment via the AWS toolkit and noted that the created environment was Linux 2, supporting my suspicion that this version of the AWS toolkit is not supporting Linux 2023.
AWS toolkit version: 1.43.0.0
Visual Studio: 17.7.7
Hope this helps somebody

[floralph]

Hi, can you please provide details about the project you are trying to deploy, and what you were expecting to see as a deployment target in the Publish to AWS experience?

[coanpape]

The project is a .NET 6.0 WebAPI written in C#. In the past we had created an Elastic Bean Stalk environment running on the .NET Core running on 64bit Amazon Linux 2 platform, we'd been using this in various forms over the past year, having deployed to it multiple times, using the AWS Toolkit's "Publish to AWS" function. We recently rebuilt it and unknowingly built the new Linux 2023 platform. The AWS Toolkit's "Publish to AWS" function failed to list the Linux 2023 environment as a target.
Having noticed the difference in the platform I tried building another environment identical (AFAIK) excepting the Linux 2 platform. The AWS Toolkit's "Publish to AWS" function did list the newly created Linux 2 platform.

I'm happy to provide any further details, as needed.

[shruti0085]

Hello @coanpape we are tracking the issue you reported in #373
If that issue does not address your concern, please create a new issue and provide relevant details for us to further investigate it.

@acmesoft-arg we have not heard back from you so we will go ahead and mark this issue duplicate of the one indicated above.
If you have specifics you can share, please create a new issue and describe the project you are working with, and the deployment you were expecting to see.

[acmesoft-arg]

excuse me for late response: in my case the project is a asp.net core 7.0 web api, I tried to deploy to North Virginia, to the ECR to avoid any complexity for some reason publish to existing target never shows.
(I'm using fargate)
Operating system/Architecture
Linux/X86_64
Network mode
awsvpc

Now I'm think, could be a lack of role issue? In that case, which role do I need?