<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>DevOps on Codex.org</title>
    <link>http://localhost:1313/categories/devops/</link>
    <description>Recent content in DevOps on Codex.org</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>©2000-2026 Codex.org</copyright>
    <lastBuildDate>Wed, 30 Dec 2020 14:27:20 -0500</lastBuildDate><atom:link href="http://localhost:1313/categories/devops/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Easily enable SSO (Single Sign-On) to protect your AWS Accounts</title>
      <link>http://localhost:1313/posts/easily-enable-sso-single-sign-on-to-protect-your-aws-accounts/</link>
      <pubDate>Wed, 30 Dec 2020 14:27:20 -0500</pubDate>
      
      <guid>http://localhost:1313/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;&#xA;&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>Setting up the cfnmason project for Python</title>
      <link>http://localhost:1313/posts/setting-up-the-cfnmason-project-for-python/</link>
      <pubDate>Sun, 24 Nov 2019 08:17:22 -0500</pubDate>
      
      <guid>http://localhost:1313/posts/setting-up-the-cfnmason-project-for-python/</guid>
      <description>&lt;p&gt;Cfnmason is yet another tool that can be used to manipulate cloudformation stacks. It is not designed to be a replacement for CloudFormation like Terraform, but as a means of making building and managing them easier. I had written a version of this ages ago in Ruby, but with most of my work now being in Python, I am creating a new version in Python. As I have never created an exportable Python package, this will track the process of building and releasing a new PyPi package.&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>Writing Tech Blogs are Hard Work</title>
      <link>http://localhost:1313/posts/writing-tech-blogs-are-hard-work/</link>
      <pubDate>Mon, 19 Nov 2018 21:31:23 -0500</pubDate>
      
      <guid>http://localhost:1313/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>DevOps Consultant vs DevOps Engineer</title>
      <link>http://localhost:1313/posts/devops-consultant-vs-devops-engineer/</link>
      <pubDate>Fri, 19 Oct 2018 23:04:05 -0400</pubDate>
      
      <guid>http://localhost:1313/posts/devops-consultant-vs-devops-engineer/</guid>
      <description>&lt;p&gt;What is the difference between a DevOps Consultant and a DevOps Engineer? This question recently came up and I wanted to add my thoughts on the topic.&lt;/p&gt;&#xA;&lt;p&gt;First, lets address the fact that consultants are almost always hired to work on a specific project or to address a specific issue the company is facing. As such, the role of a consultant will probably always be different than that of a regular employee. The regular employee has to deal with the mundane job of ensuring the lights are on, email, ongoing projects, operations, regular development tasks. The list goes on.&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>DevOps is more than just about developers</title>
      <link>http://localhost:1313/posts/devops-is-more-than-just-about-developers/</link>
      <pubDate>Sat, 25 Feb 2017 20:04:27 -0500</pubDate>
      
      <guid>http://localhost:1313/posts/devops-is-more-than-just-about-developers/</guid>
      <description>&lt;h3 class=&#34;relative group&#34;&gt;There. It has been said. Take a moment, and think about it.&#xA;    &lt;div id=&#34;there-it-has-been-said-take-a-moment-and-think-about-it&#34; class=&#34;anchor&#34;&gt;&lt;/div&gt;&#xA;    &#xA;    &lt;span&#xA;        class=&#34;absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none&#34;&gt;&#xA;        &lt;a class=&#34;text-primary-300 dark:text-neutral-700 !no-underline&#34; href=&#34;#there-it-has-been-said-take-a-moment-and-think-about-it&#34; aria-label=&#34;Anchor&#34;&gt;#&lt;/a&gt;&#xA;    &lt;/span&gt;&#xA;    &#xA;&lt;/h3&gt;&#xA;&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>
    
  </channel>
</rss>
