Error accessing AWS through Visual Studio 2017 - amazon-web-services

I'm trying to connect to AWS (Amazon Web Services) using Visual Studio 2017. However, in the AWS Explorer in Visual Studio, it says "Failed to connect to AWS".
I created an account in the AWS IAM Management Console.
I assigned this account AdministratorAccess and created access keys.
I installed the AWS SDK for .NET for Visual Studio 2017.
In the Visual Studio AWS Explorer, I selected and created a New Account Profile.
The AWS Explorer shows "Failed to connect to AWS". (The Region list is still disabled.)
It seems like a rather simple process, but it's not working for me.
As a credential test, I set up the AWS CLI (Command Line Interface). Then I ran aws configure using the same Access key ID and Secret access key. I was able to access AWS--e.g. aws iam list-users and aws lambda list-functions. (I have some test lambda functions in my account already, and they showed up.)
What am I missing? Let me know if you need any more info.
Thanks.

Ok, so now it's suddenly working. I hadn't touched it for a while, and then clicked 'Refresh' in the AWS Explorer. The Regions list is now populated and all of my services are displayed.
Is it possible that AWS takes a while to propagate users and access? Just a thought.
-- Update
I tried again the following day, and now I get the original error again. I have not changed anything. In fact, my dev environment was left open overnight.
What the heck could have possibly changed?

Do you have the Fiddler installed and running? If yes, please close the Fiddler and try again.

Related

How to use AWS CLI secrets with IIS in production?

This is my question (literally stolen from here, but the ultimate question is different)
"I have written some code to retrieve my secrets from the AWS Secrets Manager to be used for further processing of other components. In my development environment I configured my credentials using AWS CLI. Once the code was compiled I am able to run it from VS and also from the exe that is generated."
My question is that once it's on my IIS production server, I repeat these steps but it doesn't work, because I run the steps as the user account I'm logged in as, but the IIS process doesn't run as the logged in user, so the code can't get what it needs.
I want the IIS process to be able to access these credentials under its own user profile. How do I place the credentials under that profile? This question seems to have the answer (C:\Users\<IIS_app_name>\.aws\credentials) but how do I actually access the <IIS_app_name>? Or figure out what it is? I attempt to access this path with my II_app_name, but I get an error that it doesn't exist.
This is an on prem server that accesses aws secrets manager.

Not able to attach Role via AWS Cloud9

I am new to Cloud9 and following this URL to setup Kubeflow in AWS.
Unfortunately, I am not able to attach the role to the user as mentioned in this URL.
Could anyone please suggest what could have gone wrong here?
While the link did not work for me here, below suggestion provided by AWS support worked for me.
Please navigate to Preferences on the menu bar in the AWS Cloud9 IDE.
- On the Preferences tab, in the navigation pane, choose AWS Settings-->Credentials.
- Use AWS managed temporary credentials to turn AWS managed temporary credentials on or off.

GCP Terraform authorization, error 403 permission issue

I am trying to create a Label module for GCP using Terraform. I was using Visual Studio code to write the script. What happened that Visual Studio code got linked to my other GCP account and now when I am trying to create a bucket in GCP, it is correctly targeting the right project but saying that source (my other GCP account) does not have permission to create bucket (which is right).
But now I don't know how to connect using right source so that it understand that I am an authenticated user.

Connect to another AWS account in Visual Studio Team Explorer

I installed AWS Toolkit for Visual Studio 2017. I clicked "Connect" and provided all the necessary keys. It got connected to my office AWS account.
Now I have a free account of AWS for learning purpose. I have a sample repository in CodeCommit under free account. Now I want to connect to this account.
Whenever I click "Connect", it automatically connects to office account and not offering me to enter credentials of the free account.
I opened "Manage Connections", but there I can only add a new Microsoft account not AWS.
You need to add your free account as a profile. The Providing AWS Credentials guide will walk you through adding multiple AWS profiles. Then, when you click "Connect" a pop up will allow you to choose the AWS profile that you would like for the connection. Once connected, there is an option to sign out if you would like to connect with a different profile.

Can CircleCI be used with Microsoft TFS (Visual Studio)?

I'm using microsoft TFS and I want to make continuous deployment on AWS using CircleCI.. Is that possible? if not, what should I exactly do?
Afraid not, CircleCI is just a continuous integration tools which TFS could also do the CI and include some useful task easily enable build and release pipelines.
You could use AWS Tools for Microsoft Visual Studio Team Services.
This tool include a new service endpoint type, AWS, to supply AWS credentials to the tasks at runtime.
It will create an AWS Credentials Connection. Select the AWS endpoint type and provide the following parameters:
A name used to refer to the credentials when configuring tasks that
require AWS credentials
AWS Access Key ID
AWS Secret Access Key
After an AWS subscription has be linked to Team Foundation Server, you could use the task deploy to Amazon EC2 with AWS CodeDeploy.
Note: Minimum supported environments
Visual Studio Team Services
Team Foundation Server 2015 Update 3 (or higher)