<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:media="http://search.yahoo.com/mrss/"><channel><title>AWS on KGOL-Blog</title><link>https://blog.kgol.xyz/en/tags/aws/</link><description>Recent content in AWS on KGOL-Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>©2025, All Rights Reserved</copyright><lastBuildDate>Sat, 16 Apr 2022 17:00:00 +1100</lastBuildDate><atom:link href="https://blog.kgol.xyz/en/tags/aws/index.xml" rel="self" type="application/rss+xml"/><item><title>Terraform Module - Security Hub Summarizer</title><link>https://blog.kgol.xyz/en/posts/tf-module-sechub-summarizer/</link><pubDate>Sat, 16 Apr 2022 17:00:00 +1100</pubDate><atom:modified>Sat, 16 Apr 2022 17:00:00 +1100</atom:modified><guid>https://blog.kgol.xyz/en/posts/tf-module-sechub-summarizer/</guid><description>This module can be found on Github and Terraform Registry
Background AWS Security Hub is a pretty useful tool for discovering potential vulnerabilities in your infrastructure.
Recently I was deploying a landing zone through Terraform that included Security Hub and came across an issue regarding how Security Hub notifies the discovery of a new vulnerability.
The current practice is to have an Eventbridge Rule that looks for Security Hub finding events and triggers an SNS.</description><dc:creator>Kieran Goldsworthy</dc:creator><media:content url="https://blog.kgol.xyz/img/TF%20Module%20-%20Sechub%20Summarizer.drawio.png" medium="image"><media:title type="html">featured image</media:title></media:content><category>AWS</category><category>Terraform</category><category>Security</category><category>Garden Shed</category></item><item><title>Terraform Module - Container Insights</title><link>https://blog.kgol.xyz/en/posts/tf-module-container-inisights/</link><pubDate>Sat, 16 Apr 2022 16:00:00 +1100</pubDate><atom:modified>Sat, 16 Apr 2022 16:00:00 +1100</atom:modified><guid>https://blog.kgol.xyz/en/posts/tf-module-container-inisights/</guid><description>This module can be found on Github and Terraform Registry
The Container Insights Terraform Module is used to deploy AWS&amp;rsquo; Container Insights agent onto a Kubernetes Cluster (EKS Specifically).
This allows for enabling deeper visibility into the operations of your K8 cluster via metrics and logs sent to AWS CloudWatch.
The module connects to the Kubernetes cluster via the management endpoint to run a custom-written Helm Chart.
This helm chart deploys the Container Insights Agent to the cluster as a DeamonSet and configures it to use IAM roles for service accounts, with an IAM Role this module also creates.</description><dc:creator>Kieran Goldsworthy</dc:creator><media:content url="https://blog.kgol.xyz/img/TF%20Module%20-%20Container%20Insights.drawio.png" medium="image"><media:title type="html">featured image</media:title></media:content><category>AWS</category><category>Terraform</category><category>Observability</category><category>Garden Shed</category></item><item><title>Terraform Module - Transit Gateway Route Table</title><link>https://blog.kgol.xyz/en/posts/tf-module-tgw-routetable/</link><pubDate>Sat, 16 Apr 2022 15:00:00 +1100</pubDate><atom:modified>Sat, 16 Apr 2022 15:00:00 +1100</atom:modified><guid>https://blog.kgol.xyz/en/posts/tf-module-tgw-routetable/</guid><description>This module can be found on Github and Terraform Registry
This module creates an AWS Route Table for Transit Gateway, and its associations and propagations.
It is designed to be used in collaboration with the official TGW module by AWS [Github, TF Registry].
While the official TGW module does include some route table functionality, the advantage of this module is better support for cross-account attachments and easier implementation of multiple route tables for the same TGW, thus being able to implement multiple routing domains (More details here).</description><dc:creator>Kieran Goldsworthy</dc:creator><media:content url="https://blog.kgol.xyz/img/TF%20Module%20-%20TGW%20RT.drawio.png" medium="image"><media:title type="html">featured image</media:title></media:content><category>AWS</category><category>Terraform</category><category>Networking</category><category>Garden Shed</category></item><item><title>Multiple TGW Route Tables</title><link>https://blog.kgol.xyz/en/posts/tgw-routing-domains/</link><pubDate>Wed, 30 Mar 2022 00:00:00 +0000</pubDate><atom:modified>Wed, 30 Mar 2022 00:00:00 +0000</atom:modified><guid>https://blog.kgol.xyz/en/posts/tgw-routing-domains/</guid><description>A more advanced routing architecture for AWS VPCs.
TLDR: TGW can route traffic based on the source VPC as well as the destination IP.
Before AWS introduced Transit Gateway, the only way to connect VPCs together was to use VPC peering. The main issue with this approach is that you need a VPC Peering between each pair of VPCs that you want to connect.
To simplify large multi-VPC environments AWS released Transit Gateway, this allows for a hub-and-spoke model which allows for multiple VPCs to talk to each other with only a connection to a single hub.</description><dc:creator>Kieran Goldsworthy</dc:creator><media:content url="https://blog.kgol.xyz/img/lots-of-road-signs.png" medium="image"><media:title type="html">featured image</media:title></media:content><category>AWS</category><category>Networking</category><category>Man Pages</category></item><item><title>Account Factory for Terraform (AFT) Thoughts</title><link>https://blog.kgol.xyz/en/posts/atf-thoughts/</link><pubDate>Sun, 20 Feb 2022 00:00:00 +0000</pubDate><atom:modified>Sun, 20 Feb 2022 00:00:00 +0000</atom:modified><guid>https://blog.kgol.xyz/en/posts/atf-thoughts/</guid><description>I&amp;rsquo;ve worked with AWS and Terraform for 3-4 years at this point and when AWS initially announced the Account Factory for Terraform (AFT) I didn&amp;rsquo;t take a too closer look because the company I worked for already had a solution to account generation that we would not be changing very soon (for many reasons).
After I moved jobs I worked for a company that wanted to build AWS via terraform and were considering the account provisioning process, including using AFT.</description><dc:creator>Kieran Goldsworthy</dc:creator><media:content url="https://blog.kgol.xyz/img/AFT.png" medium="image"><media:title type="html">featured image</media:title></media:content><category>AWS</category><category>Terraform</category><category>Interesting Bits</category></item><item><title>S3 Idea</title><link>https://blog.kgol.xyz/en/posts/s3-idea/</link><pubDate>Fri, 14 Jan 2022 00:00:00 +0000</pubDate><atom:modified>Fri, 14 Jan 2022 00:00:00 +0000</atom:modified><guid>https://blog.kgol.xyz/en/posts/s3-idea/</guid><description>Making the world a better place, one bucket at a time.
S3 takes from a global namespace (actually, it&amp;rsquo;s the ARN that needs to be globally unique), which means anyone can create a bucket with any name (subject to a format) as long as that name has not been used by someone else.
This actually creates a problem.
Given the global namespace, short simple bucket names are already taken. For example, a bucket used to store logs can&amp;rsquo;t be called logs because someone else certainly already has it.</description><dc:creator>Kieran Goldsworthy</dc:creator><media:content url="https://blog.kgol.xyz/img/S3Evolution.png" medium="image"><media:title type="html">featured image</media:title></media:content><category>AWS</category><category>Security</category><category>Interesting Bits</category></item><item><title>AWS in China</title><link>https://blog.kgol.xyz/en/posts/aws-in-china/</link><pubDate>Wed, 12 Jan 2022 00:00:00 +0000</pubDate><atom:modified>Wed, 12 Jan 2022 00:00:00 +0000</atom:modified><guid>https://blog.kgol.xyz/en/posts/aws-in-china/</guid><description>AWS has a &amp;lsquo;partition&amp;rsquo; in Mainland China.
It&amp;rsquo;s not like building in normal AWS, some services/features are missing or work in odd ways.
Partitions AWS has a concept of &amp;lsquo;partitions&amp;rsquo;, these are basically separate instances of the AWS Cloud.
You may have heard this term before when it comes to the different parts of the ARN e.g.&amp;ldquo;arn:partition:service:region:account-id:resource-id&amp;rdquo;
There are currently 3 partitions:
aws The normal aws cloud aws-us-gov AKA GovCloud aws-cn Mainland China These different partitions have limited overlap and connectivity.</description><dc:creator>Kieran Goldsworthy</dc:creator><media:content url="https://blog.kgol.xyz/img/RedCloud.png" medium="image"><media:title type="html">featured image</media:title></media:content><category>AWS</category><category>Networking</category><category>Interesting Bits</category></item><item><title>Terragrunt Default Tags</title><link>https://blog.kgol.xyz/en/posts/terragrunt-default-tags/</link><pubDate>Sat, 21 Aug 2021 00:00:00 +0000</pubDate><atom:modified>Sat, 21 Aug 2021 00:00:00 +0000</atom:modified><guid>https://blog.kgol.xyz/en/posts/terragrunt-default-tags/</guid><description>An approach to adding tags to all resources deployed by terragrunt
This page describes a method to adding a set of default tags to all resources that can be tagged in an AWS account (other terraform providers may be compatible)
More specifically, all resources deployed by terraform / terragrunt in a git repository.
Setup First I should mention how I have set up the various terragrunt and terraform code, modules and repositories.</description><dc:creator>Kieran Goldsworthy</dc:creator><media:content url="https://blog.kgol.xyz/img/tags.jpg" medium="image"><media:title type="html">featured image</media:title></media:content><category>AWS</category><category>Terraform</category><category>Terragrunt</category><category>Man Pages</category></item><item><title>AWS Resource Policies</title><link>https://blog.kgol.xyz/en/posts/aws-resource-policies/</link><pubDate>Sun, 27 Sep 2020 00:00:00 +0000</pubDate><atom:modified>Sun, 27 Sep 2020 00:00:00 +0000</atom:modified><guid>https://blog.kgol.xyz/en/posts/aws-resource-policies/</guid><description>The other side of AWS IAM Permissions
IAM Policies This article will not be an in-depth look at IAM Policies, but it&amp;rsquo;s a good idea to go over the general basics.
An IAM Policy is in the form of a JSON Object with the most important part being the statements.
Each Policy Statement defines a set of actions, whether the action should be explicitly Allowed or Denied, and under which conditions the statement should apply.</description><dc:creator>Kieran Goldsworthy</dc:creator><media:content url="https://blog.kgol.xyz/img/aws_iam.jpg" medium="image"><media:title type="html">featured image</media:title></media:content><category>AWS</category><category>IAM</category><category>Security</category><category>Man Pages</category></item><item><title>What the heck are Permission Boundaries?</title><link>https://blog.kgol.xyz/en/posts/aws-iam-permissions-boundaries/</link><pubDate>Sat, 26 Sep 2020 00:00:00 +0000</pubDate><atom:modified>Sat, 26 Sep 2020 00:00:00 +0000</atom:modified><guid>https://blog.kgol.xyz/en/posts/aws-iam-permissions-boundaries/</guid><description>How to use this lesser known feature of AWS IAM
A competent understanding of IAM Polices and how they affect the permissions of any User/Role they are attached to is important to understand Permission Boundaries.
Introducing Permissions Boundaries Boundaries are applied to Users and Roles and they act as the upper-limit (like a Boundary&amp;hellip; funny that) to the User/Role, regardless of what might be granted by the attached IAM Policies.</description><dc:creator>Kieran Goldsworthy</dc:creator><media:content url="https://blog.kgol.xyz/img/boundary_fence.webp" medium="image"><media:title type="html">featured image</media:title></media:content><category>AWS</category><category>IAM</category><category>Security</category><category>Man Pages</category></item><item><title>Installing and Configuring Confluence Data Center on AWS</title><link>https://blog.kgol.xyz/en/posts/installing-and-configuring-confluence-data-center-on-aws/</link><pubDate>Sun, 16 Feb 2020 00:00:00 +0000</pubDate><atom:modified>Sun, 16 Feb 2020 00:00:00 +0000</atom:modified><guid>https://blog.kgol.xyz/en/posts/installing-and-configuring-confluence-data-center-on-aws/</guid><description>Or at least how I did it
Disclaimer This is my experience and steps I performed, YMMV.
Some of these steps might not be required for your environment and some other steps might be.
Some of the values might be different for you, where I think that might be the case they will appear as variables like so: ${VARIABLE}.
This guide is to help you, not tell you want to do, so I take no responsibility if you screw up.</description><dc:creator>Kieran Goldsworthy</dc:creator><media:content url="https://blog.kgol.xyz/img/confluence.jpg" medium="image"><media:title type="html">featured image</media:title></media:content><category>Atlassian</category><category>Confluence</category><category>AWS</category><category>Java</category><category>Man Pages</category></item><item><title>Installing and Configuring Jira Data Center on AWS</title><link>https://blog.kgol.xyz/en/posts/installing-and-configuring-jira-data-center-on-aws/</link><pubDate>Sun, 16 Feb 2020 00:00:00 +0000</pubDate><atom:modified>Sun, 16 Feb 2020 00:00:00 +0000</atom:modified><guid>https://blog.kgol.xyz/en/posts/installing-and-configuring-jira-data-center-on-aws/</guid><description>Or at least how I did it
Disclaimer This is my experience and steps I performed, YMMV.
Some of these steps might not be required for your environment and some other steps might be.
Some of the values might be different for you, where I think that might be the case they will appear as variables like so: ${VARIABLE}.
This guide is to help you, not tell you want to do, so I take no responsibility if you screw up.</description><dc:creator>Kieran Goldsworthy</dc:creator><media:content url="https://blog.kgol.xyz/img/jira.jpg" medium="image"><media:title type="html">featured image</media:title></media:content><category>Atlassian</category><category>Jira</category><category>AWS</category><category>Java</category><category>Man Pages</category></item><item><title>Interesting Bits #1</title><link>https://blog.kgol.xyz/en/posts/interesting-bits-1/</link><pubDate>Wed, 22 May 2019 18:47:28 +1000</pubDate><atom:modified>Wed, 22 May 2019 18:47:28 +1000</atom:modified><guid>https://blog.kgol.xyz/en/posts/interesting-bits-1/</guid><description>Misspelled characters, Unexpected AWS achievements
1 One of my favourite characters is the lowercase Greek letter &amp;lsquo;L&amp;rsquo; called &amp;rsquo;lambda&amp;rsquo;. I don&amp;rsquo;t know why I like it, perhaps it was after I played Half-Life; or perhaps it was when it was used for eigenvalue when I was learning linear algebra.
Either way, I do use the symbol every now and then. But alas there is no \(\lambda\) symbol on the keyboard, hence to use it I would need to copy it from either the web or from a built in feature of Microsoft Windows called &amp;lsquo;Character Map&amp;rsquo;.</description><dc:creator>Kieran Goldsworthy</dc:creator><media:content url="https://blog.kgol.xyz/img/post2.webp" medium="image"><media:title type="html">featured image</media:title></media:content><category>Windows</category><category>AWS</category><category>Cloudformation</category><category>Interesting Bits</category></item></channel></rss>