Vishal Shekokar's Blog

Automating Jenkins Installation on AWS EC2 Instances with User Data and IAM Role Management

Vishal Shekokar's photo
Vishal Shekokar
·

2 min read

Introduction

In the world of cloud computing, Amazon Web Services (AWS) stands as a pioneer, offering a vast array of services to cater to diverse business needs. In this blog post, we'll explore the power of automation in AWS, specifically focusing on launching EC2 instances with Jenkins pre-installed using User Data. Additionally, we'll delve into the realm of Identity and Access Management (IAM), creating roles to manage user permissions more efficiently.

Automating Jenkins Installation with User Data

User Data in AWS: When launching an EC2 instance, the ability to pass user data opens up a realm of possibilities for automating configuration tasks. This includes installing applications, setting up environments, and running scripts post-launch.

Task 1 - Launching EC2 Instance with Jenkins:

  • Create a new EC2 instance on the AWS console.

  • In the "User data" field, provide a script to install Jenkins automatically.

  • Complete the instance launch, noting the public IP address.

  • Access Jenkins through the browser, following the public IP address: http://<instance-public-ip>:8080.

  • Verify the task completion by taking screenshots of the EC2 instance details (showing User Data) and the Jenkins dashboard.

User Data Script Example:

bashCopy code#!/bin/bash
sudo apt-get update
sudo apt-get install -y default-jdk
wget -q -O - https://pkg.jenkins.io/debian/jenkins.io.key | sudo apt-key add -
sudo sh -c 'echo deb http://pkg.jenkins.io/debian-stable binary/ > /etc/apt/sources.list.d/jenkins.list'
sudo apt-get update
sudo apt-get install -y jenkins
sudo systemctl start jenkins
sudo systemctl enable jenkins

Understanding IAM Roles

IAM in AWS: AWS Identity and Access Management (IAM) is the backbone of securing AWS resources, allowing centralized control over user access.

IAM Entities Explained:

  • IAM Users: Individual entities with unique credentials and permissions.

  • IAM Groups: Collections of users for easier permission management.

  • IAM Roles: Entities with policies determining their AWS actions, not bound to specific users or groups.

Task 2 - Creating IAM Roles:

  1. DevOps-User Role:

    • Permissions tailored for DevOps activities (e.g., EC2 management, S3 access).

  2. Test-User Role:

    • Permissions suitable for testing activities.

  3. Admin Role:

    • Full administrative access to AWS resources.

Conclusion

In this hands-on exploration, we've automated Jenkins installation on AWS EC2 instances using User Data, enhancing efficiency and reducing manual efforts. Additionally, we've ventured into IAM, creating roles to manage user permissions systematically.

Automation is key in the cloud era, empowering users to streamline processes, improve consistency, and focus on innovation. AWS, with its powerful features, provides a robust platform for such endeavors.

Embrace automation, secure your resources with IAM, and let AWS propel your cloud journey forward. Happy automating! 🚀

#90daysofdevopsAWSautomation