DEV Community: Souleymane. Tiendrebeogo

Install and configure AWS cli on Windows machine

Souleymane. Tiendrebeogo — Tue, 26 Sep 2023 05:58:08 +0000

There are 2 ways of installing aws cli on your Windows machine .

1-The long and boring way

Go to AWS official page , download the .msi file and the follow the instructions (click, click, click) just like you would normally install a normal software on your Windows machine.

2- Quick and easy through the cli

Make sure that you have chocolatey installed . Click here to learn how to install it
Launch PowerShell and run it as administrator and run the command bellow

 choco install awscli

After that you can check your cli version with the command bellow

 aws --version

Configure your AWS CLI to connect to your AWS console

Log into your aws account
Head to AIM
Head to users
Select a user
Head to security credential tab and create and access key . Make sure to keep them safe

Now lets configure the cli

aws configure

Enter your Access key ID and your Secret access key that you previously downloaded
AWS Access Key ID [*************************]
AWS Secret Access Key [*************************]
Default region name [ us-west-2]
Default output format [json]:json
Now you are good to go . To make sure lets check
aws iam list-users

If we get the users information as show in our aws console , that means the configuration is successful and now we can interact with our aws account from the cli.

Cheers!
Follow me on twiter @asksouley
Check my website : www.asksouley.com

AWS Storage : Core Storage Portfolio. Part 1

Souleymane. Tiendrebeogo — Tue, 26 Sep 2023 05:56:16 +0000

The AWS storage lineup comprises fundamental storage services offered by Amazon Web Services. This array of AWS storage solutions empowers businesses to swiftly acquire storage capacity without the need to invest significant time, finances, or resources in purchasing costly storage hardware that could become outdated within a few years.

AWS Storage Services encompass three primary storage categories:

Block Storage
File Storage
Object Storage

In the following paragraphs, I will provide simplified explanations for these three main storage types, which constitute the core storage services within AWS.

Block Storage: (EBS)

Much like DAS (Direct Attached Storage), Amazon's cloud-based storage, known as Elastic Block Storage (EBS), is well-suited for mission-critical applications and those that demand low-latency storage hosting. EBS, being a block storage solution, offers various classes within AWS:

General Provisioned SSD: gp3 and gp2
Provisioned IOPS SSD: Io1, Io2, and Io2 Block Express
Throughput I-Optimized HDD: St1, Sc1
Use Cases for EBS include:

Running databases
On-premises storage migration
Scaling your big data engines

File Storage (EFS)

Much like NAS (Network Attached Storage), Amazon's Elastic File System (EFS) serves as Amazon's solution for file storage and is particularly well-suited for data that needs to be shared. AWS offers various types of EFS storage:

Amazon FSx for Lustre
Amazon FSx for Windows File Server
Amazon FSx for NetApp ONTAP
Amazon FSx for OpenZFS
Use Cases for EFS include:

Streamlining DevOps processes
Modernizing applications
Improving content management systems
Supporting data science initiatives

Object Storage (S3)

Amazon's Simple Storage Service (S3) serves as Amazon's offering in the realm of object storage. Renowned for its cost-effectiveness, S3 proves to be the ideal destination for storing items such as snapshots or backups. The various tiers of AWS S3 encompass:

S3 Standard
S3 Standard-IA (Infrequent Access)
S3 Intelligent-Tiering
S3 One Zone-IA
Additionally, AWS Glacier provides options for:

Instant Retrieval
Flexible Retrieval
Deep Archive
Use Cases for S3 and Glacier include:

Data Lake

S3 is the optimal storage choice for running big data analytics, machine learning, and high-performance computing. Learn more here]

Backup and Restore

Ensure compliance with your Service Level Objectives (SLO) by meeting your Recovery Time Objectives (RTO) and Recovery Point Objectives (RPO). Learn more here

Low-Cost Data Archival

AWS's different tiers, including Glacier, enable companies to securely store their cold data at the lowest possible cost. Learn more here

Cloud-Native Applications

Expedite the development and launch of highly scalable cloud or web-based native applications. Learn more here

In the Next Post, I will be diving deep into each of the aws core storage services.

Lets link up on twitter: @asksouley
YouTube: @BlocksandObjects

Cloud Migration Strategies: The 6 "R". Part 1/6

Souleymane. Tiendrebeogo — Fri, 17 Mar 2023 00:28:08 +0000

With the boom on the field of cloud computing, there is more and more need for engineers capable of helping companies make their transition to the cloud smooth.
Being able to assist an organization to make safely make their transition to the cloud is a valuable skillset to have. In this post, I will go over the 6R of Cloud Migration Strategy.

It is important to mention that not all applications are optimized to run on the cloud. After careful evaluation, if you think that your application is still better of on the cloud, take a time to understand which cloud Migration Strategy fits your case best.

In most block posts, you will see the 6R's staring with "Refactor" and end up with "Retire" However, in this post I deliberately decided to go from the migration strategy that requires the Least effort to Most effort.

Retire
Retain
Repurchase
Rehost
Replaftorm
Refactor

Retire: I will coin this as "Drop and Go" In this option application that have reached end of life (EOL) are simply retired or decommissioned.

Retain: Also known as "Re-visit"
In this case some applications are just excluded from the migration strategy to be revisited on a later time. The reason for that may be things like latency, compliance/regulatory constrains for simply costs. In this case you will be running a hybrid environment.

Rehost : Mainly referred as _Lift and Shift _.
This is known as one of the most basic way of cloud migration strategy . It consists of moving your application or data without having to go through a code level changes. It is the preferred method for most organizations as it carries least amount of risks or complication.

Repurchase: This is also known as "Drop and Shop"
In this case, on prem or legacy applications are just dropped in favor of cloud-native vendor software packages It is like moving from proprietary application to SAAS

Replaftorm: This also know as Lift Tinker and Shift Method
In this method, candidate applications are packaged , tweaked a little bit and moved to the cloud via tools like AWS Data Migration Service

Refactor : I will coin this as " Go from scratch "
In this case, an application is rewritten re-architectured from scratch to make cloud native. It is a an expensive and time consuming method that require a team of qualify cloud engineers. Most companies goes that route if their existing applications are not cloud compatible.

In the following series I will have a full blog post of each of the 6R mentioned here.

Let me know if you find this post useful.

Lets link up on twitter : @asksouley
or visit my site. www.asksouley.com

Cheers!

Install Chocolatey on your Windows machine

Souleymane. Tiendrebeogo — Fri, 03 Mar 2023 05:30:08 +0000

"Chocolatey is a machine-level, command-line package manager and installer for software on Microsoft Windows. It uses the NuGet packaging infrastructure and Windows PowerShell to simplify the process of downloading and installing software"

https://chocolatey.org/install

After that Head to your Window search bar, select your cmd and launch it as administrator and then run the command below

 Get-ExecutitionPolicy

If it return " Restricted" , then follow up with the second command bellow

Set-ExecytionPolicy AllSigned or  Set-ExecutionPolicy Bypass -Scope Process

Now, are ready to install chocolatey by running the command bellow

 Set-ExecutionPolicy Bypass -Scope Process -Force; [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072; iex ((New-Object System.Net.WebClient).DownloadString('https://community.chocolatey.org/install.ps1'))

After that, run the command below to see chocolatey version

choco

you will be able to see chocolatey version

Adding an EBS volume to a running AWS EC2 Instance

Souleymane. Tiendrebeogo — Thu, 23 Feb 2023 05:34:18 +0000

When creating an EC2 instance on AWS, you are given the option to select the size of your storage. However you may run into a scenario where you need more storage than what you have provisioned . In that case. you can either increase the size of the storage or attach an extra EBS volume to your instance . This short post is about showing how to add an extra volume to an EC2 instance.

I assume that you already know how to create a EBS volume.

Spin out your instance and attach the new volume created by following the instructions below.

Select the new volume
Under the "Action" tab select "attach volume"
Select the EC2 instance you created
Under " Device name , keep /dev/sdf
(as best practice in linux, /dev/sda1 is for root volume and /dev/sd(f-p) for data volumes )
Select "Attach volume"

After attaching the volume, there are few extra steps to do in order to make sure that the volume is accessible.

SSH into your EC2 and run the command below

 df -f

you will only see the root volume and not the newly attached volume.

To "SEE" the newly mounted volume, run the command below

lsblk

Now you will see the newly mounted volume along with its mount point.

The next step will be to mount the new volume. Run the command below

 sudo mkfs -t xfs /dev/xvdf
 sudo mkdir  /data 
 sudo mount /dev/xvdf /data

After that when we run the "df -h" command , you we should be able to see the new volume along the with the root volume

Hope you like it.
Site Web :www.asksouley.com
Twitter :@asksouley

What is Ansible?

Souleymane. Tiendrebeogo — Wed, 15 Feb 2023 05:48:14 +0000

Ansible is an opensource IT automation tool that automates provisioning, configuration management, application deployment and orchestration. It was created by RedHat and then handled to the community via opensource.

Why use Ansible?

Assume that you are a system Administrator for a company and and you in charge of maintaining the infrastructure consisting of few webserver database servers, you will be fine as, maintaining and updating few servers manually is an easy task.

But in a situation where your company has hundreds of servers, then everything changes . To maintain and update hundreds of servers manually one by will not only be a dompting and inefficient use of the company's time.

That is when a tool like Ansible comes into pay. Ansible will allow you configure and update your server exactly how you want it to be through some lines of YAML and that is referred as an Infrastructure as Code (IaC).

How Ansible Work?

Traditionally, in order to manage servers remotely, you needed to have an agent installed thus the concept of Master/salve .The only way the master can get information from the salves were through the agents installed on the target nodes.

That is called Pull Configuration and configuration management as done by tools like Chef and Puppet.
But Ansible is different, and that is what makes it so attractive to lot of Sysadmins.

Ansible is Agentless. Unlike the Pull Configuration, there is no need to install an Agent on the target nodes. Ansible use what is called Push Configuration. Unlike Pull Configuration, you can Push information to your target node and force them to be configured as you wish.

Setting up and Ansible

Set up your main machine and install Ansible on it. In the next blog I will quickly show how to install Ansible. No need to have Ansible installed on your target machines.

In order for your Ansible instance to push the desired configuring, the only the only requirement will be an ssh connection.

The configuration that will be send ( Module ) will have a set of instructions called "Playbook" and will on your Ansible which as mentioned earlier can be a local machine, a VM, and or cloud instance like an AWS EC2.In addition to that , your Ansible node will have the list of the target machines in what is called "Inventory".

Playbooks

This is where will be store the set of instruction used to configure the target nodes a and they are written in YAML
Below is a basic playbook to install apache on an target server. In next blogs I will dive deeper into the structure of of an Ansible playbook by explaining it line by line. Oh and it you are a little confuse about the syntax, there are tools out there like yamlchecker that can help check the validity of your playbook

Ansible is an open-source IT automation tool that simplifies provisioning, configuration management, application deployment, and orchestration.

There are several reasons why you should use Ansible. As a system administrator responsible for maintaining a company's infrastructure with a few web and database servers, updating and maintaining them manually may be manageable. However, if your company has hundreds of servers, this becomes an arduous and inefficient task that consumes valuable company time. This is where Ansible comes in handy.

Ansible allows you to configure and update your servers precisely the way you want them to be, using a few lines of YAML. This is known as Infrastructure as Code (IaC).

Traditionally, to manage servers remotely, you needed to have an agent installed. This is known as Pull Configuration and is used by tools like Chef and Puppet for configuration management. However, Ansible is different and more attractive to sysadmins because it is agentless.

With Ansible, you can push information to your target nodes and configure them as you desire. You only need to set up your main machine and install Ansible on it; no need to install Ansible on your target machines. The only requirement is an SSH connection for your Ansible instance to push the desired configuration.

To configure target nodes, Ansible uses modules, which are sets of instructions called "playbooks." Playbooks are written in YAML and stored in the main machine, which can be a local machine, a VM, or a cloud instance such as AWS EC2. Your Ansible node will have a list of the target machines in "Inventory."

To illustrate, here is a basic playbook that installs Apache on a target server. We will delve deeper into the structure of an Ansible playbook in future blogs. If you find the syntax confusing, there are tools such as "yamlchecker" to validate your playbook.

---
  - name:  is https installed?
    hosts: all
    task:
      - name: Install apache
        apt:
            name: apache2 
            state: latest
        become: yes
      - name: index.html
        copy:
          content: "this is an ansible playbook"
          dest: /var/www/html/index.html
    become: yes
  - name: restart apache2
    service:
            name: apache2
            state: restarted
            enabled: yes
    become: yes

Inventory

This is where we maintain the structure of the network environment. Below is a random example of an inventory file for webserver . It has the IP Addresses of the targeted servers

"webservers: {
      "hosts:[
            " 192.168.0.1
              "192.168.0.10
]
}

In the next blog, I will show you how to spin up an AWS EC2 servers, install Ansible on the main server and deploy a basic webserver.

Follow me if you like my content on twitter at @asouley

Solved : centOS not getting IP address

Souleymane. Tiendrebeogo — Sun, 05 Feb 2023 08:11:31 +0000

This for those who have installed CentOS recently and either on VMware workstation or Oracle's VirtualBox and having connectivity issues. In this short blog post wills show you how to quickly fix that.
Make sure that your VM is running, and then head to settings , access the network tab and make sure the Bridge Adapter is selected under your main network Adapter as shown in the image below

Open nmtui with the command below

sudo nmtui

You will get a text base interface and from there , just proceed and activate the connection. Use the tab button to navigate to " Activate a connection"

AWS Storage : What Happened in 2022

Souleymane. Tiendrebeogo — Sat, 31 Dec 2022 19:46:19 +0000

Here in this post, I will be sharing with you all the new features that the AWS storage Team has implemented in 2022. Some of them were based on customers feedback while other were just part of AWS consistent strive for performance.

Amazon EFS Elastic Throughput

AWS EFS got even better with a new throughput option . On top of the existing throughput mode ( Bursting throughput and provisioned Throughput) that we are already familiar with, now we have Elastic Throughput that is suitable for spiky or unpredictable workload and performance requirement that are tricky to predict. or for applications that drive throughput at 5% or less of the peak throughput on average (the average-to-peak ratio). Elastic Throughput can drive up to 3 GiBps for read operations and 1 GiBps for write operations per file system, in all AWS Regions

Lower latency for EFS.

Now EFS can deliver up to 60% lower Read Operation while working with frequently accessed data and metadata and also up to 40% lower Write Operation with working with small files (<64kb)

For example, in region like N Virginia read latencies are as low as 0.25 milliseconds for frequently-accessed data, and write latencies are as low as 1.6 milliseconds for EFS-One Zone (and 2.7 milliseconds for EFS-Standard)

Amazon File cache Now generally available.

As fully managed, scalable, and high-speed cache File cache allow for processing file data stored in disparate locations—including on premises. It Cache accelerates and simplifies cloud bursting and hybrid workflows including media and entertainment, financial services, health and life sciences, microprocessor design, manufacturing, weather forecasting, and energy. This allow companies running hybrid infrastructure to be fully efficient.

AWS Glacier retrieval time.

Now the restore throughput on amazon Glacier has been improved by up to 10x when retrieving large volumes of archived data.
This improvement allows your applications to initiate restore requests from S3 Glacier at a much faster rate, significantly reducing the restore completion time for datasets composed of small objects. In addition, with S3 Batch Operations, you can now automatically initiate requests at a faster rate, allowing you to restore billions of objects containing petabytes of data with just a few clicks in the S3 console, or with a single API request.
The retrieval performance benefit scales with the number of restored objects, and reduces data retrieval completion times by up to 90%
Now companies can save money on storage cost by utilizing cold storage without taking a hit of retrieval speed

S3 access point now support cross account access point.

Amazon S3 Access Points simplify data access for any AWS service or customer application that stores data in S3 buckets. With S3 Access Points, you create unique access control policies for each access point to more easily control access to shared datasets. Now, bucket owners are able to authorize access via access points created in other accounts. In doing so, bucket owners always retain ultimate control over data access, but can delegate responsibility for more specific IAM-based access control decisions to the access point owner. This allows you to securely and easily share datasets with thousands of applications and users, and at no additional cost.

S3 Storage lens has now 34 new metrics.

Amazon S3 Storage Lens is a cloud storage analytics feature that delivers organization-wide visibility into object storage usage and activity. Now 34 additional metrics have been added to uncover deeper cost optimization opportunities, identify data protection best practices, and improve the performance of application workflows.

AWS MSK tiered storage.

Amazon Managed Streaming for Apache Kafka (MSK) now offers Tiered storage that brings a virtually unlimited and low-cost storage tier. Tiered Storage lets you store and process data using the same Kafka APIs and clients , while saving your storage costs by 50% or more over existing MSK storage options .
Tiered Storage makes it easy and cost-effective when you need a longer safety buffer to handle unexpected processing delays or build new stream processing applications making it now possible to scale your compute and storage independently, simplifying operations.

AWS Security Lake

AWS announced the preview release of Amazon Security Lake, a purpose-built service that automatically centralizes an organization’s security data from cloud and on-premises sources into a purpose-built data lake stored in your account.
Amazon Security Lake automates the central management of security data, normalizing from integrated AWS services and third-party services and managing the lifecycle of data with customizable retention and also automates storage tiering.

Multi region access point fail over control

Amazon S3 Multi-Region Access Points failover controls let you shift S3 data access request traffic routed through an Amazon S3 Multi-Region Access Point to an alternate AWS Region within minutes to test and build highly available applications.

With S3 Multi-Region Access Points failover controls, you can operate S3 Multi-Region Access Points in an active-passive configuration where you can designate an active AWS Region to service all S3 requests and a passive AWS Region that will only be routed to when it is made active during a planned or unplanned failover. This make it easy shift S3 data access request traffic from an active AWS Region to a passive AWS Region typically within 2 minutes to test application resiliency and perform disaster recovery simulations.

EBS RULE LOCK FOR RECYCLE BIN

Now with EBS you can set up a Rule Lock for Recycle Bin so customers can lock their Region-level retention rules to prevent them from being unintentionally modified or deleted. This new setting adds an additional layer of protection for customers to recover their EBS Snapshots and EC2 AMIs in case of inadvertent or malicious deletions.

I will be diving deeper into each of these release next year . Until them , Happy New year. Stay Safe

Installing Ansible on AWS EC2 Instance

Souleymane. Tiendrebeogo — Sun, 25 Dec 2022 22:05:39 +0000

Here in this blog post I will show you how to install Ansible on an AWS EC2 instance.

Bellow are the pre requisites

Have an AWS account
Spin and EC2 instance and connect to it via ssh or directly from your aws console .

For the purpose of this post I created an aws ubuntu instance.

After connecting to your instance run the commands bellow. This will make sure that your instance is up to get and that you got access to Ansible repos for install.

sudo apt update 
sudo apt-add-repository -y ppa:ansible/ansible

Once the steps above are done, now you may get started with the real deal by installing Ansible with the command bellow

sudo apt-get -y install ansible

After that, Ansible will be installed on your instance . You can now check the version with the command below

ansible --version

You will get the version of ansible installed along with the path to the configuration file.

Since the main goal of using Ansible is to automate our resource provisioning process, we will need to have boto3 installed. To learn more about boto3 , check my other blog post here

To install boto 3, just make sure that your instance is up to date one more time and running the command bellow

sudo apt update
sudo apt install python3-boto3

Just to make sure, you can also check that boto is installed by running the commands bellow

Method 1: pip show boto3
Method 2: pip list
Method 3: pip list boto | greb boto

Let me know if you like it . I tried to make it as short as possible . Next will be how to automate the creation of EC2 instance using Ansible.

Like it?
Follow me on @asksouley

Interact with AWS S3 using boto3, AWS's SDK for Python . Part 1

Souleymane. Tiendrebeogo — Tue, 08 Nov 2022 14:24:17 +0000

Boto3 is an amazon AWS SKD (Software Development Kit ) for Python. Using boto3, it is possible to create , update and delete resources on AWS S3 and EC3 by writing the appropriate Python's Scripts. Here in this blogpost, I will be focusing Amazon Simple Storage Service S3 and show how to create and S3 Bucket. Boto3 is fully maintained and published by Amazon Web Services.
To learn more about Boto3 , please check the link here.

Bellow are the prerequisites

Have an aws account
Lunch an EC2 Instance and SSH into it.
Install Python3
Install pip
Install Boto3

Installing python

sudo amazon-linux-extras install python3.8

** Installing pip **
Once you ssh into your EC2 instance , run the command bellow

sudo yum -y install python-pip

There is no need to install aws cli here since it already comes preinstalled when using amazon linux 2 EC2 instance.
Once installed you can check the version by running the code bellow

aws --version

Installing Boto3

pip install boto3

Once you have boto3 installed you can also check the version by running the command bellow

pip list

Once you have create the appropriate role and attached it to the instance , you should be able to make some call base on the permission that you passed to the instance via the AIM role

Create an IAM role and attach it to your ec2 instance. On that role you will specify the permission needed to complete your tasks which in here is to interact with aws S3 .I granted full access control to that role

Create a new role

Select your instance
Click on the drop down arrow and select security and then Modify the IAM Role and then chose the new IAM role you created

Here I have create an new role and granted it Full Access to S3 and now I should be able to get some response back from my aws resources.

Run the following command and to see the List all the buckets
you have in your account account

aws s3 ls

Create a new Bucket named volt123zzzz

aws s3 mb s3://volt123zzzz

As you can see a new bucket named(volt123zzzz) was created.

Remove bucket named volt123zzzz

aws s3 rb s3://volt123zzzz

Once run. the newly created bucket (volt123zzzz) will be removed

In later posts, I will dive deep in and show more functionalities and of aws and boto2

Lets link up on twitter @asksouley

Storage Performance: What are Latency, IOPS and Throughput and why should I care ?

Souleymane. Tiendrebeogo — Wed, 14 Sep 2022 03:48:08 +0000

When it comes to storage efficiency and performance, some of the basic key terms to understand are:

Latency
IOPS
Throughput

Having a full grasp around these key terms will help pick the best storage for your application.

In addition to picking up the right the volume type for your application , it is also important to confirm that the volume picked is compatible with the instance type you plan on using.

I know it seems like a lot of figure out but thankfully AWS compute Optimizer can help alleviate that burden by identifying optimal configurations using machine learning.

To learn more about instance and volume compatibility, check the resource that AWS has put together here

Latency

Latency is the true end-to-end client time of an I/O operation; in other words, it is the time elapsed between sending an I/O to EBS and receiving an acknowledgement from EBS that the I/O read or write is complete.
It is measured in unite of time and the lower the latency is the faster is the transaction time.

It is worth mentioning that Several other factors can affect the latency as well. Among them are block size and QueueLenght. The QueueLenght the number of transaction request pending. However the QueueLenght can be also controlled by assigning a value to it. That value will determined how many IP operation can line up.

IOPS

IOPS is the Input Output Operation per second, in other terms, it is the measurement of the number read and write operations that can be carried out one second and that is used to asset the performance of a storage . SSD are the best type of storage when higher IOPS is needed .

Throughput

Throughput measures the ability for a storage to handle read and write operation of large sequential data files and it is measured in Megabytes per Seconds (MB/s).

If your application for example is serving video files online, your need will be redirected toward a HDD base EBS Volumes since they are optimize to work very will with transactions where the dominant performance attribute is Throughput.

Amazon S3. 6 Essential CLI Commands to better manage S3 Buckets.

Souleymane. Tiendrebeogo — Thu, 08 Sep 2022 06:47:27 +0000

Amazon S3 or simple Simple Storage Service is a simple an object storage service offered by Amazon Web Service. With S3, the users can store various type of data (images, texts and or videos) as object in buckets.

AWS has a great web interface for creating , deleting and managing S3 buckets but it is nothing compared to the flexibility and the speed that the CLI offers

The list of CLI Command available is extensive. To lean more and go beyond what I will be converting in this blog post, click here

Bellow are 6 CLI Commands that any cloud engineer must know when dealing with Amazon S3.

1. The “mb” command Creating a new S3 Bucket.

This command is used to create new S3 Buckets. Make sure that the bucket name is unique.

Aws s3 mb myBucketName

aws s3 mb myBucketName

2. The “ls “command.

Used to inspect buckets by listing Buckets or the content of Buckets.

aws s3 ls

aws s3 myUnikMajicBucket

3. The “mv” command.

This is used to move things around. From local to S3, from S3 to local as well as between S3 Buckets.
People tend to get confused between the “mv” and the “cp” or copy command. mv is used to move files from location A to location B (The files no longer in location A). When “cp” is used, the file is in both location A and location B.

Move files from local to S3

aws s3 mv file1_name.txt s3://bucket-name/file2_name.txt_

Move from S3 to local

aws s3 mv s3://bucket_name/file1_name.txt file2_name.txt

Move files between S3 Buckets

aws s3 mv s3://bucket_name/file1_name.txt s3://bucket2_name /file2_name_2.txt

4. The “rb” command

This is used to delete or remove S3 Buckets. This will only work if the bucket is empty

aws s3  rb myBucket_name

Used to force delete a bucket along with his contents

aws s3 rb Bucket_name --force

5. The “rm “command.

This is used to delete the content of an S3 bucket.

aws s3 rm <s3url_to_the_file>

6. The “sync “command.

This is used to sync or update files either from local to s3, from s3 to local or between s3 buckets

aws s3 sync ./local_folder s3"//mybucket_name