<?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 Codex.org</title><link>https://codex.org/tags/aws/</link><description>Recent content in Aws on Codex.org</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>©2000-2026 Codex.org</copyright><lastBuildDate>Sun, 11 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://codex.org/tags/aws/index.xml" rel="self" type="application/rss+xml"/><item><title>Moving from S3 to Clouflare pages</title><link>https://codex.org/posts/moving-from-s3-to-clouflare-pages/</link><pubDate>Sun, 11 Oct 2026 00:00:00 +0000</pubDate><guid>https://codex.org/posts/moving-from-s3-to-clouflare-pages/</guid><description>What it took to move from S3 to Cloudflare pages</description></item><item><title>Easily enable SSO (Single Sign-On) to protect your AWS Accounts</title><link>https://codex.org/posts/easily-enable-sso-single-sign-on-to-protect-your-aws-accounts/</link><pubDate>Wed, 30 Dec 2020 14:27:20 -0500</pubDate><guid>https://codex.org/posts/easily-enable-sso-single-sign-on-to-protect-your-aws-accounts/</guid><description>&lt;p&gt;Enabling SSO on your AWS Accounts is strongly encouraged, adds additional security, access to multiple accounts from a single entry point (with different permission sets), and above all, it is free.&lt;/p&gt;&#10;&lt;p&gt;The following is a walk-through of how to enable Single Sign On in the AWS console. These instructions are for people with individual accounts to a few accounts. Actually, these instructions are just a good general starting point for smaller size orgs.&lt;/p&gt;</description></item><item><title>An Introduction to AWS Step Functions &amp;#8211; Part 2</title><link>https://codex.org/posts/an-introduction-to-aws-step-functions-%238211-part-2/</link><pubDate>Tue, 22 Jan 2019 07:31:38 -0500</pubDate><guid>https://codex.org/posts/an-introduction-to-aws-step-functions-%238211-part-2/</guid><description>&lt;p&gt;In &lt;a href="http://new.codex.org/2018/12/getting-started-with-aws-step-functions/" target="_blank" rel="noreferrer"&gt;Part 1&lt;/a&gt;, I went through a whirlwind tour and left example code on how to create a Lambda function and a Step Function. The thing is, I did not explain how the code works. That is what this article is about. I am going to be using the same code from the previous &lt;a href="http://new.codex.org/2018/12/getting-started-with-aws-step-functions/" target="_blank" rel="noreferrer"&gt;post&lt;/a&gt;, but will be going through the code and explaining it. We shall see how well the formatting works.&lt;/p&gt;</description></item><item><title>Getting Started with AWS Step Functions Part I</title><link>https://codex.org/posts/getting-started-with-aws-step-functions-part-i/</link><pubDate>Sat, 22 Dec 2018 22:57:19 -0500</pubDate><guid>https://codex.org/posts/getting-started-with-aws-step-functions-part-i/</guid><description>&lt;p&gt;AWS came out with Step Functions a few years ago, and up until recently, I have not had the opportunity to dive in and give them a try. Yes, I could build my own pipeline or state machine, but the idea behind Step Functions is that it does most of the heavy lifting for you. That, and it ties into other AWS services. As such, I decided to dive into getting started, and looked at the demo options and walkthroughs that were available. None of them met my needs, so I rolled my own.&lt;/p&gt;</description></item><item><title>Writing Tech Blogs are Hard Work</title><link>https://codex.org/posts/writing-tech-blogs-are-hard-work/</link><pubDate>Mon, 19 Nov 2018 21:31:23 -0500</pubDate><guid>https://codex.org/posts/writing-tech-blogs-are-hard-work/</guid><description>&lt;p&gt;I once read an article that said more people need to write technical blogs. That the problem with much of the technology field was that people did not write in-depth articles on the stuff that they are doing. And, if more people were able to take the time and post a blog entry here and there we would all be better for it. As nice as that sounds, I have to say that writing technical posts are difficult, time consuming, and can quickly go out of date.&lt;/p&gt;</description></item><item><title>Configuring AWSCLI and Python on Windows</title><link>https://codex.org/posts/configuring-awscli-and-python-on-windows/</link><pubDate>Mon, 22 Oct 2018 20:28:29 -0400</pubDate><guid>https://codex.org/posts/configuring-awscli-and-python-on-windows/</guid><description>&lt;p&gt;Trying and doing stuff on a Windows 10 machine has become a rather interesting experiment. It started as a place to be able to play video games and have access to a few programs that are not easily available on Linux, to a test of seeing if I could now do all the things on Windows 10 that I could do on Linux.&lt;/p&gt;&#10;&lt;p&gt;Turns out, I wanted to test out the Cloud Directory service from AWS. I figured the 2 easiest ways to do this would be via the &lt;a href="https://aws.amazon.com/cli/" target="_blank" rel="noreferrer"&gt;AWS CLI&lt;/a&gt; and &lt;a href="https://www.python.org" target="_blank" rel="noreferrer"&gt;Python&lt;/a&gt;. It did not occur to me that I had neither of these installed until I opened up &lt;a href="http://cmder.net/" target="_blank" rel="noreferrer"&gt;Cmder.exe&lt;/a&gt; and typed [code light=”true”]aws[/code] and then [code gutter=”false”]python[/code] and both came back with the not found.&lt;/p&gt;</description></item><item><title>DevOps is more than just about developers</title><link>https://codex.org/posts/devops-is-more-than-just-about-developers/</link><pubDate>Sat, 25 Feb 2017 20:04:27 -0500</pubDate><guid>https://codex.org/posts/devops-is-more-than-just-about-developers/</guid><description>&lt;h3 class="relative group"&gt;There. It has been said. Take a moment, and think about it.&#10; &lt;div id="there-it-has-been-said-take-a-moment-and-think-about-it" class="anchor"&gt;&lt;/div&gt;&#10; &#10; &lt;span&#10; class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;&#10; &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#there-it-has-been-said-take-a-moment-and-think-about-it" aria-label="Anchor"&gt;#&lt;/a&gt;&#10; &lt;/span&gt;&#10; &#10;&lt;/h3&gt;&#10;&lt;p&gt;There is a push in the community to talk about Continuous Integration / Continuous Deployment (CI/CD), and tying this all to the DevOps movement. About what practices are used to get code to market the fastest, and with minimal amount of code defects. And, I will admit, that I agree wholeheartedly, that CI/CD or some sort of pipeline is important to allow software development teams to move fast and innovate. Or, to just roll out code without doing it every 6 months. I would almost argue that CI/CD is more akin to Agile and Scrum methodologies than it is to DevOps.&lt;/p&gt;</description></item><item><title>Building a Windows 2012R2 Instance in AWS with Terraform</title><link>https://codex.org/posts/building-a-windows-2012r2-instance-in-aws-with-terraform/</link><pubDate>Mon, 21 Nov 2016 14:22:23 -0500</pubDate><guid>https://codex.org/posts/building-a-windows-2012r2-instance-in-aws-with-terraform/</guid><description>&lt;p&gt;Terraform is an application by HashiCorp that is designed to treat infrastructure as code. Lately, I have been working with it to begin automation of resources within AWS, and have been quite pleased.&lt;/p&gt;&#10;&lt;p&gt;Lets get started with building out a Windows 2012 R2 server with Terraform on AWS.&lt;/p&gt;&#10;&lt;p&gt;You are going to need to have the following items configured in AWS in order for this to work, as I am not going to be using Terraform to build out these items.&lt;/p&gt;</description></item><item><title>Terraform vs Cloudformation &amp;#8212; First Thoughts</title><link>https://codex.org/posts/terraform-vs-cloudformation-%238212-first-thoughts/</link><pubDate>Sun, 06 Nov 2016 10:25:09 -0500</pubDate><guid>https://codex.org/posts/terraform-vs-cloudformation-%238212-first-thoughts/</guid><description>&lt;p&gt;Building out AWS infrastructures by hand is not something that should be taken on lightly. Just as in building out a Data Center or service in any cloud environment (Google, VMWare, etc), building out a bunch of systems by hand is a good way to inherit a bunch of technical debt and a headache or three. On top of that, it is slow and cumbersome to build out servers in a manual fashion, and since it is done manually, it is easy to make mistakes and introduce snowflakes into your environment. Instead, we need to address the build out with automation tooling.&lt;/p&gt;</description></item></channel></rss>