<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>AWS on Tibor Hercz - Writing about Cloud, architecture, AWS, GCP and software engineering.</title>
    <link>https://tiborhercz.com/tags/aws/</link>
    <description>Recent content in AWS on Tibor Hercz - Writing about Cloud, architecture, AWS, GCP and software engineering.</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Fri, 12 Jul 2024 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://tiborhercz.com/tags/aws/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>AWS ECS Auto Scaling</title>
      <link>https://tiborhercz.com/aws-ecs-auto-scaling/</link>
      <pubDate>Fri, 12 Jul 2024 00:00:00 +0000</pubDate>
      <guid>https://tiborhercz.com/aws-ecs-auto-scaling/</guid>
      <description>&lt;p&gt;When I first started using AWS ECS, I was a bit confused about how to scale the service.&#xA;I thought (and hoped) it was one simple setting, but it turned out to be a bit more complicated and requires various settings to be configured.&#xA;This article summarizes the settings needed to enable auto-scaling for an ECS service.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Golang JWT authorizer for AWS API Gateway</title>
      <link>https://tiborhercz.com/golang-jwt-authorizer-for-aws-api-gateway/</link>
      <pubDate>Wed, 05 Jul 2023 00:00:00 +0000</pubDate>
      <guid>https://tiborhercz.com/golang-jwt-authorizer-for-aws-api-gateway/</guid>
      <description>&lt;p&gt;When using AWS API Gateway you can use the AWS Lambda authorizer for HTTP APIs to authorize the requests.&#xA;In this blog I will show you how to validate a JWT token signed with KMS in a Lambda using the Golang runtime.&#xA;For the examples I am using API Gateway V2 with HTTP APIs with the &lt;code&gt;v2&lt;/code&gt; authorizer payload format version and for the resources I am using Terraform.&lt;/p&gt;</description>
    </item>
    <item>
      <title>How to: Deploy Terraform to AWS with GitHub Actions authenticated with OpenID Connect</title>
      <link>https://tiborhercz.com/how-to-deploy-terraform-to-aws-with-github-actions-authenticated-with-openid-connect/</link>
      <pubDate>Sun, 14 May 2023 00:00:00 +0000</pubDate>
      <guid>https://tiborhercz.com/how-to-deploy-terraform-to-aws-with-github-actions-authenticated-with-openid-connect/</guid>
      <description>&lt;p&gt;In the past it was very common to use AWS credentials (access token and secret) in your GitHub actions pipeline.&#xA;This poses a security risk because most of the time these AWS credentials are long-lived credentials with a lot of permissions.&#xA;If these credentials get leaked or misused the damage done could be huge.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Improve your AWS user management and security with AWS IAM Identity Center (SSO)</title>
      <link>https://tiborhercz.com/improve-your-aws-user-management-and-security-with-aws-iam-identity-center-sso/</link>
      <pubDate>Tue, 02 May 2023 00:00:00 +0000</pubDate>
      <guid>https://tiborhercz.com/improve-your-aws-user-management-and-security-with-aws-iam-identity-center-sso/</guid>
      <description>&lt;p&gt;I have seen a lot AWS environments and noticed that it is very common that companies use AWS IAM users to log in and access the API.&#xA;This can cause security issues and is time-consuming to manage but is very easy to improve by setting up AWS IAM Identity Center (Successor to AWS Single Sign-On).&lt;/p&gt;</description>
    </item>
    <item>
      <title>Steps to take after leaking AWS credentials</title>
      <link>https://tiborhercz.com/steps-to-take-after-leaking-aws-credentials/</link>
      <pubDate>Wed, 26 Apr 2023 00:00:00 +0000</pubDate>
      <guid>https://tiborhercz.com/steps-to-take-after-leaking-aws-credentials/</guid>
      <description>&lt;p&gt;So you leaked your AWS credentials onto the world wide web, and you are wondering what to do to minimize the damage.&#xA;There are multiple steps that should be taken, but I do think that the order of these steps matter.&lt;/p&gt;</description>
    </item>
    <item>
      <title>What happens when you leak AWS credentials and how AWS minimizes the damage</title>
      <link>https://tiborhercz.com/what-happens-when-you-leak-aws-credentials-and-how-aws-minimizes-the-damage/</link>
      <pubDate>Wed, 05 Apr 2023 00:00:00 +0000</pubDate>
      <guid>https://tiborhercz.com/what-happens-when-you-leak-aws-credentials-and-how-aws-minimizes-the-damage/</guid>
      <description>&lt;p&gt;I heard multiple times that AWS scans public GitHub repositories for AWS credentials and informs its users of the leaked credentials.&lt;/p&gt;&#xA;&lt;p&gt;So I am curious to see this for myself, so I decided to intentionally leak AWS credentials to a Public GitHub repository.&#xA;And show you the steps I took and how I got informed about the leaked credentials.&lt;/p&gt;</description>
    </item>
    <item>
      <title>How to interconnect on-premises network and multiple AWS VPCs</title>
      <link>https://tiborhercz.com/how-to-interconnect-on-premises-network-and-multiple-aws-vpcs/</link>
      <pubDate>Thu, 16 Mar 2023 00:00:00 +0000</pubDate>
      <guid>https://tiborhercz.com/how-to-interconnect-on-premises-network-and-multiple-aws-vpcs/</guid>
      <description>&lt;p&gt;Creating a large network, connecting multiple VPC and an on-premises data center together can be done in multiple ways.&#xA;In this article I will explain how to do this by using Transit Gateway and Direct Connect on a high-level.&lt;/p&gt;</description>
    </item>
    <item>
      <title>How to view AWS accounts attached to IAM Identity Center (SSO) groups</title>
      <link>https://tiborhercz.com/how-to-view-aws-accounts-attached-to-iam-identity-center-sso-groups/</link>
      <pubDate>Wed, 23 Nov 2022 00:00:00 +0000</pubDate>
      <guid>https://tiborhercz.com/how-to-view-aws-accounts-attached-to-iam-identity-center-sso-groups/</guid>
      <description>&lt;p&gt;The AWS IAM Identity Center (Successor to AWS Single Sign-On) web console can be hard to navigate when trying to view the AWS accounts attached to&#xA;an AWS IAM Identity Center (Successor to AWS Single Sign-On) group.&#xA;This involves a lot of going back and forth between pages to get this seemingly simple information.&#xA;Having done this multiple times and wasting an equal amount of time.&#xA;I took the time to create a simple Go tool &lt;code&gt;aws-iam-identity-center-explorer&lt;/code&gt; making use of the AWS SDK to retrieve this information and output it in a JSON structure.&lt;/p&gt;</description>
    </item>
    <item>
      <title>CloudFormation Custom Resource: Transit Gateway Peering Accepter</title>
      <link>https://tiborhercz.com/cloudformation-custom-resource-transit-gateway-peering-accepter/</link>
      <pubDate>Mon, 11 Jul 2022 00:00:00 +0000</pubDate>
      <guid>https://tiborhercz.com/cloudformation-custom-resource-transit-gateway-peering-accepter/</guid>
      <description>&lt;p&gt;A Transit Gateway Peering Attachment must be accepted by the owner of the attachment.&#xA;Even if both Transit Gateways are in the same account. To automate this with CloudFormation I have created a custom resource.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Best practices for S3 web hosting and explaining why</title>
      <link>https://tiborhercz.com/best-practices-for-s3-web-hosting-and-explaining-why/</link>
      <pubDate>Thu, 03 Feb 2022 00:00:00 +0000</pubDate>
      <guid>https://tiborhercz.com/best-practices-for-s3-web-hosting-and-explaining-why/</guid>
      <description>&lt;p&gt;There are a lot of very good resources explaining how to set up a S3 website.&#xA;But not explaining why you should choose one option over the other.&lt;/p&gt;&#xA;&lt;p&gt;In this article I will not explain step by step how to set up a S3 website. If you are looking for that, I have added some links at the bottom of this article.&#xA;Instead I will give you the best practices and support those with an explanation.&lt;/p&gt;</description>
    </item>
    <item>
      <title>S3 website: Why your domain and bucket name must be identical</title>
      <link>https://tiborhercz.com/s3-website-why-your-domain-and-bucket-name-must-be-identical/</link>
      <pubDate>Mon, 31 Jan 2022 00:00:00 +0000</pubDate>
      <guid>https://tiborhercz.com/s3-website-why-your-domain-and-bucket-name-must-be-identical/</guid>
      <description>&lt;p&gt;When setting up S3 website hosting you can use a Route53 alias for connecting the domain to the website bucket.&#xA;This approach forces you to set identical names for the S3 bucket and domain name.&#xA;In this article I will explain to you why the domain name and bucket names must be identical.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Scheduled scaling for EC2 Auto Scaling</title>
      <link>https://tiborhercz.com/scheduled-scaling-for-ec2-auto-scaling/</link>
      <pubDate>Thu, 23 Dec 2021 00:00:00 +0000</pubDate>
      <guid>https://tiborhercz.com/scheduled-scaling-for-ec2-auto-scaling/</guid>
      <description>&lt;p&gt;Scheduled scaling for EC2 Auto Scaling can help out with predicable load by specifying capacity changes on a schedule.&#xA;For example when a busy period is expected or to save money for your development environment scaling them down outside office hours.&lt;/p&gt;</description>
    </item>
    <item>
      <title>How to bootstrap an AWS account with Terraform state backend</title>
      <link>https://tiborhercz.com/how-to-bootstrap-an-aws-account-with-terraform-state-backend/</link>
      <pubDate>Sat, 06 Nov 2021 00:00:00 +0000</pubDate>
      <guid>https://tiborhercz.com/how-to-bootstrap-an-aws-account-with-terraform-state-backend/</guid>
      <description>&lt;p&gt;If you want to create an infrastructure CI/CD pipeline for AWS using Terraform, you want to keep the state in a remote backend. When provisioning an environment with Terraform that includes the state backend resources, you will need two actions to set up the remote state backend. In this blog I will present you with a CloudFormation template with which you can bootstrap the AWS account. This will decouple the state backend resources from the Terraform template. This allows you to use the remote backend straight away from your CI/CD pipeline.&lt;/p&gt;</description>
    </item>
    <item>
      <title>How to access your AWS Secret Manager secrets in an Elastic Kubernetes Service cluster</title>
      <link>https://tiborhercz.com/how-to-access-your-aws-secret-manager-secrets-in-an-elastic-kubernetes-service-cluster/</link>
      <pubDate>Wed, 03 Nov 2021 00:00:00 +0000</pubDate>
      <guid>https://tiborhercz.com/how-to-access-your-aws-secret-manager-secrets-in-an-elastic-kubernetes-service-cluster/</guid>
      <description>&lt;p&gt;By using the Kubernetes Secrets Store CSI Driver you can provide pods with secrets from the AWS Secret Manager.&#xA;This allows you to use the features the Secrets Manager has to offer within your EKS cluster.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
