Forem: Shamim Ansari

Optimizing Your AWS EC2 Windows Instance: A Comprehensive Guide to Extending Root Volumes and Adding Extra Storage

Shamim Ansari — Sun, 24 Dec 2023 19:09:49 +0000

Extending the root volume of an EC2 Windows instance and attaching an additional volume is a multi-step process. Here's a step-by-step guide to achieve this:

Step 1: Launch an EC2 Windows Instance

Navigate to the EC2 Dashboard.
Click "Launch Instance" to create a new EC2 instance.
Choose a Windows AMI (Amazon Machine Image) and select an instance type.
In the "Add Storage" section, configure the root volume size according to your requirements.
Complete the instance launch wizard, including security group and key pair settings.
Launch the instance.

Step 2: Connect to the EC2 Instance

Once the instance is running, right-click it in the EC2 Dashboard, and select "Connect."

Follow the instructions to connect to the instance using Remote Desktop Protocol (RDP).

Step 3: Extend the Root Volume

Inside the EC2 Windows instance, open the "Disk Management" utility under Computer Management.

Locate the root volume, which is typically labeled as "C:." and you can see current storage as 30 GB (We will try to extend this volume)

Go to AWS console -> Volume -> Select volume -> Click on action -> 'Modify Volume' and change it to 40 GB

Go to EC2 Windows instance, open the "Disk Management" utility under Computer Management.

Note: You can see in the snip as total 40 GB online out of which 10 GB Unallocated

Right-click on disk and choose 'Extend Volume'

Validation:

You can see extended volume in below snip

Step 4: Attach an Additional EBS Volume

In the AWS Console, navigate to the EC2 Dashboard and click on "Volumes" in the left navigation pane.

Create a new EBS volume with the desired size (e.g., 30GB). Note the availability zone.
Back in the EC2 Dashboard, stop the Windows instance to attach the new volume.

Go to Volume and select it and choose 'Attache Volume' from 'Action'
Select instance ID & Create Volume
Back in the EC2 Dashboard
Start the instance.
Connect to the instance using RDP.
Open the "Disk Management" utility.
You will see the new volume listed. Initialize it and format it as needed.

Step 5: Validate the Configuration

In Windows Explorer, verify that the root volume (C:) has been extended with the additional space.

Create and modify files on the extra volume to ensure it is functioning correctly.
You can also check the disk sizes and available space in the "File Explorer" or use the "Get-Volume" PowerShell command.

Big big congratulation for completing this hands on LAB

Don't forget to do cleanup of all these AWS services which can lead to extra charges

Follow me on Linkedin | Twitter for more such contents and Check out my Services

Demystifying Cloud Computing: Exploring the Core Pillars of Private and Public Clouds, IaaS, PaaS, and SaaS

Shamim Ansari — Sat, 02 Dec 2023 18:18:24 +0000

The fundamental pillars of cloud computing include various deployment models and service models. Let's explore each of these pillars:

1. Private Cloud:

A private cloud is a cloud environment exclusively used by a single organization.
It is typically hosted on the organization's own infrastructure or in a dedicated environment provided by a cloud service provider.
Private clouds offer enhanced security and control, making them suitable for organizations with strict data privacy and compliance requirements.

2. Public Cloud:

A public cloud is a cloud infrastructure that is shared by multiple organizations and is owned and operated by a cloud service provider.
It offers on-demand resources and services to the public over the internet.
Public clouds are highly scalable, cost-effective, and suitable for a wide range of applications and workloads.

3. Private Cloud vs. Public Cloud:

This pillar explores the differences and trade-offs between private and public clouds, helping organizations choose the right cloud deployment model for their specific needs.
Considerations include factors like control, security, cost, scalability, and management.

4. Brief Introduction of Infrastructure as a Service (IaaS):

IaaS is one of the three primary cloud service models and provides virtualized computing resources over the internet. With IaaS, organizations can rent virtual machines, storage, and networking resources, allowing them to set up and manage their own infrastructure.
Users have control over the OS and software stack installed on the virtual machines.

5. Brief Introduction of Platform as a Service (PaaS):

PaaS is a cloud service model that abstracts away the underlying infrastructure, focusing on providing a platform for developing, deploying, and managing applications.
Developers can build and deploy applications without worrying about managing the underlying infrastructure.
PaaS offerings often include development tools, databases, and application hosting environments.

6. Brief Introduction of Software as a Service (SaaS):

SaaS is a cloud service model where software applications are hosted and provided to users over the internet on a subscription basis.
Users access SaaS applications through web browsers without the need for local installation.
Common examples of SaaS applications include email services, customer relationship management (CRM) software, and productivity tools like Google Workspace and Microsoft 365.

Follow me on Linkedin | Twitter for more such contents

Building a Globally Connected Network: A Step-by-Step Guide to VPCs, Internet Gateway, and VPC Peering in AWS

Shamim Ansari — Thu, 09 Nov 2023 15:28:57 +0000

Creating a Virtual Private Cloud (VPC) in AWS and setting up VPC peering between two regions can be a bit complex for beginners, but I'll provide a step-by-step guide to help you through the process. VPC peering allows you to connect VPCs in different regions as if they were on the same network. Here's a simplified guide:

Step 1: Log in to the AWS Console

Go to the AWS Management Console (https://aws.amazon.com/).
Sign in with your AWS account credentials.

Step 2: Choose the First Region

In the AWS Management Console, make sure you're in the region where you want to create the first VPC.

Step 3: Create the First VPC and Internet Gateway
Go to the VPC Dashboard:

In the AWS Management Console, navigate to the "Services" menu.
Select "VPC" under the "Networking & Content Delivery" section.
Click "Your VPCs" in the left-hand navigation pane.
Click "Create VPC."

Fill out the form for the first VPC:

VPC Name: Give your VPC a name (e.g., MyVPC).
IPv4 CIDR Block: Define the IP address range for your VPC (e.g., 10.0.0.0/16).
IPv6 CIDR Block: You can leave this blank for now.
Tenancy: Choose "Default."
Click "Create VPC."
In the VPC Dashboard, go to "Internet Gateways."
Click "Create Internet Gateway" and give it a name (e.g., MyIGW).
Select the Internet Gateway you just created and click "Attach to VPC." Choose the VPC you created.

Step 4: Create Subnets
After creating the VPC, go to "Subnets" in the VPC Dashboard.

Click "Create Subnet."

Fill out the form for each subnet:

Name tag: Give it a name (e.g., Subnet-1).
VPC: Choose the VPC you created.
Availability Zone: Choose an availability zone.
IPv4 CIDR Block: Define the subnet's IP address range (e.g., 10.0.1.0/24).
Repeat this process for each subnet you want to create.

Step 5: Set Up Route Tables and Internet Gateway

Go to "Route Tables" in the VPC Dashboard.

Create a route table for each subnet and associate it with the appropriate VPC.
Define the routes for each route table. For the public subnet, add a route to the Internet Gateway.

Step 6: Choose the Second Region

In the AWS Management Console, change your region to the one where you want to create the second VPC.

Step 7: Create the Second VPC and Internet Gateway

Note: Follow the same steps as in "Step 3" to create a VPC in the second region.

In the VPC Dashboard, go to "Internet Gateways."

Click "Create Internet Gateway" and give it a name (e.g., MyIGW).
Select the Internet Gateway you just created and click "Attach to VPC." Choose the VPC from the second region.

Step 8: Set Up VPC Peering

In the second region, go to "VPC Peering Connections" in the VPC Dashboard.
Click "Create Peering Connection."

Fill out the form:

Peering Connection Name: Give it a name (e.g., MyPeeringConnection).
Your VPC: Choose the VPC from the second region.
Peer VPC: Choose the VPC from the first region.
Click "Create Peering Connection."

Step 9: Accept Peering Request

In the second region, select the peering connection and click "Actions."
Choose "Accept Request."

Step 10: Configure Route Tables for Peering

In both regions, update your route tables to allow traffic from the peered VPC.

That's it! You've created VPCs in two different regions, set up VPC peering, and configured an Internet Gateway for the public subnet to enable internet access from the VPCs. Be mindful of security group and network ACL rules to control the traffic.

Follow me on Linkedin | Twitter for more such contents

AWS VPC Project: Learn How to Design and Configure Virtual Private Clouds

Shamim Ansari — Wed, 08 Nov 2023 18:02:12 +0000

Amazon Virtual Private Cloud (Amazon VPC) is a cloud networking service provided by Amazon Web Services (AWS) that allows you to create a logically isolated section of the AWS cloud where you can launch and manage AWS resources. It provides a way to build a private, secure, and isolated network environment within the AWS cloud.

Here are some key features and concepts related to AWS VPC:

Isolation: VPCs allow you to isolate your cloud resources. This means you can create a network that is logically separated from other VPCs and the public internet, providing enhanced security and control.
Subnets: Within a VPC, you can create one or more subnets. Subnets are segments of the IP address range of your VPC and are used to organize and control traffic within your VPC. You can make subnets public or private, depending on your network architecture requirements.
Internet Gateway: To connect your VPC to the internet, you can attach an Internet Gateway. This enables resources in public subnets to communicate with the internet.
NAT Gateway/NAT Instance: To allow resources in private subnets to access the internet while remaining hidden from incoming traffic, you can use Network Address Translation (NAT) gateways or instances.
Security Groups and Network ACLs: You can control inbound and outbound traffic at the instance level using security groups, and at the subnet level using network access control lists (NACLs).
Peering: You can peer VPCs to establish private connectivity between them. This can be used for various purposes, such as sharing resources or facilitating communication between VPCs.
VPC Endpoints: VPC endpoints allow you to privately connect your VPC to supported AWS services, such as S3, without using the public internet.
VPC Flow Logs: VPC Flow Logs capture information about IP traffic going in and out of network interfaces in your VPC. This is useful for security and monitoring purposes.
VPC VPN and Direct Connect: AWS provides options for connecting your VPC to your on-premises network using Virtual Private Network (VPN) connections or AWS Direct Connect for dedicated, high-speed network connections.
Transit Gateway: Transit Gateway is a way to simplify network connectivity between multiple VPCs, on-premises data centers, and remote networks. It acts as a hub for connecting these networks.
VPC Peering: VPC peering allows you to connect two VPCs together so that resources in one VPC can communicate with resources in another VPC. This connection is private, and it does not involve traffic going over the public internet.
VPC Endpoints: VPC endpoints enable you to securely access AWS services without using the public internet. This is useful for services like Amazon S3 or DynamoDB.

Project: AWS VPC Setup and Configuration

Setting up a hands-on project to work with Amazon VPC will help you gain practical experience in configuring and managing virtual private clouds. Here's a sample project that you can follow:

Objective: Create a secure AWS VPC with public and private subnets, launch EC2 instances, set up connectivity, and test network configurations.

Prerequisites:

An AWS account.
Basic knowledge of AWS services like EC2, Security Groups, and Route Tables.
AWS CLI and/or AWS Management Console access.

Step 1: Create a New VPC and Subnets

Log in to your AWS account using the AWS Management Console.
Navigate to the VPC service.
Create a new VPC with a CIDR block of your choice (e.g., 10.0.0.0/16).
Create two subnets within the VPC:
1.Public Subnet (e.g., 10.0.0.0/24)
2.Private Subnet (e.g., 10.0.1.0/24)

Step 2: Launch EC2 Instances

In the public subnet, launch an EC2 instance. This instance will serve as a web server. Ensure it has a public IP address.
In the private subnet, launch another EC2 instance. This instance will serve as a database server.

Step 3: Security Groups and Route Tables

Create security groups for both the web server and the database server. Allow necessary inbound and outbound traffic.
Configure route tables for the public and private subnets. The public subnet should have a route to the internet through the Internet Gateway.

Step 4: Test Connectivity

SSH into the web server from your local machine using the public IP address.
From the web server, attempt to connect to the database server using its private IP address.

Step 5: Additional Configuration (Optional)

Set up a Network Address Translation (NAT) Gateway or NAT Instance in the public subnet to allow the private server to access the internet while keeping it private.
Experiment with VPC Peering to connect your VPC to another VPC if you have one.

Step 6: Clean Up

Terminate the EC2 instances and delete any resources you've created to avoid ongoing charges.

Follow me on Linkedin | Twitter for more such contents

Host a Static website on AWS S3. Configure Amazon CloudFront for content delivery and Route 53 for domain management.

Shamim Ansari — Mon, 30 Oct 2023 08:02:43 +0000

You can fork my repository to complete this project or make a copy to your local system using pull command

Creating a static website and hosting it on AWS S3, configuring Amazon CloudFront for content delivery, and using Route 53 for domain management involves several steps. Here's a step-by-step guide to achieving this:

Step 1: Create an AWS Account

If you don't have an AWS account, sign up for one at https://aws.amazon.com/. Once you have an account, log in to the AWS Management Console.

Step 2: Create an S3 Bucket

In the AWS Management Console, go to the S3 service.
Click the "Create bucket" button.
Choose a globally unique name for your bucket (e.g., my-static-website-example).
Select a region for your bucket (choose the one closest to your target audience).
Leave the default settings and create the bucket.

Step 3: Upload Your Website Files

Inside your newly created S3 bucket, click on the "Upload" button.
Upload your HTML, CSS, JavaScript, and any other static assets (e.g., images) to the bucket.
Once uploaded, select your HTML file and click on the "Properties" tab. Under "Permissions," set the object to be public by clicking "Make public."

Step 4: Configure S3 for Static Website Hosting

In your S3 bucket, navigate to the "Properties" tab.
Scroll down to the "Static website hosting" section.
Select the option for "Use this bucket to host a website."
Set the index document (e.g., index.html) and the error document if desired.
Click "Save changes."

Step 5: Configure Amazon CloudFront for Content Delivery

In the AWS Management Console, go to the CloudFront service.
Click "Create Distribution."
Choose the "Web" distribution type.
Configure the following settings:
Origin Domain Name: Select your S3 bucket endpoint from the dropdown.
Viewer Protocol Policy: Choose "Redirect HTTP to HTTPS" or "HTTPS Only" depending on your preference.
Alternate Domain Names (CNAMEs): Add your domain name (e.g., www.example.com).
Default Root Object: Specify your index document (e.g., index.html).
Leave the rest as default or configure as needed.
Click "Create Distribution."

Step 6: Configure Route 53 for Domain Management

In the AWS Management Console, go to the Route 53 service.
Create a new hosted zone for your domain (e.g., example.com).
Inside the hosted zone, create a new record set.
Choose the record type (e.g., A - IPv4 address).
Alias: Yes.
Alias Target: Select your CloudFront distribution from the dropdown.
Create another record set for the "www" subdomain following the same steps.
Update the DNS settings of your domain registrar to use the Route 53 name servers.

Step 7: Test Your Website

It may take some time for DNS changes to propagate. Once it's done, you should be able to access your static website via your custom domain (e.g., www.example.com).

That's it! Your static website is now hosted on AWS S3, delivered through CloudFront for faster content delivery, and managed using Route 53 for domain management.

Follow me on Linkedin | Twitter for more such contents

Hosting a Portfolio website on AWS | Amazon Web Service | Step by Step Guide | Mini-Project for Beginners

Shamim Ansari — Sat, 21 Oct 2023 17:05:50 +0000

Hosting a portfolio website on an AWS Ubuntu server is a great way to showcase your work. Here's a step-by-step guide on how to do it:

Step-1: Launch an AWS EC2 Instance:

Log in to your AWS Management Console.
Navigate to the EC2 dashboard.
Click on "Launch Instance" to create a new EC2 instance.
Choose an Amazon Machine Image (AMI) for Ubuntu Server.
Select an instance type and configure instance details.
Add storage as needed.
Configure security groups to allow incoming traffic on ports 80 (HTTP) and 443 (HTTPS).
Review and launch the instance.

Step-2: Connect to Your Ubuntu Server:

Once the instance is running, connect to it using SSH. You can use a terminal on your local machine with the following command (replace your-key.pem and your-instance-ip with your actual key file and instance IP):

$ ssh -i your-key.pem ubuntu@your-instance-ip

Step-3: Update and Upgrade Your Server:

After connecting, run the following commands to update and upgrade your server:

$ sudo apt update
$ sudo apt upgrade

Step-4: Install a Web Server (Apache or Nginx):

You can choose between Apache and Nginx as your web server. Here's how to install Apache:

$ sudo apt install apache2

After installation, start the Apache server:

$ sudo systemctl start apache2

Step-5: Upload Your Website Files:

You can use SCP or SFTP to transfer your HTML, CSS, and JavaScript files to the server. Replace 'your-local-directory' with the path to your website files and 'your-remote-directory' with the path where you want to store them on the server:

$ scp -i your-key.pem -r your-local-directory ubuntu@your-instance-ip:your-remote-directory

Step-6: Configure the Web Server:

Create a virtual host configuration file for your website (replace your-public-ip with your server IP):

$ sudo vi /etc/apache2/sites-available/public-ip.conf

Add the following configuration (modify as needed):

<VirtualHost *:80>
    ServerAdmin webmaster@your-public-ip
    ServerName your-public-ip
    DocumentRoot /var/www/html/
    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined
</VirtualHost>

Step-7: Enable the virtual host and restart Apache:

$ sudo a2ensite public-ip.conf
$ sudo systemctl restart apache2

Step-8: Configure DNS (if using a domain):

If you're using a custom domain, configure your DNS settings to point to your server's IP address.

Step-9: Secure Your Website (Optional):

It's recommended to secure your website with HTTPS. You can use Let's Encrypt to obtain a free SSL certificate.

Step-10: Test Your Website:

Open a web browser and visit your domain or server IP to verify that your website is live.
Your portfolio website should now be hosted on your AWS Ubuntu server. You can further customize and optimize the server and website as needed.

Please do let me know if you face any error, I will be happy to help and troubleshoot your issue.

Follow me on Linkedin | Twitter for more such contents

AWS CLI | Important & Useful Commands

Shamim Ansari — Sun, 15 Oct 2023 17:33:38 +0000

The AWS Command Line Interface (CLI) provides a wide range of commands for interacting with various AWS services and managing your AWS resources. Here's a list of some commonly used AWS CLI commands, grouped by their respective services or functions.

AWS CLI installation based on Operating System

AWS CLI Core Commands:

aws configure: Set up your AWS CLI configuration, including access key, secret key, default region, and output format.
aws help: Get help and information on AWS CLI commands and their usage.

Amazon EC2 (Elastic Compute Cloud):

aws ec2 describe-instances: List EC2 instances in your AWS account.
aws ec2 run-instances: Launch a new EC2 instance.
aws ec2 terminate-instances: Terminate one or more EC2 instances.

Amazon S3 (Simple Storage Service):

aws s3 ls: List S3 buckets or objects.
aws s3 cp: Copy files and directories to/from S3.
aws s3 rm: Delete objects from S3.

Amazon RDS (Relational Database Service):

aws rds describe-db-instances: List RDS database instances.
aws rds create-db-instance: Create a new RDS database instance.
aws rds delete-db-instance: Delete an RDS database instance.

Amazon IAM (Identity and Access Management):

aws iam create-user: Create a new IAM user.
aws iam list-users: List IAM users.
aws iam attach-user-policy: Attach a managed policy to an IAM user.

AWS Lambda:

aws lambda create-function: Create a new Lambda function.
aws lambda list-functions: List Lambda functions in your AWS account.
aws lambda invoke: Invoke a Lambda function.

Amazon CloudWatch:

aws cloudwatch put-metric-data: Publish custom metrics to CloudWatch.
aws cloudwatch describe-alarms: List CloudWatch alarms.
aws cloudwatch get-metric-statistics: Get statistics for CloudWatch metrics.

Amazon ECS (Elastic Container Service):

aws ecs create-cluster: Create a new ECS cluster.
aws ecs list-container-instances: List container instances in an ECS cluster.
aws ecs run-task: Run a new task on an ECS cluster.

Amazon SQS (Simple Queue Service):

aws sqs create-queue: Create a new SQS queue.
aws sqs list-queues: List SQS queues in your AWS account.
aws sqs send-message: Send a message to an SQS queue.

Amazon SNS (Simple Notification Service):

aws sns create-topic: Create a new SNS topic.
aws sns list-topics: List SNS topics.
aws sns publish: Publish a message to an SNS topic.

Amazon DynamoDB:

aws dynamodb create-table: Create a new DynamoDB table.
aws dynamodb list-tables: List DynamoDB tables.
aws dynamodb put-item: Put an item into a DynamoDB table.

Note: To get specific information about a particular command, you can use the 'aws help' command followed by the command you want to learn more about. For example:

aws help ec2 describe-instances

Certainly! Here are more AWS CLI commands for various AWS services:

Amazon VPC (Virtual Private Cloud):

aws ec2 create-vpc: Create a new Virtual Private Cloud (VPC).
aws ec2 describe-vpcs: List VPCs in your AWS account.
aws ec2 create-subnet: Create a new subnet within a VPC.

Amazon SNS (Simple Notification Service):

aws sns list-subscriptions: List subscriptions to an SNS topic.
aws sns create-subscription: Subscribe an endpoint (e.g., an email address or an SQS queue) to an SNS topic.

AWS CloudFormation:

aws cloudformation create-stack: Create a new CloudFormation stack.
aws cloudformation list-stacks: List CloudFormation stacks in your AWS account.
aws cloudformation describe-stack-events: Describe events for a specific CloudFormation stack.

AWS CloudFront (Content Delivery Network):

aws cloudfront create-distribution: Create a new CloudFront distribution.
aws cloudfront list-distributions: List CloudFront distributions.
aws cloudfront create-invalidation: Create an invalidation for a CloudFront distribution.

AWS Elastic Beanstalk:

aws elasticbeanstalk create-application: Create a new Elastic Beanstalk application.
aws elasticbeanstalk create-environment: Create a new Elastic Beanstalk environment.
aws elasticbeanstalk describe-environments: Describe Elastic Beanstalk environments.

AWS Glue (Data ETL Service):

aws glue create-database: Create a new AWS Glue database.
aws glue create-crawler: Create an AWS Glue crawler to discover and catalog data.
aws glue start-job-run: Start an AWS Glue job run.

AWS Redshift (Data Warehouse):

aws redshift create-cluster: Create a new Amazon Redshift cluster.
aws redshift describe-clusters: Describe Amazon Redshift clusters.
aws redshift modify-cluster: Modify the properties of an Amazon Redshift cluster.

AWS Kinesis (Real-time Data Streaming):

aws kinesis create-stream: Create a new Kinesis data stream.
aws kinesis list-streams: List Kinesis data streams.
aws kinesis put-record: Put a single data record into a Kinesis data stream.

AWS Step Functions (Serverless Orchestration):

aws stepfunctions create-state-machine: Create a new Step Functions state machine.
aws stepfunctions list-state-machines: List Step Functions state machines.
aws stepfunctions start-execution: Start the execution of a Step Functions state machine.

AWS Secrets Manager:

aws secretsmanager create-secret: Create a new secret in AWS Secrets Manager.
aws secretsmanager list-secrets: List secrets stored in AWS Secrets Manager.
aws secretsmanager get-secret-value: Retrieve the value of a secret.

Follow me on Linkedin | Twitter for more such contents

How to write Jenkinsfile? | A Comprehensive Guide for Beginners

Shamim Ansari — Thu, 12 Oct 2023 09:15:09 +0000

A Jenkinsfile is a text file that defines the entire build process for a Jenkins pipeline. It uses a domain-specific language (DSL) that is based on Groovy syntax. Writing a Jenkinsfile involves defining stages, steps, and other configuration elements to automate the build, test, and deployment processes. Here's a basic guide on how to write a Jenkinsfile:

Create a Jenkinsfile: Start by creating a Jenkinsfile in your project's repository root or in a specified directory. You can name it Jenkinsfile without any file extension.

Specify Pipeline Configuration: Begin the Jenkinsfile by defining the pipeline configuration. There are two syntax options: Declarative and Scripted.

Declarative Syntax: This is a more structured and human-readable approach. Use the pipeline block to define your pipeline:

pipeline {
    agent {
        // Specify the agent (where the build runs)
        // e.g., 'docker', 'node', 'label', 'any', etc.
    }
    stages {
        // Define your build stages here
        stage('Build') {
            steps {
                // Define steps for the 'Build' stage
            }
        }
        stage('Test') {
            steps {
                // Define steps for the 'Test' stage
            }
        }
        // Add more stages as needed
    }
    post {
        // Define post-build actions, such as notifications or cleanup
    }
}

Scripted Syntax: This offers more flexibility but may be less readable for complex pipelines. Use the node block to define your pipeline:

node {
    // Define your pipeline steps here
}

Define Stages and Steps: Inside the 'stages' block, define the individual stages of your build pipeline. Each stage contains one or more steps. Steps can be shell commands, scripts, or predefined Jenkins plugins.

stages {
    stage('Build') {
        steps {
            // Execute build commands here
        }
    }
    stage('Test') {
        steps {
            // Execute test commands here
        }
    }
    // Add more stages and steps as needed
}

Configure Agents: In the 'agent' block (Declarative syntax) or using 'node' (Scripted syntax), specify where the build should run. You can use a specific node or container image.

Define Post-Build Actions: In the 'post' block, you can define post-build actions, such as sending notifications, archiving artifacts, or triggering other Jenkins jobs based on the build result.

Save and Commit: Save the Jenkinsfile and commit it to your version control system (e.g., Git). Jenkins will automatically detect and execute the pipeline when changes are pushed to the repository.

Configure Jenkins Job: In your Jenkins server, create a new pipeline job, specify the location of the Jenkinsfile in your repository, and configure any required parameters or triggers.

Run the Pipeline: Trigger the pipeline either manually or based on your configured triggers (e.g., code changes, schedules).

Monitor and Debug: Use the Jenkins web interface to monitor pipeline execution, view logs, and debug any issues that may arise.

Follow me on Linkedin, Twitter

How to write a YAML configuration file? | A Step-by-Step Guide for Beginners

Shamim Ansari — Mon, 09 Oct 2023 17:25:08 +0000

Writing a YAML configuration file is relatively straightforward, and YAML (YAML Ain't Markup Language) is often used for configuration files due to its readability. YAML uses indentation to represent the structure of data hierarchies. Here's a basic guide on how to write a YAML configuration file:

Start with a Document Indicator: In YAML, each document starts with --- on a new line. This indicates the beginning of a new document or configuration.

---

Define Key-Value Pairs: YAML uses a key-value pair structure. Use a colon : to separate the key from the value, and indent the value with spaces or tabs. Commonly, two spaces per level of indentation are used, but consistency is more important than the number of spaces.

key1: value1
key2: value2

Use Indentation for Nested Data: If you have nested data structures like dictionaries or lists, use proper indentation to represent the hierarchy. YAML is whitespace-sensitive, so make sure to align items correctly.

parent_key:
  child_key1: child_value1
  child_key2: child_value2

Lists and Arrays: To create a list or array, use a hyphen '-' followed by a space to indicate list items. Lists can contain strings, numbers, or other data types.

fruits:
  - apple
  - banana
  - cherry

Comments: You can add comments in YAML using the # symbol. Comments are for human readability and are ignored by most parsers.

# This is a comment
key: value

Quoted Strings: If a string contains special characters or starts with characters that might be misinterpreted as YAML syntax, you can enclose it in single or double quotes.

key: "This is a string with spaces and special characters: @!$"

Multi-line Strings: For multi-line strings, you can use the | character followed by a newline. This preserves newlines and leading/trailing spaces in the string.

description: |
  This is a multi-line
  string with
  preserved formatting.

Anchors and Aliases (Advanced): YAML allows you to use anchors ('&') and aliases ('*') to reference the same value in multiple places within your configuration. This is useful for reducing redundancy.

first_name: &name John
last_name: *name

References to Environment Variables (Advanced): In some cases, you may want to reference environment variables in your YAML configuration. You can do this using a special syntax, such as '${ENV_VAR_NAME}'.

api_key: ${SECRET_API_KEY}

Finalize the Document: End your YAML configuration with '...' or a new '---' to indicate the end of the document.

...

Remember to validate your YAML file using a YAML parser or linter to ensure that it is correctly formatted. YAML can be sensitive to indentation errors, so maintaining proper spacing is crucial for accurate parsing.

Follow me on Linkedin, Twitter

Kubernetes Cheatsheet: Essential Commands and Concepts for Efficient Container Orchestration

Shamim Ansari — Mon, 02 Oct 2023 13:43:56 +0000

Kubernetes Cheatsheet

Kubernetes Basics:

kubectl version: Check the Kubernetes client and server versions.
kubectl cluster-info: View cluster details.
kubectl get pods: List all pods in the current namespace.
kubectl get nodes: List all nodes in the cluster.
kubectl describe pod [pod-name]: Get detailed information about a pod.

Creating and Managing Resources:

kubectl create -f [yaml-file]: Create a resource from a YAML file.
kubectl apply -f [yaml-file]: Apply changes to a resource.
kubectl delete [resource-type] [resource-name]: Delete a resource.
kubectl edit [resource-type] [resource-name]: Edit a resource in the default text editor.
kubectl get [resource-type]: List resources of a specific type.
kubectl logs [pod-name]: View logs of a pod.

Scaling:

kubectl scale deployment [deployment-name] --replicas=[num-replicas]: Scale a deployment.
kubectl autoscale deployment [deployment-name] --min=[min-replicas] --max=[max-replicas]: Autoscale a deployment.

Networking:

kubectl expose [resource-type] [resource-name] --port=[port] --target-port=[target-port] --type=[service-type]:Expose a resource as a service.
kubectl get svc: List services.
kubectl port-forward [pod-name] [local-port]:[pod-port]: Forward ports from a local machine to a pod.

Configuration:

kubectl config view: View the current configuration.
kubectl config use-context [context-name]: Set the current context.

Pods:

kubectl exec -it [pod-name] -- [command]: Execute a command in a pod.
kubectl run [pod-name] --image=[image-name]: Create a new pod running a specific image.

Namespaces:

kubectl create namespace [namespace-name]: Create a new namespace.
kubectl get namespaces: List namespaces.
kubectl config set-context --current --namespace=[namespace-name]: Set the default namespace.

Secrets and ConfigMaps:

kubectl create secret generic [secret-name] --from-literal=[key]=[value]: Create a secret.
kubectl create configmap [configmap-name] --from-literal=[key]=[value]: Create a ConfigMap.
kubectl describe secret [secret-name]: View secret details.
kubectl describe configmap [configmap-name]: View ConfigMap details.

Storage:

kubectl get pv: List persistent volumes.
kubectl get pvc: List persistent volume claims.

Advanced Troubleshooting:

kubectl describe [resource-type] [resource-name]: Get detailed information about a resource.
kubectl top [resource-type] [resource-name]: Display resource usage statistics.

Remember to replace placeholders like [resource-type], [resource-name], [pod-name], etc., with your actual resource and object names.

This cheatsheet should help you get started with Kubernetes and serve as a handy reference as you work with containers and orchestration in Kubernetes.

Follow me on Linkedin, Twitter

Unlocking Free AWS Certification Vouchers: Your Path to Cloud Career Advancement

Shamim Ansari — Sun, 01 Oct 2023 10:04:14 +0000

Have you ever felt hindered by the cost of a certification voucher while pursuing your dream career in the cloud? Imagine the possibilities if you could get your hands on a free AWS certification voucher. Well, the good news is that it's not just a dream! In this post, I'll unveil a remarkable opportunity to obtain 100% free AWS certification vouchers and provide insights into seven other avenues to explore.

🔍 Exploring the AWS Emerging Talent Community
What is the AWS Emerging Talent Community? It's an exclusive, invite-only platform designed to empower learners from AWS Academy, AWS Educate, and AWS re/Start to advance their cloud skills and embark on rewarding cloud careers. By joining this thriving community, you gain access to personalized content recommendations, AWS Certification preparation resources, discount vouchers, and much more! Learn more

💡 Unlocking Your Invitation
While it's true that the community operates by invitation only, the process to secure your invite is surprisingly straightforward. You can achieve this too, in just a few hours. Simply create a free account at awseducate.com and utilize the filter feature to locate courses offering a badge. Completing any badge-eligible course puts you in line for an invitation to the ETC.

🌟 Exploring Other Access Routes
Apart from AWS Educate, two other AWS Education Programs can grant you access to the AWS Emerging Talent Community: AWS Academy and AWS re/Start.

🏆 Earn and Redeem
Once you're part of the community, you can accumulate points by conquering challenges. The more challenges you complete, the more points you earn, which can be redeemed for fantastic rewards, including AWS certification vouchers.

🌐 Beyond Vouchers: A World of Opportunities
The benefits of joining the AWS Emerging Talent Community extend far beyond obtaining a certification voucher. I recently took advantage of the AWS Mentor Program, which offers invaluable mentorship for emerging cloud professionals. The ETC is like a daily newspaper for cloud enthusiasts, where you'll discover curated technical and career-related content. It's also a fantastic platform to connect and network with like-minded individuals on their cloud learning journey.

🚀 Exploring Other Free Voucher Avenues
But wait, there's more! You can also secure free AWS certification vouchers through various other avenues:

1️⃣ AWS Community Builders Programme
2️⃣ All Builders Welcome Grant scholarship
3️⃣ AWS New Voices foundational speaker training program
4️⃣ Get AWS Certified – Sub-Saharan Africa Challenge organized by AWS Training and Certification
5️⃣ Join and actively participate in AWS User groups
6️⃣ Become an AWS Authorized Instructor
7️⃣ Attain the prestigious title of AWS Cloud Captain

Exploring the Fundamentals: A Comprehensive Guide to Linux for Beginner

Shamim Ansari — Sat, 30 Sep 2023 10:06:35 +0000

Linux:

Linux is kernel not OS
Linux is not a UNIX derivative. It was written from scratch
A Linux distribution is the Linux kernel and a collection of software that together creates an OS.

Linux Features:

Open source
Secure
Simplified updates for all installed software
Light weight
Multi-User or Multi-Task
Multiple distributions – RedHat, Debian, Fedora etc.

File System Hierarchy:
/home - home directory for other user /root – It is home directory for root user /boot – It contains bootable files for Linux /etc - It contains all configurations files. /usr – By default software are installed in this directory /bin – It contains commands used by all users /sbin - It contains commands used by only root user /opt – Optional application software Packages /dev – Essentials device files. This includes terminal devices, usb or any devices attached to the system.

Linux Commands & It’s use cases:

cat command
– The cat command is one of the most universal tools, yet all it does is Copy standard input to Standard Output.
Touch Command -

Vi editor -

A programmer text editor
It can be used to edit all kinds of plain text, it is specially useful for editing programs, mainly used for Unix programs.

Notes: :w – to save :wq or :x – To save and quit :q – quit :q! – force quit, no save
Vi is a standard whereas ‘nano’ has to be available depending on the linux we use.

rmdir – This command is used to remove the specified directory (empty) rmdir -p – Removes both the parent and child directory rmdir -pv – Removes all the parent and sub-directories along with verbose. rm -rf – Removes even non-empty file and directory. Rm -rp – Removes non-empty directories including parent and sub directory. rm -r – Removes empty directory hostname Ifconfig, cat /etc/os-release yum install httpd yum remove httpd yum update httpd service httpd start service httpd status chkconfig httpd on chkconfig httpd off which whoami echo yum list intalled useradd- To create user groupadd – To create a group gpasswd -a/-m – To add user into group, to add multiple user ln – Hardlink/ backup ln -s – Softlink/ short cut tar – Tar is an archiver used to combine multiple files into one gzip – It is a compression tool used to reduce the size of a file wget – It is the non-intracity network downloader.

Access mode/ Permission:

chmod – Used to change the access mode
chown – Change the owner of the file or directory
chgrp – Change the group of file or directory

File Details:

Note: r = read, w = write, x = execute

rm -rf * - To remove all file/directory in single command

Follow me on Linkedin, Twitter