AWS/CLI - Revision history

Pio2pio: /* Install awscli */

2021-06-15T08:15:15Z

Install awscli

@@ Line 3: / Line 3: @@
 sudo apt-get install awscli # via apt-get
 pip install awscli          # via pip
 </syntaxhighlightjs>

2021-06-04T10:17:48Z

Configure

← Older revision		Revision as of 12:17, 4 June 2021
Line 35:		Line 35:


	{{Note\| <tt>config</tt> file ~~atleast~~ with awscliv1 does not allow for trailing spaces in the configuration }}		{{Note\| <code>config</code> file at least with awscliv1 does not allow for trailing spaces in the configuration }}


	The <code>/.aws/config</code> profile sections must have the format of <tt>'''[profile profile-name]'''</tt>, except for the default profile, i.e:		The <code>~/.aws/config</code> profile sections must have the format of <tt>'''[profile profile-name]'''</tt>, except for the default profile, i.e:
	<source>		<source>
	[default]		[default]

2021-06-04T10:16:58Z

Configure

← Older revision		Revision as of 12:16, 4 June 2021
Line 33:		Line 33:
	$ aws ec2 describe-regions #to get a list all available regions		$ aws ec2 describe-regions #to get a list all available regions
	</source>		</source>
	~~The <tt>/.aws/config</tt> profile sections must have the format of <tt>'''[profile profile-name]'''</tt>, except for the default profile. For example:~~


	~~Example ~~~/.aws/~~credentials file~~		{{Note\| <tt>config</tt> file atleast with awscliv1 does not allow for trailing spaces in the configuration }}


			The <code>/.aws/config</code> profile sections must have the format of <tt>'''[profile profile-name]'''</tt>, except for the default profile, i.e:
	<source>		<source>
	[default]		[default]

2021-03-24T08:33:17Z

okta-aws-cli-assume-role

← Older revision		Revision as of 10:33, 24 March 2021
Line 255:		Line 255:
	Creating example ~/.okta/config.properties		Creating example ~/.okta/config.properties

	Add the following to ~/.bash_profile or ~/.profile:		# Add the following to ~/.bash_profile or ~/.profile:

	# OktaAWSCLI		# OktaAWSCLI
	~~if [~~[ -f "$HOME/.okta/bash_functions" ]~~]; then~~		[ -f "$HOME/.okta/bash_functions" ] && . "$HOME/.okta/bash_functions"
	. "$HOME/.okta/bash_functions"		[ -d "$HOME/.okta/bin" && ":$PATH:" != ":$HOME/.okta/bin:" ] && PATH="$HOME/.okta/bin:$PATH"
	fi
	~~if [~~[ -d "$HOME/.okta/bin" && ":$PATH:" != ":$HOME/.okta/bin:" ]~~]; then~~
	PATH="$HOME/.okta/bin:$PATH"
	fi
	</source>		</source>

2020-10-03T09:08:04Z

Auth to Kubernetes with okta-kubectl-auth plugin

← Older revision		Revision as of 11:08, 3 October 2020
Line 320:		Line 320:

	== Auth to Kubernetes with [https://github.com/jetstack/okta-kubectl-auth okta-kubectl-auth] plugin ==		== Auth to Kubernetes with [https://github.com/jetstack/okta-kubectl-auth okta-kubectl-auth] plugin ==
			* [https://code.tubitv.com/securing-aws-access-with-okta-49d720eb9f28 securing-aws-access-with-okta] Tubi

	== Multi account aws cli execution loop ==		== Multi account aws cli execution loop ==

2020-09-02T07:44:35Z

okta-aws-cli-assume-role

← Older revision		Revision as of 09:44, 2 September 2020
Line 282:		Line 282:
	OKTA_BROWSER_AUTH=false		OKTA_BROWSER_AUTH=false
	OKTA_MFA_CHOICE=OKTA.push		OKTA_MFA_CHOICE=OKTA.push
			OKTA_PASSWORD_CMD=$(echo "yourpassword") # command to fetch your password, instead prompting you
	</source>		</source>

2020-09-02T07:39:14Z

Multi account aws cli execution loop

← Older revision		Revision as of 09:39, 2 September 2020
Line 317:		Line 317:
	* [1] [https://github.com/oktadeveloper/okta-aws-cli-assume-role/blob/master/docs/man/okta-credential_process.1.md okta-credential_process] readme		* [1] [https://github.com/oktadeveloper/okta-aws-cli-assume-role/blob/master/docs/man/okta-credential_process.1.md okta-credential_process] readme
	* [2] [https://github.com/oktadeveloper/okta-aws-cli-assume-role/blob/master/docs/man/okta-listroles.1.md okta-listroles] readme		* [2] [https://github.com/oktadeveloper/okta-aws-cli-assume-role/blob/master/docs/man/okta-listroles.1.md okta-listroles] readme

			== Auth to Kubernetes with [https://github.com/jetstack/okta-kubectl-auth okta-kubectl-auth] plugin ==

	== Multi account aws cli execution loop ==		== Multi account aws cli execution loop ==

2020-09-02T07:33:07Z

okta-aws-cli-assume-role

← Older revision		Revision as of 09:33, 2 September 2020
Line 257:		Line 257:
	Add the following to ~/.bash_profile or ~/.profile:		Add the following to ~/.bash_profile or ~/.profile:

	#OktaAWSCLI		# OktaAWSCLI
	if [[ -f "$HOME/.okta/bash_functions" ]]; then		if [[ -f "$HOME/.okta/bash_functions" ]]; then
	. "$HOME/.okta/bash_functions"		. "$HOME/.okta/bash_functions"
Line 273:		Line 273:


	Create a configuration file, [https://github.com/oktadeveloper/okta-aws-cli-assume-role#configuring-the-application read more...]		Create a configuration file, [https://github.com/oktadeveloper/okta-aws-cli-assume-role#configuring-the-application read more...]. Note this file does not contain your Okta password.
	<source lang=bash>		<source lang=bash>
	# vi ~/.okta/config.properties		# vi ~/.okta/config.properties
Line 292:		Line 292:
	awscli # bash wrapper		awscli # bash wrapper
	withokta # bash wrapper		withokta # bash wrapper
			</source>


			Populate list of roles you can assume (unsure if this creates temporary file), but then you will be able to assume role using <code>--profile</code> described in the next step.
			<source lang=bash>
			$ okta-listroles
			Username: piotr
			Password: ***

			JSON response: [{"accountName":"Account: aws-111-us (111111111111)","roleOptions":[{"roleName":"saml-111-Administrator","roleArn":"arn:aws:iam::111111111111:role/saml-111-Administrator"}]},{"accountName":"Account: aws-222-eu (222222222222)","roleOptions":...]
	</source>		</source>

2020-08-31T12:46:59Z

Configure

← Older revision		Revision as of 14:46, 31 August 2020
Line 13:		Line 13:
	AWS_SESSION_TOKEN=3333 # token retrieved when using 'sts' service		AWS_SESSION_TOKEN=3333 # token retrieved when using 'sts' service

	# in 2015 AWS decided to ~~use AWS_SESSION_TOKEN in favour of~~ AWS_SECURITY_TOKEN(deprecated). There		# in 2015 AWS decided to rename AWS_SECURITY_TOKEN(deprecated) into AWS_SESSION_TOKEN. There
	# are still tools ~~like~~ Ansible, Terraform and Boto that support the deprecated variable name.		# are still tools eg. Ansible, Terraform and Boto that support the deprecated variable name.
	AWS_SECURITY_TOKEN=$AWS_SESSION_TOKEN		AWS_SECURITY_TOKEN=$AWS_SESSION_TOKEN
	</source>		</source>

2020-08-31T12:45:37Z

Configure

← Older revision		Revision as of 14:45, 31 August 2020
Line 8:		Line 8:
	;[https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-envvars.html Environment variables]		;[https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-envvars.html Environment variables]
	<source lang=bash>		<source lang=bash>
	AWS_ACCESS_KEY_ID=1111		AWS_ACCESS_KEY_ID=1111 # access keyID for your user or keyID retrieved when using 'sts' service
	AWS_SECRET_ACCESS_KEY=2222		AWS_SECRET_ACCESS_KEY=2222
	AWS_DEFAULT_REGION=eu-west-1		AWS_DEFAULT_REGION=eu-west-1