🚀Day 42: IAM Programmatic access and AWS CLI ☁

IAM Programmatic access

This is the feature of AWS that allows to access AWS resources without entering the AWS console. To access your AWS account from a terminal or system, you can use AWS Access keys and AWS Secret Access keys. Programmatic access can be quite powerful, so implementing best practices to protect access key IDs and secret access keys is important to prevent accidental or malicious account activity.

AWS CLI

The AWS Command Line Interface (AWS CLI) is a unified tool to manage your AWS services. With just one tool to download and configure, you can control multiple AWS services from the command line and automate them through scripts. The AWS CLI v2 offers several new features including improved installers, new configuration options such as AWS IAM Identity Center (successor to AWS SSO), and various interactive features.

Task-01: Create AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY from AWS Console

1. We have already seen how to create an IAM user in my previous blog. Here we can created a user.

   

2. Navigate to the security credentials section and create Access Key.

   

3. Choose the CLI option or as per your requirement.

   

4. Now, create the access key.

   

5. You can see two keys now which are the Access key and the Secret access key.

   

6. You can verify the status of the key in the user section.

   

Task-02: Setup and install AWS CLI and configure your account credentials

1. Download the Windows version of AWS CLI.

   

2. Follow the default process to install the CLI version.

   

   

3. After the installation, navigate to CMD and check the CLI version.

   

4. Connect AWS to CLI by providing the keys generated in Task 1. You can verify the connection of CLI to AWS by checking available instances in AWS.

Thanks for reading my article. Have a nice day.