<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Gary King on Medium]]></title>
        <description><![CDATA[Stories by Gary King on Medium]]></description>
        <link>https://medium.com/@garyking_54824?source=rss-2b29ba6d19ee------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*S1-8giq7Hut_AQnn</url>
            <title>Stories by Gary King on Medium</title>
            <link>https://medium.com/@garyking_54824?source=rss-2b29ba6d19ee------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 21:10:40 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@garyking_54824/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Encrypt Data with AWS KMS]]></title>
            <link>https://medium.com/@garyking_54824/encrypt-data-with-aws-kms-d098887b47df?source=rss-2b29ba6d19ee------2</link>
            <guid isPermaLink="false">https://medium.com/p/d098887b47df</guid>
            <category><![CDATA[key-management-service]]></category>
            <category><![CDATA[dynamodb]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[iam-roles]]></category>
            <dc:creator><![CDATA[Gary King]]></dc:creator>
            <pubDate>Wed, 14 May 2025 14:26:02 GMT</pubDate>
            <atom:updated>2025-05-14T14:26:02.813Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Introducing Today’s Project!</strong></p><p>In this project, I will demonstrate the use of KMS keys to encrypt a database. The goal is to protect the data of the database through the use of granting permission to users for KMS keys.</p><p><strong>Tools and concepts</strong></p><p>Services I used include DynamoDB, IAM and AWS KMS. Key concepts I learnt include encryption, permission access and database creation.</p><p><strong>Project reflection</strong></p><p>This project took me approximately 1.5 hours. It was rewarding to see the power of AWS KMS keys on securing data in a database. I did this project to inmprove my abilities on security in AWS. This was a great project that definitely met my expectations.</p><p><strong>Encryption and KMS</strong></p><p>Encryption is the process of using algorithms to convert data into a secure format called ciphertext. Companies and developers do this to protect your data. Encryption keys are essentailly decoders to get the encrypted cyphertext back to normal.</p><p>AWS Key Management Service (KMS) is a secure vault for your encryption keys. Key management systems are important because it helps you maage all your keys in one place. KMS has the benefit of also giving you logs on every time a key is used.</p><p>Encryption keys are broadly categorized as the algorithm that will decrypt &amp; encrypt your data. I set up a symmetric key because they are generally faster and more efficient for encrypting large amounts of data (and I’m not sharing the key).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/780/1*OdJUm3bchwc5Rfz7lU-z7A.png" /></figure><p>Encrypting Data</p><p>My encryption key will safeguard data in DynamoDB, which is at rest.</p><p>The different encryption options in DynamoDB include Owned by Amazon DynamoDB, AWS managed key and Stored in your account, and owned and managed by you. Their differences are based on ownership &amp; management of the keys.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*m1ovhC9Sy6hhu_22Z7fGGA.png" /></figure><p><strong>Data Visibility</strong></p><p>Rather than controlling who has access to the key, KMS manages user permissions by who has been granted the permission to use the key.</p><p>Despite encrypting my DynamoDB table, I could still see the table’s items because my IAM user has permissions to use the encryption key in KMS. DynamoDB uses transparent data encryption, which means an authorized user will see it in a decrypted format.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/672/1*PIbe_4ytbjXSfEpJgVhH4g.png" /></figure><p><strong>Denying Access</strong></p><p>I configured a new IAM user to verify our encryption using KMS is working correctly. The permission policies I granted this user are full access to DynamoDB, but not to my KMS key.</p><p>After accessing the DynamoDB table as the test user, I encountered an ‘Access Denied’ error because this user does not have KMS permissions and cannot decrypt the data in my DynamoDB table. This confirmed my KMS key is working how it should.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/841/1*dN1vPWehs_V33s6O0gq6hQ.png" /></figure><p>Granting Access</p><p>To let my test user use the encryption key, I granted the user permission to use the KMS key. My key’s policy was updated to allow the new user permission to use it as seen in the code.</p><p>Using the test user, I retried accessing the DynamoDB table. I observed that the operation was completed this time which confirmed that adding the permission to use the KMS key has worked.</p><p>Encryption secures data instead of access to a resource (e.g. a DynamoDB table) or an entire service (e.g. DynamoDB). I could combine encryption with the afore mentioned measures to further limit access and keep our data &amp; resources secure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/415/1*YBAD5-oJgSzhGLbU6iS7XQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d098887b47df" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Create S3 Buckets with Terraform]]></title>
            <link>https://medium.com/@garyking_54824/create-s3-buckets-with-terraform-85dc3a157c69?source=rss-2b29ba6d19ee------2</link>
            <guid isPermaLink="false">https://medium.com/p/85dc3a157c69</guid>
            <category><![CDATA[s3]]></category>
            <category><![CDATA[cli]]></category>
            <category><![CDATA[terraform]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Gary King]]></dc:creator>
            <pubDate>Wed, 14 May 2025 14:17:42 GMT</pubDate>
            <atom:updated>2025-05-14T14:17:42.053Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Introducing Today’s Project!</strong></p><p>In this project, I will demomstrate using Terraform to deploy infrastructure in AWS. The goal is to configure my AWS credentials in the terminal and create and manage S3 buckets with Terraform. Finally, I will upload files to S3 using Terraform.</p><p><strong>Tools and concepts Services I used were:</strong></p><p>Terraform Amazon S3 AWS CLI AWS IAM</p><p><strong>Project reflection</strong></p><p>The project took me approximately 1.5 hours. The most challenging part was setting up Terraform for the first time. It was most rewarding to use Terraform to launch resources in AWS using the AWS CLI. It truly showcased the power of Terraform and illustrated its use cases. I completed the project today to improve my Terrafrom knowledge and learn more about Infrastructure as code (IaC). This project definitely met my goals and has given me a solid base to continue my exploring and learning of Terraform.</p><p><strong>Introducing Terraform</strong></p><p>Terraform is a tool that helps you build and manage your cloud infrastructure using code. Instead of setting up resources manually in the AWS console or CLI, you write a script that tells Terraform exactly what you want in your cloud infrastructure, like servers, databases, and networks. Terraform then automatically builds all of this for you, using your script as a blueprint.</p><p>Infrastructure as Code (IaC) is a way to manage your IT infrastructure. Instead of manually setting up your resources e.g. creating resources one by one in the Console, you’re writing configuration files in code. Things built from code are built the same way every time. You can repair and rebuild things quickly, and other people can build identical instances of the same thing. This makes managing large-scale systems more efficient, less error-prone, and way faster than doing everything manually. Terraform is a top IaC tool because it supports multiple cloud providers, so you can set up multi-cloud infrastructures that use AWS, Azure, GCP and more. It also uses a simple configuration language.</p><p>Terraform uses configuration files to define and manage infrastructure. These files describe the desired state of your infrastructure, and Terraform figures out how to achieve that state.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/713/1*7YKIeYp9JixpeBv06_mbQQ.png" /></figure><p><strong>Configuration files</strong></p><p>The configuration is structured in blocks to help organize the code better. The style of organizing code into individual blocks is called modularity. Each block handles a specific piece of your setup, like a resource or a configuration, which makes it easier to read, manage, and adjust things separately without affecting the rest of your infrastructure. These are the basic building blocks of any Terraform configuration: Provider blocks specify which plugins (like AWS, Google Cloud, or Azure) Terraform uses to deploy and manage resources in those services. Resource blocks define what resources to manage, such as networks, virtual machines, or storage buckets. Each resource is individually managed and can be customized with parameters defined by the provider.</p><p><strong>My main.tf configuration has three blocks</strong></p><p>The first block indicates the provider “aws”: Indicates that AWS is the provider. A provider is a plugin (a software add-on) that allows Terraform to interact with a specific cloud service, API, or on-premises resource. The provider translates your configurations into API calls that manage your infrastructure. The second block provisions the resource “aws_s3_bucket” “my_bucket”: This block provisions an S3 bucket. “my_bucket” is an internal alias used in your code to reference this resource. The third block manages the resource “aws_s3_bucket_public_access_block” “my_bucket_public_access_block”: Manages public access policies for the S3 bucket. In our case, options like block_public_acls, ignore_public_acls, block_public_policy, and restrict_public_buckets, are all set to true to stop public access to your bucket and its contents.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/991/1*UwdNQPAA-wS-2bZ2PVEYAw.png" /></figure><p><strong>Customizing my S3 Bucket</strong></p><p>For my project extension, I visited the official Terraform documentation to read documentation on the aws provider, where we can find setup instructions, descriptions of each available resource, best practice tips and examples, and parameters for customization. The aws_s3_bucket in the Terraform documentation is all about how to use Terraform to create and manage AWS S3 buckets. It covers how to configure these buckets, set their properties, and manage interactions with other AWS services.</p><p>I chose to customize my bucket by adding tags because I wanted to be able to differentiate if this file was for a development environment or production environment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/815/1*ZpRIim2coH4AH_ISY80NYg.png" /></figure><p><strong>Terraform commands</strong></p><p>I ran ‘terraform init’ to Terraform init is the first command you run for a new Terraform project. It sets up your project by: Downloading necessary plugins: It grabs the specific providers Terraform needs to manage your cloud services, like AWS. Setting up the backend: Prepares where Terraform will store its record of your setup, so it knows what your cloud setup looks like and can manage it efficiently. Preparing modules: If your setup uses reusable code components, called modules, this is where the code is downloaded from their source to replace placeholders in your code. Creating a lock file: This file keeps track of the versions of everything Terraform is using, making sure that everyone on your team is using the same setup to avoid inconsistencies.</p><p>Next, I ran ‘terraform plan’ to create an execution plan, showing you what changes Terraform will make to my infrastructure based on my configuration file. It shows what will be created, updated, or destroyed so we can review and confirm the configuration before any real changes are made.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/824/1*F6IA-92dEF56nyamJBAkBA.png" /></figure><p><strong>AWS CLI and Access Keys</strong></p><p>When I tried to plan my Terraform configuration, I received an error message that says ‘Planning Failed’ because I did not have AWS CLI installed.</p><p>To resolve my error, first I installed AWS CLI, which is The AWS CLI (Command Line Interface). This is a powerful tool that lets you manage your AWS services from your terminal. Instead of having to use the AWS Management Console, you can now run text commands from your local machine.</p><p>I set up AWS access keys to connect the CLI to the management console as the CLI needs another way of authenticating you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/996/1*bZgd1hEGGkl1Bo2I8Lpx4g.png" /></figure><p><strong>Lanching the S3 Bucket</strong></p><p>I ran ‘terraform apply’ to apply the changes I’d written in my Terraform configuration. It creates, modifies, or deletes resources in your infrastructure based on your code. In my case, this command creates the S3 bucket in my AWS account.</p><p>If you run terraform apply before terraform init, you would run into an error because terraform init needs to set up your project first by downloading necessary plugins and setting up the state file, which is a file Terraform uses to track the current state of your infrastructure. There actually aren’t any errors if you skip terraform plan. This is because terraform apply will automatically run a plan and ask for confirmation before making any changes. But, skipping the explicit terraform plan means you might miss reviewing these changes in detail. It’s best practice to run a plan to catch any potential errors or unexpected results before they affect your live infrastructure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HUCTFG8ivShieWxdhBpIrw.png" /></figure><p><strong>Uploading an S3 Object</strong></p><p>I created a new resource block to add an image to my S3 bucket using Terraform.</p><p>We need to run terraform apply again because you need to run terraform apply anytime you change your Terraform configuration. This will make sure the changes are correctly applied to your infrastructure.</p><p>To validate that I’ve updated my configuration successfully, I logged back into my management console and into my S3 bucket. I then was able to see my image.png which I downloaded and opened to verify it worked — which it did!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/823/1*1sserfPmPU7bekeW6Zy4hw.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=85dc3a157c69" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Launch a Kubernetes Cluster]]></title>
            <link>https://medium.com/@garyking_54824/launch-a-kubernetes-cluster-a18bd1e92509?source=rss-2b29ba6d19ee------2</link>
            <guid isPermaLink="false">https://medium.com/p/a18bd1e92509</guid>
            <category><![CDATA[kubernetes-cluster]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[iam-roles]]></category>
            <dc:creator><![CDATA[Gary King]]></dc:creator>
            <pubDate>Wed, 14 May 2025 14:06:46 GMT</pubDate>
            <atom:updated>2025-05-14T14:06:46.290Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Introducing Today’s Project!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6a_dk34aBxx7KNkxvaPsdw.png" /></figure><p>In this project, I will launch a Kubernetes cluster, track how AWS creates it and access EKS from the management console.</p><p><strong>What is Amazon EKS?</strong></p><p>Amazon EKS is is a managed service provided by AWS that simplifies deployment, management and scaling of containerized applications using Kubernetes. I used it in today’s project to manage my kubernetes cluster.</p><p><strong>What is Kubernetes?</strong></p><p>Kubernetes is a container orchestration platform, which is a fancy way to say that it coordinates containers so they’re running smoothly across all your servers. It makes sure all your containers are running where they should, scales containers automatically to meet demand levels, and even restarts containers if something crashes. Without a tool like Kubernetes, you would create and manage every container manually. Youʼd have to start each container yourself and keep an eye on them to restart any that crash. Traffic to your app going up or down would mean turning containers on or off one by one, and youʼd also have to make sure each container has access to storage if it needs it. Updating your app would mean carefully swapping out containers without causing downtime. As you might imagine, managing hundreds or thousands of containers this way would be a huge<br>amount of work and hard to get right all the time. Kubernetes takes care of all these tasks automatically.</p><p>I used eksctl to: — Set up an EKS cluster named nextwork-eks-cluster — Launch a node group called nextwork-nodegroup. — Use t2.micro EC2 instances as nodes. — Start my node group with 3 nodes and automatically scale between 1 (minimum) and 3 nodes (maximum) based on demand. — Use Kubernetes version 1.31 for the cluster setup.</p><p>I initially ran into two errors while using eksctl. The first one was because eksctl was not installed. The second one was because I had not set up an IAM role for my EC2 instance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s_TUJByI_-jNpynXTHM0pQ.png" /></figure><p><strong>eksctl and CloudFormation</strong></p><p>CloudFormation helped create my EKS cluster because eksctl uses CloudFormation to build the cluster; along with all of the necessary resources such as VPC, subnets, route tables, security groups, NAT gateways and internet gateways!</p><p>The second stack is specifically for my node group, which is a group of EC2 instances that will run my containers. CloudFormation separates the core EKS cluster stack from the node group stack to make it easier to manage and troubleshoot each part independently, especially if one half fails.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*3xYH8x8zNVC-ylaPTXTNMA.png" /></figure><p><strong>The EKS console</strong></p><p>I had to create an IAM access entry in order to connect AWS IAM users with Kubernetesʼ Role-Based Access Control (RBAC), which is Kubernetes’ system to manage access inside a cluster. In short, my IAM Admin user needs a specific access entry to get access to the nodes in my EKS cluster.</p><p>It took approximately 15 minutes to create my cluster. Since I’ll create this cluster again in the next project of this series, maybe this process could be sped up if I keep my IAM user’s access and settings.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6oKl2i9yJ1Af1QK33usDyw.png" /></figure><p><strong>Deleting nodes</strong></p><p>Nodes can be found in the EKS cluster’s nodes in Amazon EC2 because nodes are a generic term used for virtual machines, in AWS’ case, they are called EC2 instances.</p><p>Desired size is the number of nodes you want running in your group. Minimum and maximum sizes are helpful for setting parameters for your app; setting the minimum number of nodes to keep your app running at all times and the maximum to allow EKS to scale up in high demand periods.</p><p>When I deleted my EC2 instances, more EC2 instances were created in their place. This is because we have set the desired amounts to minimum of 1 node, and maximum of 3.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/907/1*ghy1d30QHTDvIR2XAaAPAA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a18bd1e92509" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Host a Website on Amazon S3]]></title>
            <link>https://medium.com/@garyking_54824/host-a-website-on-amazon-s3-1c3300a505b5?source=rss-2b29ba6d19ee------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c3300a505b5</guid>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[s3]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Gary King]]></dc:creator>
            <pubDate>Sat, 15 Mar 2025 12:20:20 GMT</pubDate>
            <atom:updated>2025-03-15T12:20:20.199Z</atom:updated>
            <content:encoded><![CDATA[<p>Introducing today’s project!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/546/1*ps3j5jpq6OkhrOcYQ6CikA.png" /></figure><p><strong>What is Amazon S3</strong></p><p>S3 is a cloud storage service where you can store and retrieve virtually any amount of data. It is scalable, durable, versatile, cost-effective &amp; secure.</p><p><strong>How I used Amazon S3 in this project</strong></p><p>I used S3 in my project to store all my files for hosting my static website.</p><p><strong>How I Set Up an S3 Bucket</strong></p><p>Creating an S3 bucket took me 2 minutes!</p><p>The Region I picked for my S3 bucket was London because I am in London. This aids in two aspects; it improves latency and minimizes cost.</p><p>Bucket names are globally unique! This means that there can never be another S3 bucket with the same name as yours.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_RY5kVyxc-P7chdGlrzQGQ.png" /></figure><p><strong>Upload Website Files to S3</strong></p><p>index.html and image assets</p><p>I uploaded two files to my S3 bucket — they were an index.html file and a folder called NextWork.</p><p>The index.html file is used to create design web pages; it is essentially instructions (blueprint) to tell my website where to display the images etc. The folder I uploaded contains all the content for the website itself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dO_rdkTdsYfJMFathtYCIA.png" /></figure><p><strong>Static Website Hosting on S3</strong></p><p>Website hosting simply means making your website visible to the public; it means storing your HTML file (and the other files for your website) on a webserver, so it’s accessible online.</p><p>To enable website hosting with my S3 bucket, I edited the properties of my S3bucket to enable the hosting of static websites.</p><p><strong>Access Control Lists (ACL)</strong></p><p>An ACL is a set of rules that decides who can get access to a resource. Enabling ACLs in this S3 setup lets me control who can access and do things with the objects (i.e. website files) I uploaded into my bucket.</p><p><strong>Bucket Endpoints</strong></p><p>Once static website is enabled, S3 produces a bucket endpoint URL, which is a URL to get to the static website.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/823/1*qNzAUShx5aOEOAE4SBhZJg.png" /></figure><p>An error!</p><p>When I first visited the bucket endpoint URL, I saw a 403 Forbidden error message.</p><p>The reason for this error is we are being informed that the static website is being hosted on S3 but the content is still private.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*J0jjmll97UV156G1LwKg7g.png" /></figure><p>Success!</p><p>To resolve this connection error, I had to granted public access to my objects using an ACL.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/815/1*urAGnA5F4CVXeL81yTpPgA.png" /></figure><p>Thanks for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c3300a505b5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Visual Data with Amazon QuickSight]]></title>
            <link>https://medium.com/@garyking_54824/visual-data-with-amazon-quicksight-d8038d773378?source=rss-2b29ba6d19ee------2</link>
            <guid isPermaLink="false">https://medium.com/p/d8038d773378</guid>
            <category><![CDATA[s3]]></category>
            <category><![CDATA[amazon-quicksight]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Gary King]]></dc:creator>
            <pubDate>Sat, 15 Mar 2025 11:41:40 GMT</pubDate>
            <atom:updated>2025-03-15T11:59:38.324Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Introducing today’s project!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/532/1*TyKsKCcgu5DagBbKzfsT7g.png" /></figure><p><strong>What is Amazon QuickSight?</strong></p><p>Amazon QuickSight is a visualisation tool that can provide visual insights to data. It is useful as it can ingest large data sets and illustrate this information in simple and diverse charts &amp; graphs.</p><p><strong>How I used Amazon QuickSight in this project.</strong></p><p>I used Amazon QuickSight in today’s project to visualize a large set of Netflix data to get useful insights.</p><p><strong>Upload project files into S3</strong></p><p>S3 is used in this project to store two files, which were Netflix dataset and manifest.json file.<br>I edited the manifest.json file by updating the S3 URI of my dataset. It’s important to edit this file because keeping an outdated S3 URI means that manifest.json would be directing to the wrong address.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JXqQThDjnsyTg4VPNmGErw.png" /></figure><p><strong>Create QuickSight account</strong></p><p>It is free to create a QuickSight account (the free trail lasts for 30 days).</p><p>It took less then 5 minutes to setup and wait for account creation. I also had to enable QuickSight’s access to S3 because my dataset is stored in an S3 bucket- and specific access to that bucket is required for QuickSight to process that data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UdrTynMG7PRjsGpGWTtpig.png" /></figure><p><strong>Download the Dataset</strong></p><p>I connected the S3 bucket to QuickSight by visiting the S3 bucket and importing the S3 URI into QuickSight.</p><p>The manifest.json file was important in this step because manifest.json tells QuickSight what your dataset looks like, so QuickSight knows how to understand the data and show it in charts or graphs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/603/1*MXLyfWC9iGEkbNedSzUBhQ.png" /></figure><p><strong>My first visualization</strong></p><p>To create visualizations on QuickSight, I linked the data from my S3 bucket, imported it into QuickSight and then started to create my visualizations in QuickSight. We can have different visuals by manipulating the data in QuickSight.</p><p>The chart shown here is a breakdown of the top 20 records released by year. We can see the largest number of releases occurring in 2018. We can also see the dip in 2019–2021 which was impacted by COVID.</p><p>I created this graph by dragging and dropping the release_year label into the Y-axis heading and the type label into the Group/Colour heading.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/482/1*2BlEGYaXsGBhL840m5_0UA.png" /></figure><p><strong>Using filters</strong></p><p>Filters are useful for manipulating the data to show useful insights. Through the use of filters we can slice and dice the data to show various different scenarios to allows informed decisions to be made.</p><p>This visualization is a breakdown of the date with the most records added(January 1st 2020), the number of records across three genres and finally those genres within a specified date range (2015–2021).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/727/1*JdVc_BCS0Idrmg7zjQVFCA.png" /></figure><p><strong>Setting up a dashboard</strong></p><p>As a finishing touch, I adjusted all the charts so the dashboard is visually pleasing. I also added title to each chart so they are easily understandable to anyone that viewed the dashboard.</p><p>Did you know you could export your dashboard as PDFs too? I did this by publishing the dashboard and then navigating to the export button in the top right hand side of the page and selecting export as pdf.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B2RUsQyBSCgkOS1j9r3yjA.png" /></figure><p>Thanks for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d8038d773378" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>