Skip to main content

How to Login to AWS using CLI with AzureSSO through Azure Active Directory

Testing on Windows 10 Release 1909 

Prerequisite (Install Visual Studio Code and the AWS CLI if you don't have it already installed and your Azure Active Directory is already configured and processing authentication)

1. Install Node.Js

(Use the LTS Edition/Version)

2. Check the node version in PowerShell or Windows Terminal:

node --version && npm --version

3. npm install -g aws-azure-login

*install will take about 15-20 minutes. Be patient and let it finish. 

4. Configure your profile

aws-azure-login --configure --profile=<<Name of your profile>>


aws-azure-login --configure --profile=migrationking

Pro Tip: It installs the profile on your machine under ~/.aws/config . You can edit the file with Visual Studio Code or Notepad++

#This will prompt to Enter the Azure AD details

*** Azure Tenant ID: << Enter the Azure AD Tenant ID from the Azure AD application configuration for the AWS Account to be accessed>> Azure Tenant ID URL:

*** Azure App ID URI:  << Replace this with Azure App ID identifier from App Config>> Find it via the direct url:

*** Default Username: << Replace this with your complete Azure AD Email Address FQDN (e.g.>>

*** Stay logged in: skip authentication while refreshing aws credentials (true|false) (false) << Type in false>>

*** Default Role ARN (if multiple): <<Hit Return Key, the CLI will fetch the list of role ARN's when trying to login post configuration>>.

*** Default Session Duration Hours (up to 12): (1)

Profile saved.

If your using GovCloud make sure that you identify the region inside of your ~/.aws/config file



cat ~/.aws/config

[profile migrationking]







5. If you want to login without a GUI prompt type

aws-azure-login --profile migrationking --no-sandbox --no-prompt

6. If you want to see the gui or your chasing errors

aws-azure-login --profile migrationking --no-sandbox --no-prompt --mode=gui


Correction Example:

Popular posts from this blog

How to Fix /storage/core filesystem Out of Disk Space Error on VCSA 6.0U1

How to fix the error of " The /storage/core filesystem is out of disk space or inodes" Step 1: Login to the new VCSA 6.0U1 HTML5 web client. https://ip address:5480 Step 2: Enable SSH and Bash Shell Step 3: Login as root and type "shell" at Command> shell Step 4: df -h (Check if it's out of space) /dev/mapper/core_vg-core               50G   50G     0 100% /storage/core Step 5: Stop the services of VCSA:  hostname: # service vmware-vpxd stop hostname: # service vmware-vpxd status (make sure it is stopped) Step 6:  cd /storage/core Step 7: rm -rf *.tgz ( be CAREFUL this in the wrong directory and you will be retrieving from a backup .) If you need help. Go to Cybercity ( )  Step 8: service vmware-vpxd restart Step 9: history -c Step 10:  Refresh the browser (https://ip address:5480). Now it's all green VMware KB

VMware Tools ISO Does Not Exist

1. You attempt to Install VMware Tools and you get the following error: The required VMware Tools ISO image does not exist or is inaccessible. vix error code = 21001 Unable to install VMware Tools. An error occurred while trayin got access image file "/user'/lib/vmware/isoimages/windows.iso" needed to install VMware Tools: 2 (no such file or directory). Please refer the product documentation or KB article 2129825 for details....blah blah blah you get the point. First...that KB article is wrong. It's 1036810: 2. Go to the latest VMware Tools of your OS (You don't need to be logged in): 3. Download the ISO and then WinSCP the file or whatever method you want to use to copy the file to /usr/lib/vmware/isoimages/ The quick and easy way is to just mount it and then install the VMware Tools. If you want to get gritty! Follow on! 4. If you don't