Interacting with AWS Cloud Services

Question 1

CLI

Answer 1

1. Command Line Interface

Question 2

Various methods for interacting with AWS services/resources?

Answer 2

1. CLI
2. SDK
3. API
   - all must be configured with specific information (credentials, configuration details)

Question 3

SDK

Answer 3

1. Software Development Kit

Question 4

API

Answer 4

1. Application Program Interface

Question 5

Credential Providers

Answer 5

1. Methods to provide the necessary credential information
2. Some are specific, some are common (shared by most tools)
   - ex: of a Shared = config/credential files; these two files store profiles that can be saved and then invoked.

Question 6

Profiles

Answer 6

1. Groups of settings

- can be saved and invoked

Question 7

Environmental variables

Answer 7

1. Only one active at a time, but easily configurable

Question 8

Per-operation parameters

Answer 8

1. parameters may be changed as required based on the operation being invoked.

Question 9

General Credential order.

Answer 9

1. Per-operation parameter
2. Environmental variable
3. Shared Credentials File
4. Shared Configuration File
   - but this can be different depending, need to understand when setting up an environment which to use

Question 10

CLI default encryption

Answer 10

HTTPS TLS

Question 11

How to disable HTTPS TLS

Answer 11

1. no verify SSL Flag

- this is the default CLI encryption

Question 12

CLI - all interactions are remote?

Answer 12

1. Yes

Question 13

RESTful API

Answer 13

1. Optimized to work with serverless workloads

2. HTTP backends use HTTP APIs

Question 14

2 types of AWS APIs

Answer 14

1. RESTful

2. WebSocket

Question 15

Websocket

Answer 15

1. Allows user to build real time 2 way communication applications
   - ex: texting, streaming, 2 way dashboards

Question 16

API Gateway

Answer 16

1. API gateway = best choice if API needs API proxy functionality and API Management
2. maintains a persistent connection to handle the message transfers b/n backend services and client

Question 17

Cli Version 1 cut off date

Answer 17

1. January 2020, any builds released after that require python 2.7 / 3.5 or later
2. Versions 1 and 2 use the same command name, so it will create conflicts unless you uninstall client version 1

Question 18

Command: unistall Cli version 1

Answer 18

1. cd into downloads
2. .\aws. –version (to see if you have version 1)
3. pip uninstall awscli
4. Can download new executable

Question 19

How to install cli 2 on a Linux Ubuntu machine

Answer 19

1. sudo app update
2. install pip
3. sudo apt -y install python3 -pip
   - note: -y suppresses confirmations
4. (see what version of pip you have installed) pip3 –version
5. pip3 uninstall awscli
6. sudo app install -y curl (installs curl utility)
7. curl “https://awscli.amazonnews.com/awsclie-exe-linux-86_64.zip”
   - now can use unzip utlitiy to unzip awscli into archive
8. unizip awscliev2.zip (don’t need sudo b/c accessing my directory that I own)
9. sudo ./aws/install (install file has all of the commands to install awscli.)
10. aws –version (will now show awscliv2 and python 3.7 and botcore 2.0 (SDK with python)

Question 20

Install AWS Cli V2 on a Mac

Answer 20

1. open terminal prompt
2. curl “https://awscli.amazon.aws.com/AWSCLIEV2.pkg” -o “AWSCLIV2.pkg” (the second one is the target name) note the caps.
3. sudo installer -pkg ./AWSCLIV2.pkg -target
   - files are actually installed to user local AWS-CLI
   - installer creates a SIM link to user local AWS-CLI
4. password prompt install
5. aws –version

Question 21

AWS CLI

Answer 21

1. Command Line Interface - how you securely interact with your AWS account

Question 22

How to configure your CLI

Answer 22

1. Powershell will prompt you with 4 questions
   a) AWS Access Key ID (Sign in as admin IAM role -> security crendentials tab -> Access Keys )
   b) Secret Access key: you can only show this when you first create a key (but there is no limit on how many or when you can create these keys)
   c) default region: us-east-1
   d) default output format: json, jaml, text, table
   - CLI will store this information in a program called “default”
   - this is used anytime want to run an aws cli command that doesn’t specify which profile to use
   - saved in folder out of home directory - > .aws