DEV Community: rinku1511

Importance of UI: A reality SLAP

rinku1511 — Tue, 03 Sep 2024 06:45:35 +0000

I am adding this blog as a sweet SLAP on the face of all the people who think that UI is merely a superficial layer of software development, overshadowed by the grandeur of backend coding. For too long, the misconception has persisted that user interface (UI) is secondary to backend development. But let's set the record straight.

UI is not just about making things look pretty; it's about creating an intuitive experience for users. One of my favourite is that of Fireflyz tech, a It services company based in Ahmedabad. And contrary to popular belief, it can make or break the success of a product. It is like ignoring the effects of first impression with firm handshake and warm smile which can lead to a fruitful conversation. Let us walk through a few illustrations.

Slack initially struggled with user adoption due to its cluttered and complex interface. While the functionality was robust, navigating the platform and managing conversations proved challenging for users. Users reported difficulty in finding and organizing conversations, leading to frustration and low engagement. Slack started with a comprehensive redesign effort in 2015. The primary goals were to simplify navigation, streamline communication, and enhance overall usability. The UI/UX improvements had a profound impact on Slack's user engagement and retention. Within weeks of the redesign, Slack experienced a significant increase in daily active users almost by 10% and user satisfaction metrics.

Another great example, Amazon faced a significant challenge when many users abandoned their shopping carts at the checkout stage due to form prompting users to either log in or register. This step led to frustration and cart abandonment, costing Amazon millions in potential revenue. To tackle this problem, Amazon made a simple yet impactful change. They replaced the "Register" button with "Continue" and a message reassuring users that they didn't need to create an account to make purchases. Instead, they could proceed directly to checkout. This small adjustment resulted in a remarkable 45% increase in completed purchases and generated an additional $300 million in revenue within the first year alone.

Some might think that while a good UI can boost sales, there aren't any real downsides to a mediocre one. But here's another sweet slap in their faces to set things straight.

Taking the most well-known example of Windows 8 failure, Despite its innovative features, Windows 8 faced backlash primarily due to its radical departure well-designed UI. When you introduce an entire UI overhaul and force it on people, then you get a lot of negative pushback. Windows 8 did just that and got hate overall.

With these examples in mind and a good example of Fireflyz Tech website, let's not just slap UI on as an afterthought but give it the high-five it deserves. Cheers to better interfaces and brighter futures!

Hosting a WordPress Website on AWS LightSail with SSL

rinku1511 — Tue, 09 Apr 2024 18:46:06 +0000

In today's "oh where is my mobile phone" age, having an online presence is like having ice-cream in summers. Whether you're a blogger, entrepreneur, or small business owner, creating a website can help you reach a wider audience and establish your brand. Hence, comes in Wordpress, being the easiest and most accessible tool for the matter. Now, development aside, the question comes in about hosting the website. Where to host it so that it remain the safest yet accessible plus easy to manage, plus cheap, plus all-in-one management. There comes AWS in picture. With the power of AWS Lightsail, launching a WordPress site has never been easier. AWS Lightsail is a simplified cloud service that offers virtual private servers (VPS) with a user-friendly interface and predictable pricing.

First thing: Why choose lightsail above other hosting?

Simplicity: Lightsail offers a simplified user interface and easy-to-use tools that make it straightforward to deploy and manage virtual private servers (VPS) and applications.
Predictable Pricing: One of the standout features of Lightsail is its predictable pricing model. Unlike some other cloud services that charge based on usage or complex pricing structures, Lightsail offers flat-rate pricing with transparent billing. Plus there is always AWS pricing calculator for that. Visit this Link to see the pricing. Also, Lightsail offers a free tier for around first 3 months, allowing you to explore the platform without incurring any charges.
Scalability: While Lightsail is designed to be simple and easy to use, it still offers scalability for growing websites and applications. Users can easily upgrade their instances to larger sizes or add additional resources such as storage, RAM, or CPU as needed, ensuring that their hosting environment can scale with their business.
Integration with AWS Services: Lightsail is part of the larger AWS ecosystem, which means it integrates seamlessly with other AWS services such as Route 53 for DNS management, S3 for storage, and CloudWatch for monitoring. This makes it easy to leverage additional AWS services to enhance the functionality and performance of your website or application.
Security: As a service provided by AWS, Lightsail benefits from the security of the AWS infrastructure. AWS data centers are highly secure and adhere to industry-leading standards for data protection and compliance.
Reliability: Lightsail includes features such as automated backups and snapshots to help users protect their data and recover from any potential disasters.

Overall, AWS Lightsail offers a compelling combination of various metrics making it a top choice.

Lauching Virtual Server with Wordpress(Instance)

Go to the lightsail dashboard and from the left hand side navigation, choose "Instances". Click on create instance. This will open a screen with various choices. First is to select the region where you wish to launch the instance and the availability zone as well. Choose the region nearest to your customer base so as to decrease latency.

Now, choose the "WordPress" blueprint, which is a pre-configured image optimized for running WordPress sites. Choose linux/unix as operating system. If you are not comfortable with linux, you can choose windows OS as well.

Now, for additional security, create a new SSH key-pair. Note: you'll need this to connect to the instance. Before that, there is option to enable automated snapshots. If you enable this, LightSail will take automatic snapshots of your instance everyday. The snapshots for the last 7 days will retain and the older snapshots will be deleted.

Next is to select the size of the instance. Select the instance plan that best suits your needs – the smallest plan should be sufficient for most personal or small business websites.

Give name to your instance. Add necessary tags as per your requirement. Click on "create instance."

Now, once the instance is created, open the instance. TO access the Wordpress Admin Panel, click on the "Access WordPress Admin" on the top right corner. You will get the link with the IP on the pop-up. Click on that and you will be redirected to the access page.

The default username of the login is"user". For password, go back to your instance and select "retrieve default password" option. Now, this will give you steps to retrieve the default password. Copy that and you can access the wordpress admin panel.

The screen for password will look something like this.

Finally, you are in officially in business. Now, apply all the knowledge you have of wordpress and build a website like never before.

Connecting to DNS

Now, go to the instance. You will see the public IP for you instance. Copy that. Go to your DNS provider and add A record pointing to that IP. Now, anyone going to the URL will see the amazing wordpress website you created.

SSL

Now comes the important part. How to add SSL to the website. Don't worry, I got you covered (I mean AWS got you covered).

For this, open the instance page. Select the connect tab and scroll down till you see "connect using SSH" option.

Now, we will use the bncert tool to request an SSL/TLS certificate from Let's Encrypt. Note that using this toll will make the process simpler but is valid only for the domains and subdomains you mention while creating the SSL certificate. Enter the command:

sudo /opt/bitnami/bncert-tool

After this, you may be asked to whether you want to download update. Proceed as per your preference. Next is to insert the domain list that you want the certificate to be valid for. Enter those.

The next options depend on the domains you add. If you are adding www domain, you will be asked a few preferences for redirections. If not, you will be warned you for the absence of www domain. Then the action steps will be displayed and your consent to proceed will be asked.

Now, enter a valid email address to associate the certificate with.

Once the process is completed, your site will have SSL certificate attached and your site will be redirected for http to hppts.

Launching a WordPress site on AWS Lightsail is a straightforward process that can be completed in just a few easy steps. By following this guide, you can quickly deploy your site to the cloud and start reaching your audience online. With the power and flexibility of AWS Lightsail, the possibilities for your website are endless. Happy Wordpressing or AWSing or LightSailing ... Whatever you like!

Credit to: Fireflyz Tech

Hosting web application on AWS- Step to Step guide

rinku1511 — Wed, 13 Mar 2024 14:17:27 +0000

Welcome to the ultimate guide for hosting your web application on Amazon Web Services (AWS). In this comprehensive walkthrough, we'll cover every aspect of deploying a fully functional web app, from setting up the frontend and backend to managing databases, all while ensuring automation for a seamless development workflow.

Whether you're a seasoned developer looking to migrate to AWS or a newcomer exploring cloud hosting options, this guide is tailored to assist you in navigating the AWS ecosystem. By the end of this journey, you'll have a robust and scalable architecture that incorporates the best AWS practices, including automation with AWS CodePipeline.

Step 1: Managing Access with IAM

Before diving into the technical details, let's establish a secure foundation for your web app by managing access permissions effectively. AWS Identity and Access Management (IAM) is the key to ensuring a secure environment. Follow these steps to set up IAM for your project:

1.1 Create IAM Groups

IAM groups allow you to organize users with similar access requirements. Let's start by creating groups for different teams:
Billing Team: Team with billing access and permissions
Development Team: Team with full developer permissions
DevOps Team: Team with DevOps permissions
Read-Only Access Team: Team with read-only access
Dev Limited Permission Team: Team with limited developer permissions (for future use)
Associate users with their respective groups. IAM groups simplify permission management, ensuring that users have the appropriate access levels for their roles. This structured approach enhances security and streamlines user administration.

Step 2: Building a Robust Network Infrastructure with Amazon VPC

Now that you've secured access to your AWS environment using IAM, let's focus on creating a resilient and well-organized network using Amazon Virtual Private Cloud (VPC). Amazon VPC allows you to launch AWS resources in a logically isolated section of the cloud, providing you with full control over your virtual networking environment.

2.1 Establish VPCs for Development and Production

Begin by creating dedicated VPCs for your webapp. Here we are making a VPC in us-east-1 region.

2.2 Subnetting

Next, divide each VPC into subnets across different Availability Zones for increased fault tolerance. Divide subnets as public, private and RDS subnets each of them for dedicated purpose.

two Public Subnets for network connectivity.
two Private subnets for backend.
two Private subnets for database.

2.3 Enable Internet Connectivity with Internet Gateways

To allow communication between your VPCs and the internet, create and attach Internet Gateway to the VPC.

2.4 Configure Route Tables

Create route tables to define how traffic should flow between subnets. You need to create 3 route tables:
1.For Public Subnets: Attach the public subnets to this route table.
2.For backend Subnets: Associate 2 private subnets created for backend to this route table.
3.For Database Subnets: Associate 2 subnets dedicated to database here.

Public Subnet Routes

Private Subnet Routes

RDS Private Subnets Routes

By strategically associating route tables with corresponding subnets, you establish a well-organized and secure network infrastructure, laying the foundation for a robust and scalable web application hosting environment on AWS.

2.5 NAT Gateway

We need NAT gateway for giving our backend access to the internet for downloading and installing necessary packages. Go to the NAT console and create NAT Gateway in public subnet. Add the route to private route table directing all the traffic to NAT.

Step 3 Set Up Repository

3.1 Creating and Cloning Repository

Create AWS CodeCommit repositories each for frontend and backend and copy the clone URL from the Console.

Then, clone the repository to your local development environment for both frontend and backend using the following Git command:

git clone Link-of-the-repo-copied

Make code changes, and commit using:

git add .
git commit -m "Your descriptive commit message here"

Push the committed changes to the CodeCommit repository:

git push

Frontend Setup

4.1 Amplify

Deploy your frontend application using AWS Amplify, a managed service. The deployment process is automated through built-in CI/CD pipelines connected to the CodeCommit repository.

Start with choosing option of hosting a web-app in Amplify console.
Then choose AWS CodeCommit as a source.

Choose the repository created earlier as a source. and select the branch.

Add the environment variables needed in you application. Make sure to add the API of backend once its setup is done.

If you don't have any environment variables to add then keep other settings as they are and select Save and Deploy after checking the configurations once. Now the frontend on our WebApp is ready.

Step 5 Backend Setup

5.1 Elastic Beanstalk Setup

AWS Elastic Beanstalk is a fully managed service designed to simplify the deployment and management of applications in the cloud. Offering built-in support for various programming languages, databases, and frameworks, Elastic Beanstalk streamlines web application deployment while providing robust capabilities for load balancing, autoscaling, and launching EC2 instances.

Beanstalk Application

An Elastic Beanstalk application acts as a container for deploying and managing related web application resources. It serves as a logical grouping for components such as application versions, environments, and configurations.

Beanstalk Environment

An Elastic Beanstalk environment represents the runtime configuration for your web application. This includes resources like Amazon EC2 instances, databases, load balancers, and auto-scaling settings.

Components Managed by Beanstalk
Elastic Beanstalk takes care of several essential components:

Load Balancer
Autoscaling Groups
EC2 Instances
Security Groups
Service Roles (IAM)

Logging in Beanstalk

Logs from the EC2 instances can be collected using the Beanstalk log feature, providing comprehensive details from instance launching to the present date.

5.2 Creating Application

Click on "Create Application" to start the process. Enter a unique and descriptive Application name. Optionally, provide a "Description" for your application. Click "Create" to proceed.

After creating the application, click on "Create Environment" within the application dashboard. Select "Web server environment" as the environment tier. For "Environment name," use a naming convention as per your requirement. Choose a "Platform" that aligns with your backend technology. In this case, we are using Node.js 18 running on 64bit Amazon Linux 2023. Under the "Application code," choose the option of sample code as of now. We will get back to this with AWS CodePipeline.

Choose the appropriate option for Presents as per your need. Note that the Single instance presets are primarily recommended for development use cases and will save costs. The High availability presets are recommended for production environments.

Next is to configure service access. Choose the default service role. If you don't already have key-pair, go to EC2 console and create one. Use that here. Make an EC2 instance profile with "AWSElasticBeanstalkWebTier" permission.

5.3 Network Setup in Beanstalk

Choose the VPC and the subnets that you have created for the backend. Similarly, choose the subnets for database. Also, click on enable database option to allow beanstalk to manage the database as well.

5.4 Database Creation

Choose the appropriate database settings for your application. Here we are using mysql database.

5.5 Backend Traffic and Scaling

This step essentially revolves around the configurations of backend instance and the way you want it to scale. Select appropriate configurations pertaining to instance for your application.

Here we are going to enable autoscaling and load balancing. Change the environment type to "load balanced" and choose the minimum and maximum capacity- the minimum number of backend instances and the maximum number that you want to scale.

There are various things in this step that can be configured ranging from scaling policy to AMI and instance type. Here we will keep all those things default. You can alter then as per your need.

Moving to load balancer settings, by default the subnets for the backend EC2 will be selected. Make sure to change those to the public subnets we created.

Keep the other options as they are for load balancer. Note that the security group for load balancer will be created by beanstalk itself. We don't need to worry about it. Also, you can add listeners and listeners rules as per your application need in the beanstalk console itself. We will avoid that here.

5.6 Logging and Monitoring

Here we are going to keep all the options as default. You can change them as per your monitoring and updates needs. There is option to put maintenance window as well. All the environment variables needed in the application can be added here.

Review the entire environment configurations and then submit. It may take a few minutes for the environment to be up. Check that the status of the environment is OK.

Step 6 Pipeline Configuration

This is the simplest step. Go to AWS CodePipeline and select the create button. Give appropriate name to your pipeline and to the service role. Keep all the other settings as default in first step.

Choose source as AWS CodeCommit as we want to use the backend repository we created earlier. Choose the repository and the branch. Keep other options default.

Next step is build. Choose AWS CodeBuild for the build stage of pipeline. Click on create project if you don't have project created. It will open a CodeBuild console in new window.

Keep the build project configurations as default. Note that CodeBuild uses an instance in background for creating build. Means you can change the underlying image as well.

Once the build project is created go back to CodePipeline and choose the project you created.

Move to the next stage which is deploy. Choose AWS Elastic Beanstalk as the Deploy Provider. Select the application name that we created and environment to which you want to deploy the code.

Review the pipeline configurations and create the pipeline. This will trigger the pipeline and beanstalk build as well. And the code will go to your beanstalk backend instances.

Congratulations! You have your web-app up and running. Please comment down for any doubts and get them solved!

Ps: Source: Fireflyz Tech

Terraform for IoT: Powering Connected Devices in the Cloud

rinku1511 — Fri, 28 Jul 2023 14:14:02 +0000

Overview of IoT in the Cloud

The way we interact with devices and data has been completely transformed by the Internet of Things (IoT). When it comes to managing huge networks of connected devices, cloud platforms are crucial since they offer the infrastructure and services required. To create and maintain scalable, secure, and effective IoT ecosystems, this blog discusses how Terraform, an Infrastructure as Code (IaC) tool, works in conjunction with cloud platforms.

Building and automating IoT Infrastructure with Terraform

Terraform simplifies the process of building and managing cloud resources for IoT deployments. With its declarative syntax and provider ecosystem, terraform empowers developers and operations teams to provision edge devices, gateways, and cloud resources with ease. In this section, we'll walk through the steps of creating an IoT infrastructure using Terraform by considering an example. In this example, we'll see how to use Terraform to build a simple IoT infrastructure with AWS IoT Core.

Let's create an AWS IoT thing registry to manage our IoT devices:

resource "aws_iot_thing_type" "device_type" {
  name = "IoT_Device_Type"
}

resource "aws_iot_thing_group" "device_group" {
  name = "IoT_Device_Group"
  thing_group_properties {
    thing_group_description = "Group for IoT Devices"
  }
}

Now, let's create two IoT devices and associate them with the IoT thing registry:

resource "aws_iot_thing" "device_1" {
  name             = "IoT_Device_1"
  thing_type_name  = aws_iot_thing_type.device_type.name
  thing_group_name = aws_iot_thing_group.device_group.name
}

resource "aws_iot_thing" "device_2" {
  name             = "IoT_Device_2"
  thing_type_name  = aws_iot_thing_type.device_type.name
  thing_group_name = aws_iot_thing_group.device_group.name
}

Now, let's configure AWS IoT rules to process data from the IoT devices and store it in Amazon S3:

resource "aws_iot_topic_rule" "iot_rule" {
  name          = "IoT_Data_Rule"
  sql           = "SELECT * FROM 'iot/data'"
  description   = "Rule to process IoT data"
  rule_disabled = false
  actions {
    lambda {
      function_arn = "" #url of the lambda function
    }
  }
}

To enable communication between the IoT devices and AWS IoT Core, we need to set up an IoT policy and attach it to the devices:

resource "aws_iot_policy" "iot_device_policy" {
  name        = "IoT_Device_Policy"
  policy      = data.aws_iam_policy_document.device_policy.json
  description = "Policy for IoT devices"
}

data "aws_iam_policy_document" "device_policy" {
  statement {
    actions   = ["iot:*"]
    resources = ["*"]
  }
}

resource "aws_iot_policy_attachment" "device_policy_attachment_1" {
  policy_name = aws_iot_policy.iot_device_policy.name
  target      = aws_iot_thing.device_1.name
}

resource "aws_iot_policy_attachment" "device_policy_attachment_2" {
  policy_name = aws_iot_policy.iot_device_policy.name
  target      = aws_iot_thing.device_2.name
}

The IoT devices, item registry, rules, and policies will all be created by Terraform on AWS. We can now handle and analyze data from our IoT devices using AWS IoT Core.

Please take note that this sample just shows the bare minimum of an IoT infrastructure architecture. You can expand the configuration for data processing and storage, depending on your IoT use case.

Ensuring Security and Compliance in IoT

In an IoT deployment, security is crucial. Terraform allows us to define security policies, access controls, and encryption settings in our infrastructure code. For instance, we can create AWS IoT policies to restrict device actions, enforce TLS encryption, and manage access using IAM roles.

To ensure compliance, we can integrate Terraform with AWS Config, enabling continuous monitoring of IoT infrastructure against industry standards and regulations. By using Terraform, we maintain a secure and compliant IoT deployment, reducing risks and adhering to best practices. Also, integrating Terraform with security auditing tools and services enables continuous monitoring of infrastructure configurations for compliance with security best practices and regulatory requirements.

Monitoring and Managing IoT with Terraform

Terraform integrates seamlessly with cloud providers' monitoring services, such as AWS CloudWatch or Azure Monitor, enabling us to monitor IoT resources in the cloud along with the alerting system that can be set up based on the conclusions from the monitoring services. Also, deploying monitoring agents on IoT edge devices, orchestrated by Terraform, allows us to collect data locally and analyze it without sending everything to the cloud.

Use Case

Smart Building Automation

A commercial real estate company deployed IoT devices such as smart thermostats, occupancy sensors, and lighting controls to optimize energy consumption and enhance occupant comfort.

To manage the rapidly expanding IoT infrastructure across multiple buildings, they turned to Terraform. They created Terraform modules for each type of IoT device and defined the desired configurations as code. This included specifying temperature setpoints, occupancy thresholds, and lighting schedules. With Terraform, the company automated the provisioning and configuration of IoT devices at scale.

Additionally, terraforms state management allowed the company to track changes and maintain consistency across their IoT fleet.

Moreover, the company integrated Terraform with their existing monitoring and alerting systems. This enabled them to receive real-time insights on energy consumption patterns, occupancy trends, and potential maintenance issues.

By leveraging Terraform for their IoT initiative, the commercial real estate company successfully transformed their buildings into smart, sustainable spaces.

Conclusion

By combining the power of Terraform with cloud platforms, IoT developers and administrators can create flexible, secure, and automated environments to drive innovation and make the most of the Internet of Things.