From 0bffde6d94c4148538fbf9d82076bd57e7394c6a Mon Sep 17 00:00:00 2001 From: JJ Date: Tue, 8 Apr 2025 17:58:14 +0100 Subject: first commit --- .../aws-solutions-architect/cli-sdk.md | 29 ++++++++++++++++++++++ 1 file changed, 29 insertions(+) create mode 100644 src/certifications/aws-solutions-architect/cli-sdk.md (limited to 'src/certifications/aws-solutions-architect/cli-sdk.md') diff --git a/src/certifications/aws-solutions-architect/cli-sdk.md b/src/certifications/aws-solutions-architect/cli-sdk.md new file mode 100644 index 0000000..a75a570 --- /dev/null +++ b/src/certifications/aws-solutions-architect/cli-sdk.md @@ -0,0 +1,29 @@ +# AWS CLI, SDK and Cloud Shell + +There are 3 ways to access AWS: + +1. The web console +2. AWS CLI +3. AWS SDKs + +The CLI is open source and allows you to make operations from the command line. + +The SDKs allow you to access AWS programatically through API calls using a set of language specific APIs, including: JS, Node, PHP, Python, .NET, Ruby, Java, Go, C++. + +## AWS CLI + +You need to use an access token to setup the AWS CLI. You define access tokens per user and then user : + +`aws configure` to create access for that user from the command line. + +## Cloudshell + +You can use cloudshell in the AWS console as well. + +This will automatically use the active user's credentials. It allows for : + +- File downloads +- Uploads +- etc etc + +It is only available in some regions, however. -- cgit v1.2.3