Getting Started (AWS PowerShell): Difference between revisions

From vwiki
Jump to navigation Jump to search
(→‎Setup Credentials: Added more info on Access Key)
(→‎Setup Credentials: Added Linux unencrypted noye)
Line 7: Line 7:
Set-AWSCredential -AccessKey <your-access-key> -SecretKey <your-secret> -StoreAs default
Set-AWSCredential -AccessKey <your-access-key> -SecretKey <your-secret> -StoreAs default
</source>
</source>
{| class="vwiki-note"
|-
| '''Credentials file is not encrypted in Linux systems'''
|-
| When using the <source lang="PowerShell" inline>Set-AWSCredential</source> CmdLet on Linux systems the credentials file created is not encrypted (it is on Windows systems).  Therefore you need to ensure you secure the file, ideally store in an encrypted path accessible by only you.
|}




[[Category: AWS PowerShell]]
[[Category: AWS PowerShell]]

Revision as of 10:36, 23 October 2018

Setup Credentials

PowerShell Core can't store credentials securely by itself (the encryption used by Windows PowerShell is dependant on Windows DLL's, the Secure String object is not available in PowerShell Core), therefore AWS provide a method of storing AWS credentials securely for use which replicates how you'd do this in Windows PowerShell whereby credentials are stored in an encrypted file that can only be decrypted by the logged in user. You need the Access Key ID and Secret for your account. If you don't have an Access Key ID, go to IAM > Users and locate your account and select Create access key (the secret will not be accessible again, make a note of it somewhere secure).

The following command stores your credentials in the default profile, meaning that they will be used for operations where credentials are required, unless you specify a different profile of credentials to use

Set-AWSCredential -AccessKey <your-access-key> -SecretKey <your-secret> -StoreAs default
Credentials file is not encrypted in Linux systems
When using the Set-AWSCredential CmdLet on Linux systems the credentials file created is not encrypted (it is on Windows systems). Therefore you need to ensure you secure the file, ideally store in an encrypted path accessible by only you.