AWS Quick Sight Analytical Reports with Date Range

VIJAYaraaghavan Manoharan — Sun, 23 Jul 2023 10:17:10 GMT

Introduction

AWS QuickSight helps to develop analytical reports faster with great visuals for business by plugging in the data source. Here, will focus on the developing AWS QuickSight Report with Date Range Filter for users.

Development Steps

QuickSight Report development involves the below process:

Creation of DataSet with data source configuration.
Creation of analysis (report) using predefined visual available in AWS QuickSight for the DataSet created earlier.
Publish the report as Dashboard.
Share the Dashboard with users for access.

Here, our goal is to add DateRange Filter in the report visual by allowing users to select the Date Range.

For this development, used the dataset from https://www.kaggle.com/datasets/muthuj7/weather-dataset

Steps are:

Create New Dataset by importing the dataset in S3. Here, I named it as daterange-dataset Screenshots from POC:

Sample manifest file for reference Weather Report Manifest File

Create New Analysis with the dataset created now.

Now add Filter mapping with Start Date and End Date.

Now add Parameter mapping to Filter.

Publish it as Dashboard

Conclusion

With Date-Range Filter, AWS QuickSight report helps the users to analyze the data on specific date or date-range.

Create Terraform Scripts for an Existing Infrastructure

VIJAYaraaghavan Manoharan — Wed, 15 Feb 2023 04:22:18 GMT

Introduction

This blog explains the solution approach and steps to create Terraform Scripts for an Existing Infrastructure. Here, AWS will be used for that infrastructure.

Solution Design

Implementation Steps

As a first step, need to identify the list of resources that already exists in the AWS infrastructure. These resources might have created manually To identify the already created (could be manually using console) resources in AWS, the below-listed approach will help.
- Approach 1: Using AWS Console Tag Editor search, can identify the list resources created by resource type.
- Approach 2: Using AWS CLI command (Example : aws configservice list-discovered-resources --resource-type AWS::EC2::VPC ), can list down the resource list and its ids. Here, refer https://docs.aws.amazon.com/cli/latest/reference/configservice/list-discovered-resources.html#options
Create terraform script. Example:

terraform {
  required_providers {
    aws = {
        source = "hashicorp/aws"
        version = ">= 0.15.0"
    }
  }
}

provider "aws" {
  profile = "default"
  region = "us-west-2"
}

Run command terraform init to initialize the terraform and make sure the terraform connectivity with the infrastructure.
Update terraform resource with resource name. Refer: Terraform documentation for the exact resource name and mandatory parameter configuration for import functionality.

resource "aws_vpc" "test_vpc" {
  cidr_block = "10.0.0.0/16"
}

Here, cidr_block is mandatory. So added this parameter alone

Import the resource from existing infrastructure using the import command with the exact resource id noted in first step. Example terraform import aws_vpc.test_vpc vpc-0841e2b7a945624b6.
Once imported, use the command terraform show to show the exact resource details to update back in terraform script.
then, run terraform validate and cleanup all the error need to be fixed. Mostly the id attributes need to be removed which was copied from show command.
Now, after all the errors fixed, can run command terranform plan which should result No changes. Infrastructure is up-to-date.. This confirms terraform scripts and AWS infrastructure matches no need changes. Moving, forward can start making changes in terraform script and push it to AWS environment.

VIJAYaraagahvan Manoharan Blog

AWS Quick Sight Analytical Reports with Date Range

Introduction

Development Steps

Conclusion

Create Terraform Scripts for an Existing Infrastructure

Introduction

Solution Design

Implementation Steps