DEV Community: Mathinisha R

AWS Container Orchestration: EKS vs ECS

Mathinisha R — Sat, 30 Dec 2023 06:53:00 +0000

AWS Container Orchestration: EKS vs ECS

Amazon Elastic Kubernetes Service (EKS) and Amazon Elastic Container Service (ECS) are both container orchestration services provided by Amazon Web Services (AWS), but they are different in terms of their architecture and use cases.

Amazon Elastic Kubernetes Service (EKS)
Amazon EKS is a managed Kubernetes service designed to simplify the deployment, scaling, and management of Kubernetes clusters. By leveraging EKS, users can run containerized applications using Kubernetes without the burden of handling the underlying infrastructure intricacies. EKS is particularly well-suited for those already familiar with Kubernetes or looking to capitalize on its robust container orchestration capabilities.

Amazon Elastic Container Service (ECS)
Amazon ECS is a fully managed container orchestration service specifically tailored for Docker containers. It provides a straightforward solution for running containers without the need to manage the underlying infrastructure. ECS boasts tight integration with various AWS services, streamlining the process of building and deploying scalable containerized applications.

Key Distinctions:

1)Underlying Technology:
EKS is Kubernetes-based, providing users with the flexibility and compatibility of the Kubernetes ecosystem.
ECS, on the other hand, is a proprietary AWS service that offers simplicity without the complexity of managing Kubernetes.

2)User Base:
EKS is favored by users familiar with or inclined towards the feature-rich Kubernetes platform.
ECS, with its seamless integration into the AWS environment, is an excellent choice for those seeking a fully managed service without delving into Kubernetes intricacies.

3)Flexibility:
EKS offers greater flexibility and compatibility with the extensive Kubernetes tooling and ecosystems.
ECS, due to its tight integration with AWS services, excels in scenarios where simplicity and AWS service integration are top priorities.

In conclusion, the decision between Amazon EKS and Amazon ECS hinges on factors such as familiarity with Kubernetes, specific use cases, and the desired level of control over containerized applications. Whether opting for the flexibility of EKS or the simplicity of ECS, AWS provides solutions tailored to diverse preferences and requirements in the dynamic landscape of container orchestration.

Mastering AWS CLI Commands for User Management

Mathinisha R — Tue, 26 Dec 2023 13:43:10 +0000

Mastering AWS CLI Commands for User Management

This blog helps to understand the basic AWS CLI commands for creating users, attaching policies to define permissions, and organizing users into groups.

1)Configuring the AWS CLI:
Setting up AWS CLI with required credentials using aws configure command. This step ensures appropriate setup for later user management tasks.

aws configure

2)Creating an IAM User:
By using the "create-user" command, we can create a new IAM user. Provide a unique user-name to the identify the user.

aws iam create-user --user-name <user-name>

3)Attaching Policies to a User:
By using "attach-user-policy" command, we can provide a user specified permissions.

aws iam attach-user-policy --user-name <user-name> --policy-arn arn:aws:iam::aws:policy/<policy-name>

4)Creating an IAM group:
By using the "create-group" command, we can create groups to enhance organisation.

aws iam create-group --group-name<group-name>

5)Attaching Policies to a group:
By using the "attach-group-policy" command, we can provide necessary permissions to the group.

aws iam attach-group-policy --group-name <group-name> -- policy-arn arn:aws:iam::aws:policy/<policy-name>

6)Adding users to group:
By using the "add-user-to-group" command, we can associate users with a particular group , which can streamline management.

aws iam add-user-to-group --user-name <user-name> --group-name <group-name>

By gaining proficiency in these AWS CLI commands is essential to provide safe and efficient user administration in the AWS Cloud environment.

Understanding and Optimizing Storage with Amazon S3 Lifecycle Configuration

Mathinisha R — Fri, 22 Dec 2023 09:17:35 +0000

Understanding and Optimizing Storage with Amazon S3 Lifecycle Configuration

In the world of cloud tech, managing storage smartly is a big deal. Amazon S3, part of Amazon Web Services (AWS), comes with a cool feature called lifecycle configuration. This blog is here to help you understand it better, so you can use it to supercharge your storage.

1. What is Amazon S3 Lifecycle Configuration?
Amazon S3 Lifecycle Configuration is a feature that helps you automatically manage your files (objects) stored in Amazon S3 over time.

2.Why Does Lifecycle Configuration Matter?
Amazon S3 Lifecycle Configuration acts like a handy helper for your files. It automatically figures out where to store them and when to remove them, taking the hassle off your plate. This not only saves you money by using more affordable storage for older files but also keeps everything organized without any effort on your part.

3.Parts of S3 Lifecycle Configuration:

Upload Files: Start by putting your files into Amazon S3.

Set Rules for Storage Classes: Define rules to let S3 automatically move files between different storage classes based on their age and usage. This includes transitioning from Standard to Infrequent Access (IA), IA to Glacier for archiving, and even to the ultra-low-cost Deep Archive for long-term storage.

Automated Deletion Rules: Specify conditions under which files are automatically deleted after a certain period. This is handy for managing data with a limited lifespan.

Cost Efficiency: S3 Lifecycle helps you save money by using cost-effective storage classes for your files at different stages of their life. For example, you pay less for storing infrequently accessed files in IA or Glacier.

Simplicity and Automation: Instead of manually handling where to store each file or when to delete them, S3 Lifecycle automates these decisions based on the rules you set. This simplifies file management and ensures efficiency.

4. Smart Storage Moves with Lifecycle Magic:
Explore the different storage spots like STANDARD, INTELLIGENT_TIERING, and GLACIER in Amazon S3.
See how lifecycle magic helps your stuff move automatically between these spots, saving money and making sure things are super quick when you need them. It's like having a smart organizer for your storage space!.

To sum up, the combination of Amazon S3 and lifecycle configuration offers advantages in terms of cost-effectiveness, organization, and operational efficiency. The smooth transitions between storage classes, such as STANDARD or GLACIER, contribute to a streamlined process. Adopting these tools enhances storage management, ensuring an optimized and efficient cloud experience.

Monitoring an EC2 Instance with CloudWatch Alarm on AWS

Mathinisha R — Fri, 15 Dec 2023 14:08:03 +0000

Monitoring an EC2 Instance with CloudWatch Alarm on AWS

Summary
Amazon Web Services (AWS) offers a powerful tool to monitoring & controlling of cloud resources. In this hands-on we will learn launching of Amazon EC2 Instance and set up an CloudWatch alarm.

Requirements
You should have an AWS account and required permissions to create an Amazon EC2 instance and CloudWatch alarm.

Step:1 Launching an Amazon EC2 Instance

Navigate to the EC2 service through the AWS management console.
Click the “Launch Instance” button and start creating your EC2 instance.
Choose an AMI, here for this hands-on we will use Amazon Linux AMI.
Choose the Instance type, here will go with basic t2.micro instance(free-tier eligible).
Configure the instance count, network settings and other parameters stick to default.
Create security groups to manage incoming and outgoing traffic to our EC2 instance.
Review our configurations and click “Launch”.
Once you created an EC2 instance, your created instance will show in the instance dashboard as below.

Step:2 Monitoring EC2 Instance with CloudWatch Alarm

Choose your created instance and click the monitoring option, it will go to the CloudWatch console.
In the CloudWatch console, choose “Alarm” option and click “create” button.
Choose the “EC2” namespace and the metric you want to monitor.

Set the condition, the threshold of CPU utilization of our created EC2 Instance (example:50%).

Configure actions to our created alarm, such as sending notifications through Amazon SNS.
Review the configurations and click “Create Alarm”.

Now we have created an CloudWatch alarm for our created EC2 instance.

Project: Automating AWS with Ansible - Hello, Ansible!

Mathinisha R — Thu, 07 Dec 2023 10:18:25 +0000

Project: Automating AWS with Ansible – Hello, Ansible!

Summary
AWS with Ansible through the “Hello, Ansible!” project. This hands-on guide will tell you installing Ansible in AWS EC2 instance and execute a “Hello, Ansible!” project. From this we will learn installing Ansible in AWS instance, file generation, and personalized message display.

Objectives

Launching AWS EC2 Instance & EC2 Instance Connect
Installing Ansible on AWS EC2 Instance
Creating Ansible Playbook
Executing Ansible Playbook

Steps

Step:1 Launching AWS EC2 Instances & EC2 Instance Connect
1.1 EC2 Instance Launch:
Start an AWS EC2 Instance and configure all the settings as shown below.

1.2 AWS EC2 Instance Connect:
Connect your EC2 Instance using EC2 Instance Connect

Step:2 Installing Ansible on AWS EC2 Instance
2.1 Installing Ansible:
After connecting to your EC2 Instance via EC2 Instance Connect, follow the below commands.

To Update system packages command:

sudo yum update -y

Command for installing Ansible:

sudo amazon-linux-extars install ansible2 -y

Command for verifying Ansible installation:

ansible --version

Step:3 Creating Ansible Playbook
3.1 Creating Directory

mkdir hello_ansible
cd hello_ansible

Create an Ansible Playbook “hello_ansible.yml”

3.2 Running the playbook

ansible-playbook hello_ansible.yml

Step:4 Executing Ansible Playbook
We will see the “Hello, Ansible!” message by the following the command below

cat/tmp/hello_ansible/Hello.txt