AWS Interaction Tools Overview
AWS in API driven and AWS Interaction Tools allow plenty of options to enable interaction with its services and includes.
AWS Management console
- AWS Management console is a graphical user interface to access AWS
- AWS management console requires credentials in the form of User Name and Password to be able to login and uses Query APIs underlying for its interaction with AWS
AWS Command Line Interface (CLI)
- AWS Command Line Interface (CLI) is a unified tool that provides a consistent interface for interacting with all parts of AWS
- Provides commands for a broad set of AWS products, and is supported on Windows, Mac, and Linux
- CLI required Access key & Secret key credentials and uses Query APIs underlying for its interaction with AWS
- CLI construct and send requests to AWS for you, and as part of that process, they sign the requests using an access key that you provide.
- CLI also take care of many of the connection details, such as calculating signatures, handling request retries, and error handling.
Software Development Kit (SDKs)
- Software Development Kits (SDKs) simplify using AWS services in your applications with an API tailored to your programming language or platform
- SDKs currently support a wide range of languages which include Java, PHP, Ruby, Python, .Net, GO, Node.js etc
- SDKs construct and send requests to AWS for you, and as part of that process, they sign the requests using an access key that you provide.
- SDKs also take care of many of the connection details, such as calculating signatures, handling request retries, and error handling.
Query APIs
- Query APIs provides HTTP or HTTPS requests that use the HTTP verb GET or POST and a Query parameter named “Action”
- CLI required Access key & Secret key credentials for its interaction
- Query APIs is the core of all the access tools and requires you to calculate signatures and attach them to the request
AWS Certification Exam Practice Questions
- Questions are collected from Internet and the answers are marked as per my knowledge and understanding (which might differ with yours).
- AWS services are updated everyday and both the answers and questions might be outdated soon, so research accordingly.
- AWS exam questions are not updated to keep up the pace with AWS updates, so even if the underlying feature has changed the question might not be updated
- Open to further feedback, discussion and correction.
- REST or Query requests are HTTP or HTTPS requests that use an HTTP verb (such as GET or POST) and a parameter named Action or Operation that specifies the API you are calling.
- FALSE
- TRUE (Refer link)
- Through which of the following interfaces is AWS Identity and Access Management available?
A) AWS Management Console
B) Command line interface (CLI)
C) IAM Query API
D) Existing libraries- Only through Command line interface (CLI)
- A, B and C
- A and C
- All of the above
- Which of the following programming languages have an officially supported AWS SDK? Choose 2 answers
- PHP
- Pascal
- Java
- SQL
- Perl
- HTTP Query-based requests are HTTP requests that use the HTTP verb GET or POST and a Query parameter named_____________.
- Action
- Value
- Reset
- Retrieve
Hey Jayendra,
Should the solution to Question 1 be “a” ?
As per AWS : “Query requests are HTTP or HTTPS requests that use the HTTP verb GET or POST and a Query parameter named Action or Operation that specifies the API you are calling.”
Am I missing something ? Please let me know
Hey LSK, this is a bit of ambiguous question and I marked it false only cause the query parameter is only action and not operation. However, the actual exam questions are not like this.
Hi Jayender,
AS per the link
http://docs.aws.amazon.com/elasticloadbalancing/2012-06-01/APIReference/using-query-api.html
Using Elastic Load Balancing Query Requests
Elastic Load Balancing provides APIs that you can call by submitting a Query request. Query requests are HTTP or HTTPS requests that use the HTTP verb GET or POST and a Query parameter named Action or Operation that specifies the API you are calling.
Calling the API using a Query request is the most direct way to access the web service, but requires that your application handle low-level details such as generating the hash to sign the request, and error handling. The benefit of calling the service using a Query request is that you are assured of having access to the complete functionality of the API.
Note
The Query interface used by AWS is similar to REST, but does not adhere completely to the REST principles.
I believe it is “TRUE”
Thanks Kiran, i think you are right. Updated the answer.
Hi Jayendra
Thank for an awesome blog.
I have a small request. Is it possible to have the question and answer section show just the question and allow us to provide the answer? After our response, the correct answer can then be shown? This will allow us to test our understanding of your post before seeing the correct answer.
Thank you
Thanks, I had been planing to do so but did not good options and end up with this format 🙂
I will look further to make it more quiz like, cause I have had multiple request for the same
Hi Jayendra
Thanks for sharing your knowledge. I have 2 questions for you.
1-When you say:
SDKs construct and send requests to AWS for you, and as part of that process, they sign the requests using an access key that you provide.
When you say access key, do you mean the secret access key of a IAM user?
2-In the SDK section you have written the following, but I guess that belongs only to the CLI section:
CLI required Access key & Secret key credentials uses Query APIs underlying for its interaction with AWS
Just to be clear, does the SDK also use behind the scenes the Query API?
Thanks
#1. SDKs uses the access keys and secret access keys with IAM role. The process is transparent and handle by the SDK itself.
#2. I think the line go duplicated. Have removed the same.