Aws Toolkit For Visual Studio 2017

Posted on  by

AWS Toolkit - unable to redeploy
Posted on: Jan 7, 2020 6:29 AM
This question is not answered. Answer it to earn points.
I'm following the tutorial on how to deploy a .NET application to AWS (https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/create_deploy_NET.quickstart.html).
When I get to the 'Publish to Amazon web Services' dialog in the Visual Studio toolkit, the option to redeploy to an existing environment is disabled.
I've set up a profile and added the Access Key ID and Secret Key. Initially I tried using an IAM user, but it won't work even when I use the root access key.
Replies: 3 | Pages: 1 - Last Post: Apr 18, 2020 2:08 PM by: P. Johnson
Re: AWS Toolkit - unable to redeploy
Posted on: Jan 7, 2020 8:53 AM
I am not sure from your description what is disabled.
If the radio button is enabled, but the 'Next' button is not, the environment needs to be 'Ready' and the actual environment to deploy to needs to be selected.
If, however, the redeploy radio button is disabled, then make sure that your account profile and region are set correctly. One of the most common problems is the region..
Edited by: DrNetAWS on Jan 7, 2020 8:54 AM
Re: AWS Toolkit - unable to redeploy
Posted on: Jan 19, 2020 10:23 AM
I am experiencing a similar issue.
When attempting to redeploy a .net core 3.0 app using AWS Toolkit for Visual Studio 2019 the 'Redeploy to an existing environment' functionality is broken. For the most part, the redeploy radio button is disabled. When the screen first loads it shows a list of the existing environments to redeploy to but then as soon as the radio button is selected the list vanishes and the radio button becomes disabled. Closing & restarting the process often results in the radio button being disabled and the list being empty. Closing the Visual Studio Solution, and re-opening it resets the behavior. When the screen first loads again it shows the list of existing environments but as soon as an environment is selected the list quickly vanishes and the radio button returns to a disabled state.
Visual Studio Professional 2019
Version 16.4.3
AWS Toolkit for Visual Studio 2017 and 2019
Version: 1.15.2.1
Re: AWS Toolkit - unable to redeploy
Posted on: Apr 18, 2020 2:08 PM
I've had the same issue and found that switching to a different profile in the dropdown then switching back to the one I actually want to deploy with enables the redeploy radio button and populates the list.
Don't know why but it works for me.
You can just create another profile if you haven't got one already... as a heads up though, when I added my second profile I seem to remember it didn't add a carriage return from the last line of the default profile which corrupted my aws config file. I just went into the file and added a carriage return and a blank line between the profiles which fixed the issue.
Hope this helps.
Reply to this Thread
Answered question
Unanswered question with answer points still available
Unanswered question
Ace: 2000+ pts
Expert: 750-1999 pts
Guide: 300-749 pts
Enthusiast: 50-299 pts
Newbie: 5-49 pts
Amazonian

After the installer finishes, the toolkit functions as it has in previous versions of Visual Studio. To track issues with installing and using the toolkit in Visual Studio 2017, we opened the following GitHub issue in our AWS SDK for.NET repository. For any issues or comments about our Visual Studio 2017 support, please add to the issue. Jun 05, 2017 Microsoft Visual Studio 2017 is the version used in the examples. The AWS Toolkit for Visual Studio 2017. Download the latest version of AWS Toolkit for Visual Studio. If you have not already done so you will need to create an AWS account and a user profile which will be used by Visual Studio to upload your projects to AWS Lambda.


Aws toolkit for visual studio 2017 torrent

This issue affects Windows users, specifically Visual Studio with the AWS Toolkit installed, and it happens when the AWS Toolkit keeps a copy of old AWS credentials that may no longer be valid.

Here is the scenario.

I set up my AWS credentials using AWS configure, this stores the credentials in a file /user/.aws/credentials – I run Visual Studio, and AWS Toolkit keeps a copy of the credentials. Now, I decide to change the AWS credentials, and using the CLI again, I change the credentials on my machine. The CLI works fine, but Visual Studio is using old credentials, and breaks with an error like;

Studio

UnrecognizedClientException – The security token included in the request is invalid

at Amazon.Runtime.Internal.HttpErrorResponseExceptionHandler.HandleException(IExecutionContext executionContext, HttpErrorResponseException exception)
at Amazon.Runtime.Internal.ExceptionHandler`1.Handle(IExecutionContext executionContext, Exception exception)
at Amazon.Runtime.Internal.ErrorHandler.ProcessException(IExecutionContext executionContext, Exception exception)
at Amazon.Runtime.Internal.ErrorHandler.InvokeAsync[T](IExecutionContext executionContext)
at Amazon.Runtime.Internal.CallbackHandler.InvokeAsync[T](IExecutionContext executionContext)
at Amazon.Runtime.Internal.EndpointDiscoveryHandler.InvokeAsync[T](IExecutionContext executionContext)
at Amazon.Runtime.Internal.EndpointDiscoveryHandler.InvokeAsync[T](IExecutionContext executionContext)
at Amazon.Runtime.Internal.CredentialsRetriever.InvokeAsync[T](IExecutionContext executionContext)
at Amazon.Runtime.Internal.RetryHandler.InvokeAsync[T](IExecutionContext executionContext)
at Amazon.Runtime.Internal.RetryHandler.InvokeAsync[T](IExecutionContext executionContext)
at Amazon.Runtime.Internal.CallbackHandler.InvokeAsync[T](IExecutionContext executionContext)
at Amazon.Runtime.Internal.CallbackHandler.InvokeAsync[T](IExecutionContext executionContext)
at Amazon.Runtime.Internal.ErrorCallbackHandler.InvokeAsync[T](IExecutionContext executionContext)
at Amazon.Runtime.Internal.MetricsHandler.InvokeAsync[T](IExecutionContext executionContext)

Visual

Well, what how to clear the AWSToolkit cache?

Go to

C:Users<your user>AppDataLocalAWSToolkit

and

erase RegisteredAccounts.json

Aws Toolkit For Visual Studio 2017 Download

Then restart Visual Studio, and it will find the correct credentials.