Getting Started (AWS PowerShell) - Revision history

Sstrutt: Added "Get Instances"

2018-11-20T09:17:15Z

Added "Get Instances"

← Older revision		Revision as of 09:17, 20 November 2018
Line 28:		Line 28:
	</source>		</source>

			== Get Instances ==
			Example commands to get instances..
			<source lang="PowerShell">
			# Get running instances with Production tag
			$instances = Get-EC2Instance -Filter @(@{Name="tag:Function";Values="Production"};@{Name="instance-state-name";Values="running"}) \| Select-Object -ExpandProperty instances

			# Get specific instance
			$instance = Get-EC2Instance -Filter @(@{Name="instance-id";Values="i-012345678abcdef01"}) \| Select-Object -ExpandProperty instances
			</source>

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

Sstrutt: Added "Set Default Region"

2018-11-20T09:00:08Z

Added "Set Default Region"

← Older revision		Revision as of 09:00, 20 November 2018
Line 15:		Line 15:
	\|}		\|}

			== Set Default Region ==
			Most commands need to be run against a specific region. You can either specify this each time you run CmdLet, or if you predominantly run in one region, its more convenient to set a default region

			<source lang="PowerShell">
			Set-DefaultAWSRegion -Region eu-west-1
			</source>

			Other useful region commands...
			<source lang="PowerShell">
			Clear-DefaultAWSRegion # Clear default region
			Get-AWSRegion # Get list of regions, including what is default
			</source>

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

Sstrutt: /* Setup Credentials */ Added Linux unencrypted noye

2018-10-23T10:36:42Z

Setup Credentials: Added Linux unencrypted noye

← Older revision		Revision as of 10:36, 23 October 2018
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]]

Sstrutt: /* Setup Credentials */ Added more info on Access Key

2018-10-23T09:25:29Z

Setup Credentials: Added more info on Access Key

← Older revision		Revision as of 09:25, 23 October 2018
Line 1:		Line 1:
	== Setup Credentials ==		== 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		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		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

Sstrutt: Initial creation

2018-10-23T08:01:21Z

Initial creation

New page

== 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

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

<source lang="PowerShell">
Set-AWSCredential -AccessKey <your-access-key> -SecretKey <your-secret> -StoreAs default
</source>

[[Category: AWS PowerShell]]