Search for a command to run...
"I'm a 3rd-year Computer Engineering student at Marwadi University with skills in C++, web development (MERN stack), and DevOps tools like Kubernetes. I contribute to open-source projects and share tech knowledge on GitHub and LinkedIn. I'm learning cloud technologies and app deployment. As an Internshala Student Partner, I help others find jobs and courses." now currently focusing on #90DaysOfDevops
No comments yet. Be the first to comment.
So In This Series I am following 90 DaysOfDevops challenge , what i will learn in my devops journey i will share with you with my blogs ,You will get blog on tools which used by devops engineer , example :- Linux,ansible,terraform,docker,etc
Hi, I hope you had a great day yesterday learning about the launch template and instances in EC2. Today, we are going to dive into one of the most important concepts in EC2: Load Balancing. What is Load Balancing? Load balancing is the distribution o...
One of the most common networking issues in AWS occurs when an EC2 instance is correctly configured but remains inaccessible from the internet. Even if the security group, network ACLs, and applicatio
Static websites are one of the simplest and most cost-effective ways to host web content in the cloud. Instead of managing virtual machines or web servers, Amazon S3 allows you to store HTML, CSS, Jav
Containerization has become the standard way to package and deploy modern applications. Instead of installing software directly on virtual machines, developers package everything—including dependencie
On Day 37 of the KodeKloud 100 Days of Cloud Challenge, I explored one of the AWS security best practices—granting an EC2 instance access to Amazon S3 using IAM Roles instead of storing AWS credential
On Day 36 of the KodeKloud 100 Days of Cloud Challenge, I built a complete Application Load Balancer (ALB) architecture on AWS. Instead of exposing an EC2 instance directly to the internet, an Applica
Anand Raval
136 posts
I'm Anand Raval, a Cloud & DevOps Engineer with AWS Solutions Architect Associate (SAA-C03), Certified Kubernetes Administrator (CKA), and Azure Fundamentals (AZ-900) certifications. This blog covers AWS, Kubernetes, Terraform, CI/CD, cloud architecture, automation, cost optimization, troubleshooting guides, and hands-on DevOps projects.
Today is more of a reading excercise and getting some programmatic access for your AWS account
In order to access your AWS account from a terminal or system, you can use AWS Access keys and AWS Secret Access keys.
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.
Let me know if you have any issues while doing the task.
Log in to AWS Management Console:
Navigate to IAM:
Click on your username in the top right corner of the console and select "Security Credentials" from the drop-down menu.
Create a New IAM User:
Click on the "Access keys (access key ID and secret access key)" section.
Click on "Create Access Key".
Download Access Keys:
Launch EC2 instance with below configuration
AMI: Ubuntu
Instance Type: t2.micro
Network Settings: Allow HTTP and HTTPS traffic
Download and Install AWS CLI:
sudo apt update
sudo apt install unzip
To install the AWS CLI, run the following commands.
curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip"
unzip awscliv2.zip
sudo ./aws/install
Check AWS CLI Version:
Open your terminal or command prompt and run the following command:
aws --version
Ensure that AWS CLI is installed correctly and the version is displayed.
Configure AWS CLI:
Run the command:
aws configure
Enter your AWS Access Key ID, AWS Secret Access Key, Default region name, and Default output format when prompted.
Example:
$ aws configure
AWS Access Key ID [None]: <Your_Access_Key_ID>
AWS Secret Access Key [None]: <Your_Secret_Access_Key>
Default region name [None]: us-west-2
Default output format [None]: json
Verify Configuration:
Run a simple AWS CLI command to verify the setup:
Copy
Copy
aws s3 ls
This command lists your S3 buckets. If configured correctly, you should see a list of your S3 buckets or an empty list if you don't have any.
Thankyou for reading !!!!!