<?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>Man Pages on KGOL-Blog</title><link>https://blog.kgol.xyz/en/series/man-pages/</link><description>Recent content in Man Pages on KGOL-Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>©2025, All Rights Reserved</copyright><lastBuildDate>Fri, 29 Jul 2022 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.kgol.xyz/en/series/man-pages/index.xml" rel="self" type="application/rss+xml"/><item><title>Get 'results' from GCP Cloud Build</title><link>https://blog.kgol.xyz/en/posts/gcp-cloudbuild-results/</link><pubDate>Fri, 29 Jul 2022 00:00:00 +0000</pubDate><atom:modified>Fri, 29 Jul 2022 00:00:00 +0000</atom:modified><guid>https://blog.kgol.xyz/en/posts/gcp-cloudbuild-results/</guid><description>Pass results directly from a Cloud Build pipeline without storing/retrieving an artifact
Background The typical pattern for using a CI/CD pipeline is to provide some input (like a git repo), and the pipeline will perform a combination of commands such as API calls or software compilations.
By the end, the pipeline may produce some &amp;lsquo;artifact&amp;rsquo;. This could be the compiled software binary, X-as-Code State, or a log file.
Google Cloud Build is a managed &amp;lsquo;serverless&amp;rsquo; CI/CD pipeline service allowing you to run pipelines without the need to maintain any infrastructure and only pay for the compute over the time the pipeline is running.</description><dc:creator>Kieran Goldsworthy</dc:creator><media:content url="https://blog.kgol.xyz/img/gcp-interrogation.webp" medium="image"><media:title type="html">featured image</media:title></media:content><category>GCP</category><category>CI/CD</category><category>Man Pages</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>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>Configure multiple NICs and IPs on Linux</title><link>https://blog.kgol.xyz/en/posts/configure-multiple-nics-and-ips-on-linux/</link><pubDate>Wed, 05 Feb 2020 00:00:00 +0000</pubDate><atom:modified>Wed, 05 Feb 2020 00:00:00 +0000</atom:modified><guid>https://blog.kgol.xyz/en/posts/configure-multiple-nics-and-ips-on-linux/</guid><description>IPv4 is running out, get &amp;rsquo;em while they&amp;rsquo;re hot!
If you are in business of building and configuring Linux servers, there will come a day where you need to configure a server with multiple Network Interface Cards and/or multiple IP Address.
I had just such a task.
Before we go on, the rest of this article is going to focus on Ethernet Network Interfaces of Red Hat Enterprise Linux 7.5 servers running on AWS EC2.</description><dc:creator>Kieran Goldsworthy</dc:creator><media:content url="https://blog.kgol.xyz/img/networking.jpg" medium="image"><media:title type="html">featured image</media:title></media:content><category>Linux</category><category>Bash</category><category>Man Pages</category></item></channel></rss>