<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Aws on The IT Hollow</title>
    <link>https://theithollow.com/categories/aws/</link>
    <description>Recent content in Aws on The IT Hollow</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 17 Jun 2019 14:02:18 +0000</lastBuildDate>
    <atom:link href="https://theithollow.com/categories/aws/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>AWS Account Tagging</title>
      <link>https://theithollow.com/2019/06/17/aws-account-tagging/</link>
      <pubDate>Mon, 17 Jun 2019 14:02:18 +0000</pubDate>
      <guid>https://theithollow.com/2019/06/17/aws-account-tagging/</guid>
      <description>&lt;p&gt;We&amp;rsquo;re getting into the habit of tagging everything these days. It&amp;rsquo;s been drilled into our heads that we don&amp;rsquo;t care about names of our resources anymore because we can add our own metadata to resources to later identify them, or to use for automation. But up until June 6th, AWS wouldn&amp;rsquo;t let us tag one of the most important resources of all, our accounts.&lt;/p&gt;
&lt;p&gt;On June 6th though, our cloud world changed when &lt;a href=&#34;https://aws.amazon.com/about-aws/whats-new/2019/06/aws-organizations-now-supports-tagging-and-untagging-of-aws-acco/&#34;&gt;AWS announced&lt;/a&gt; that we can now add tags to our accounts through organizations.&lt;/p&gt;</description>
    </item>
    <item>
      <title>AWS Native Backups</title>
      <link>https://theithollow.com/2019/01/22/aws-native-backups/</link>
      <pubDate>Tue, 22 Jan 2019 16:00:59 +0000</pubDate>
      <guid>https://theithollow.com/2019/01/22/aws-native-backups/</guid>
      <description>&lt;figure&gt;
    &lt;img loading=&#34;lazy&#34; src=&#34;https://assets.theithollow.com/wp-content/uploads/2019/01/awsbackup1-1024x298.png&#34;/&gt; 
&lt;/figure&gt;

&lt;p&gt;Amazon Web Services has released yet another service designed to improve the lives of people administering an AWS environment. There is a new backup service, cleverly named, AWS Backup.&lt;/p&gt;
&lt;p&gt;This new service allows you to create a backup plan for Elastic Block Store (EBS) volumes, Elastic File System (EFS), DynamoDB, Relational Database Services (RDS), and Storage Gateway.&lt;/p&gt;
&lt;p&gt;Now we can build plans to automatically backup, tier and expire old backups automatically based on our own criteria.&lt;/p&gt;</description>
    </item>
    <item>
      <title>AWS Security Hub</title>
      <link>https://theithollow.com/2018/12/17/aws-security-hub/</link>
      <pubDate>Mon, 17 Dec 2018 15:00:59 +0000</pubDate>
      <guid>https://theithollow.com/2018/12/17/aws-security-hub/</guid>
      <description>&lt;p&gt;A primary concern for companies moving to the cloud is whether or not their workloads will remain secure. While that debate still happens, AWS has made great strides to assuage customer&amp;rsquo;s concerns by adding services to ensure workloads are well protected. At re:Invent 2018 another service named &lt;a href=&#34;https://aws.amazon.com/security-hub/&#34;&gt;AWS Security Hub&lt;/a&gt; was added. Security Hub allows you to setup some basic security guardrails and get compliance information for multiple accounts within a single service. Amazon seems to have realized that enabling customers to very easily see their security recommendations for all environments in a single place has great value to their businesses.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Setup AWS Transit Gateway</title>
      <link>https://theithollow.com/2018/12/12/setup-aws-transit-gateway/</link>
      <pubDate>Wed, 12 Dec 2018 15:00:07 +0000</pubDate>
      <guid>https://theithollow.com/2018/12/12/setup-aws-transit-gateway/</guid>
      <description>&lt;p&gt;Amazon announced a new service at re:Invent 2018 in Las Vegas, called the &lt;a href=&#34;https://aws.amazon.com/transit-gateway/&#34;&gt;AWS Transit Gateway&lt;/a&gt;. The Transit Gateway allows you to connect multiple VPCs together as well as VPN tunnels to on-premises networks through a single gateway device. As a consultant, I talk with customers often, about how they will plan to connect their data center with the AWS cloud, and how to interconnect all of those VPCs. In the past a solution like Aviatrix or a Cisco CSR transit gateway was used which leveraged some EC2 instances that lived within a VPC. You&amp;rsquo;d then connect spoke VPCs together via the use of VPN tunnels. With this new solution, there is a native service from AWS that allows you to do this without the need for VPN tunnels between spoke VPCs and you can use the AWS CLI/CloudFormation or console to deploy everything you need. This post takes you through an example of the setup of the AWS Transit Gateway in my own lab environment.&lt;/p&gt;</description>
    </item>
    <item>
      <title>AWS Resource Access Manager</title>
      <link>https://theithollow.com/2018/12/10/aws-resource-access-manager/</link>
      <pubDate>Mon, 10 Dec 2018 15:00:44 +0000</pubDate>
      <guid>https://theithollow.com/2018/12/10/aws-resource-access-manager/</guid>
      <description>&lt;p&gt;At AWS re:Invent this year in Las Vegas, Amazon announced a ton of services, but one that caught my eye was the AWS Resource Access Manager. This is a service that facilitates the sharing of some resources between AWS accounts so that they can be used or referenced across account boundaries. Typically, an AWS account is used as a control plane boundary (or billing boundary) between environments, but even then resources will need to communicate with each other occasionally. Now with AWS Resource Access Manager (RAM) we can shared Hosted DNS zones, Transit Gateways and other objects. This list will undoubtedly grow over time. This post will show you how you can share another new service, the AWS Transit Gateway, across multiple accounts within your organization.&lt;/p&gt;</description>
    </item>
    <item>
      <title>VMware Cloud on AWS Firewalls Overview</title>
      <link>https://theithollow.com/2018/11/28/vmware-cloud-on-aws-firewalls-overview/</link>
      <pubDate>Wed, 28 Nov 2018 16:03:46 +0000</pubDate>
      <guid>https://theithollow.com/2018/11/28/vmware-cloud-on-aws-firewalls-overview/</guid>
      <description>&lt;p&gt;If you&amp;rsquo;re getting started with VMware Cloud on AWS then you should be aware of all the points in which you can block traffic with a firewall. Or, if you look at it another way, the places where you might need to create allow rules for traffic to traverse your cloud. This post is used to show where those choke points live both within your VMware Cloud on AWS SDDC, as well as the Amazon VPC in which your SDDC lives.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Using AWS CloudFormation Drift Detection</title>
      <link>https://theithollow.com/2018/11/14/using-aws-cloudformation-drift-detection/</link>
      <pubDate>Wed, 14 Nov 2018 15:02:55 +0000</pubDate>
      <guid>https://theithollow.com/2018/11/14/using-aws-cloudformation-drift-detection/</guid>
      <description>&lt;p&gt;Today, AWS announced the release of the long anticipated drift detection feature for CloudFormation. This feature has been a common feature request for many of the AWS customers that I speak with to ensure their deployments are configured as expected. This post will take you through why this is an important feature and how you can use it.&lt;/p&gt;
&lt;h1 id=&#34;whats-the-big-deal&#34;&gt;Whats the Big Deal?&lt;/h1&gt;
&lt;p&gt;If you&amp;rsquo;re not familiar with it already, CloudFormation is a free service from AWS that lets you describe your infrastructure through a YAML or JSON file and deploy the configuration. Simply define your desired state and CloudFormation will deploy the resources and arrange them so that dependent services are (usually) deployed in the right order. If you&amp;rsquo;re familiar with Ansible, Chef, or Puppet, this concept of a desired state shouldn&amp;rsquo;t be new.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Restore or Resize an AWS Transit Router</title>
      <link>https://theithollow.com/2018/10/22/restore-or-resize-an-aws-transit-router/</link>
      <pubDate>Mon, 22 Oct 2018 14:03:21 +0000</pubDate>
      <guid>https://theithollow.com/2018/10/22/restore-or-resize-an-aws-transit-router/</guid>
      <description>&lt;p&gt;A transit VPC is a pretty common networking pattern in an AWS environment. [Transit VPCs](http://Should I use a Transit VPC in AWS?) can limit the number of peering connections required to connect all your VPCs by switching from a mesh topology of peers to a hub and spoke method with transit. While transit VPCs offer some nice features, it also requires a bit more management overhead since you need to manage your own routers. Cisco makes the deployment of transit routers very easy but sometimes you need to make some changes to the routers after they&amp;rsquo;re deployed like if you need to resize them. Also, sometimes bad things happen and those routers can be destroyed by accident. This post shows how you can resize your Cisco CSRs and/or restore an old configuration from snapshot.&lt;/p&gt;</description>
    </item>
    <item>
      <title>AWS Session Manager</title>
      <link>https://theithollow.com/2018/10/01/aws-session-manager/</link>
      <pubDate>Mon, 01 Oct 2018 14:05:01 +0000</pubDate>
      <guid>https://theithollow.com/2018/10/01/aws-session-manager/</guid>
      <description>&lt;p&gt;Amazon has released yet another &lt;a href=&#34;https://theithollow.com/2017/10/02/aws-ec2-simple-systems-manager-reference/&#34;&gt;Simple Systems Manager&lt;/a&gt; service to improve the management of EC2 instances. This time, it&amp;rsquo;s AWS Session Manager. Session Manager is a nifty little service that lets you assign permissions to users to access an instances&amp;rsquo;s shell. Now, you might be thinking, &amp;ldquo;Why would I need this? I can already add SSH keys to my instances at boot time to access my instances.&amp;rdquo; You&amp;rsquo;d be right of course, but think of how you might use Session Manager. Instead of having to deal with adding SSH keys, and managing access/distribution of the private keys, we can manage access through AWS Identity and Access Management permissions.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Close an AWS Account Belonging to an Organization</title>
      <link>https://theithollow.com/2018/09/17/close-an-aws-account-belonging-to-an-organization/</link>
      <pubDate>Mon, 17 Sep 2018 14:05:24 +0000</pubDate>
      <guid>https://theithollow.com/2018/09/17/close-an-aws-account-belonging-to-an-organization/</guid>
      <description>&lt;p&gt;Opening an AWS account is very easy to do. AWS makes it possible to create an account with an email address and a credit card. Even better, if you&amp;rsquo;re setting up a multi-account structure, you can use the API through organizations and you really only need an email address as an input. But closing an account is slightly more difficult. While closing accounts doesn&amp;rsquo;t happen quite as often as opening new ones, it does happen. Especially if you&amp;rsquo;re trying to fail fast and have made some organizational mistakes. When you want to clean those accounts up, you&amp;rsquo;ll need to jump through a couple of small hoops to do so. This post hopes to outline how to remove an account from an AWS Organization and then close it.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Create AWS Accounts with CloudFormation</title>
      <link>https://theithollow.com/2018/09/10/create-aws-accounts-with-cloudformation/</link>
      <pubDate>Mon, 10 Sep 2018 14:05:20 +0000</pubDate>
      <guid>https://theithollow.com/2018/09/10/create-aws-accounts-with-cloudformation/</guid>
      <description>&lt;p&gt;In a &lt;a href=&#34;https://theithollow.com/2018/09/04/aws-custom-resources/&#34;&gt;previous post&lt;/a&gt;, we covered how to use an AWS Custom Resource in a CloudFormation template to deploy a very basic Lambda function. To expand upon this ability, lets use this knowledge to deploy something more useful than a basic Lambda function. How about we use it to create an AWS account? To my knowledge, the only way to create a new AWS account is to use the CLI or manually through the console. How about we use a custom resource to deploy a new account for us in our AWS Organization? Once this ability is available in a CloudFormation template, we could even publish it in the AWS Service Catalog and give our users an account vending machine capability.&lt;/p&gt;</description>
    </item>
    <item>
      <title>AWS Custom Resources</title>
      <link>https://theithollow.com/2018/09/04/aws-custom-resources/</link>
      <pubDate>Tue, 04 Sep 2018 14:00:04 +0000</pubDate>
      <guid>https://theithollow.com/2018/09/04/aws-custom-resources/</guid>
      <description>&lt;p&gt;We love to use AWS CloudFormation to deploy our environments. Its like configuration management for our AWS infrastructure in the sense that we write a desired state as code and apply it to our environment. But sometimes, there are tasks that we want to complete that aren&amp;rsquo;t part of CloudFormation. For instance, what if we wanted to use CloudFormation to deploy a new account which needs to be done through the CLI, or if we need to return some information to our CloudFormation template before deploying it? Luckily for us we can use a Custom Resource to achieve our goals. This post shows how you can use CloudFormation with a Custom Resource to execute a very basic Lambda function as part of a deployment.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Add AWS Web Application Firewall to Protect your Apps</title>
      <link>https://theithollow.com/2018/08/20/add-aws-web-application-firewall-to-protect-your-apps/</link>
      <pubDate>Mon, 20 Aug 2018 14:02:31 +0000</pubDate>
      <guid>https://theithollow.com/2018/08/20/add-aws-web-application-firewall-to-protect-your-apps/</guid>
      <description>&lt;p&gt;Some things change when you move to the cloud, but other things are very much the same. Like protecting your resources from outside threats. There are always no-gooders out there trying to steal data, or cause mayhem like in those Allstate commercials. Our first defense should be well written applications, requiring authentication, etc and with AWS we make sure we&amp;rsquo;re setting up security groups to limit our access to those resources. How about an extra level of protection from a Web Application Firewall. AWS WAF allows us to leverage some extra protections at the edge to protect us from those bad guys/girls.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Using AWS CodeDeploy to Push New Versions of your Application</title>
      <link>https://theithollow.com/2018/08/06/using-aws-codedeploy-to-push-new-versions-of-your-application/</link>
      <pubDate>Mon, 06 Aug 2018 14:04:33 +0000</pubDate>
      <guid>https://theithollow.com/2018/08/06/using-aws-codedeploy-to-push-new-versions-of-your-application/</guid>
      <description>&lt;p&gt;Getting new code onto our servers can be done in a myriad of ways these days. Configuration management tools can pull down new code, pipelines can run scripts across our fleets, or we could run around with a USB stick for the rest of our lives. With container based apps, serverless functions, and immutable infrastructure, we&amp;rsquo;ve changed this conversation quite a bit as well. But what about a plain old server that needs a new version of code deployed on it? AWS CodeDeploy can help us to manage our software versions and rollbacks so that we have a consistent method to update our apps across multiple instances. This post will demonstrate how to get started with AWS CodeDeploy so that you can manage the deployment of new versions of your apps.&lt;/p&gt;</description>
    </item>
    <item>
      <title>How to Setup Amazon EKS with Mac Client</title>
      <link>https://theithollow.com/2018/07/31/how-to-setup-amazon-eks-with-mac-client/</link>
      <pubDate>Tue, 31 Jul 2018 14:06:02 +0000</pubDate>
      <guid>https://theithollow.com/2018/07/31/how-to-setup-amazon-eks-with-mac-client/</guid>
      <description>&lt;p&gt;We love Kubernetes. It&amp;rsquo;s becoming a critical platform for us to manage our containers, but deploying Kubernetes clusters is pretty tedious. Luckily for us, cloud providers such as AWS are helping to take care of these tedious tasks so we can focus on what is more important to us, like building apps. This post shows how you can go from a basic AWS account to a Kubernetes cluster for you to deploy your applications.&lt;/p&gt;</description>
    </item>
    <item>
      <title>How to Setup Amazon EKS with Windows Client</title>
      <link>https://theithollow.com/2018/07/30/how-to-setup-amazon-eks-with-windows-client/</link>
      <pubDate>Mon, 30 Jul 2018 16:05:09 +0000</pubDate>
      <guid>https://theithollow.com/2018/07/30/how-to-setup-amazon-eks-with-windows-client/</guid>
      <description>&lt;p&gt;We love Kubernetes. It&amp;rsquo;s becoming a critical platform for us to manage our containers, but deploying Kubernetes clusters is pretty tedious. Luckily for us, cloud providers such as AWS are helping to take care of these tedious tasks so we can focus on what is more important to us, like building apps. This post shows how you can go from a basic AWS account to a Kubernetes cluster for you to deploy your applications.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Easy Snapshot Automation with Amazon Data Lifecycle Manager</title>
      <link>https://theithollow.com/2018/07/23/easy-snapshot-automation-with-amazon-data-lifecycle-manager/</link>
      <pubDate>Mon, 23 Jul 2018 14:05:53 +0000</pubDate>
      <guid>https://theithollow.com/2018/07/23/easy-snapshot-automation-with-amazon-data-lifecycle-manager/</guid>
      <description>&lt;p&gt;Amazon has announced a new service that will help customers manage their EBS volume snapshots in a very simple manner. The Data Lifecycle Manager service lets you setup a schedule to snapshot any of your EBS volumes during a specified time window.&lt;/p&gt;
&lt;p&gt;In the past, AWS customers might need to come up with their own solution for snapshots or backups. Some apps moving to the cloud might not even need backups based on their deployment method and architectures. For everything else, we assume we&amp;rsquo;ll need to at least snapshot the EBS volumes that the EC2 instances are running on. Prior to the Data Lifecycle Manager, this could be accomplished through some fairly simple Lambda functions to snapshot volumes on a schedule. Now with the new service, there is a solution right in the EC2 console.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Should I use a Transit VPC in AWS?</title>
      <link>https://theithollow.com/2018/07/16/should-i-use-a-transit-vpc-in-aws/</link>
      <pubDate>Mon, 16 Jul 2018 14:05:46 +0000</pubDate>
      <guid>https://theithollow.com/2018/07/16/should-i-use-a-transit-vpc-in-aws/</guid>
      <description>&lt;p&gt;A common question that comes up during AWS designs is, &amp;ldquo;Should I use a transit VPC?&amp;rdquo; The answer, like all good IT riddles is, &amp;ldquo;it depends.&amp;rdquo; There are a series of questions that you must ask yourself before deciding whether to use a Transit VPC or not. In this post, I&amp;rsquo;ll try to help formulate those questions so you can answer this question yourself.&lt;/p&gt;
&lt;h1 id=&#34;the-basics&#34;&gt;The Basics&lt;/h1&gt;
&lt;p&gt;Before we can ask those tough questions, we first should answer the question, &amp;ldquo;What is a Transit VPC?&amp;rdquo; Well, a transit VPC acts as an intermediary for routing between two places. Just like a transit network bridges traffic between two networks, a transit VPC ferries traffic between two VPCs or perhaps your data center.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Visualizing the Chicago Cubs via Amazon QuickSight</title>
      <link>https://theithollow.com/2018/05/14/visualizing-the-chicago-cubs-via-amazon-quicksight/</link>
      <pubDate>Mon, 14 May 2018 15:01:07 +0000</pubDate>
      <guid>https://theithollow.com/2018/05/14/visualizing-the-chicago-cubs-via-amazon-quicksight/</guid>
      <description>&lt;p&gt;If you&amp;rsquo;re interested in visualizing your data in easy to display graphs, Amazon QuickSight may be your solution. Obviously, Amazon has great capabilities with big data, but sometimes even if you have &amp;ldquo;little&amp;rdquo; data you just need a dashboard or way of displaying that content. This post shows an example of how you can display data to tell a compelling story. For the purposes of this blog post, we&amp;rsquo;ll try to determine why the Chicago Cubs are the Major League&amp;rsquo;s favorite baseball team.&lt;/p&gt;</description>
    </item>
    <item>
      <title>AWS IAM Indecision</title>
      <link>https://theithollow.com/2018/05/07/aws-iam-indecision/</link>
      <pubDate>Mon, 07 May 2018 14:55:55 +0000</pubDate>
      <guid>https://theithollow.com/2018/05/07/aws-iam-indecision/</guid>
      <description>&lt;p&gt;Identity and Access Management (IAM) can be a confusing topic for people that are new to Amazon Web Services. There are IAM Users that could be used for authentication or solutions considered part of the AWS Directory Services such as Microsoft AD, Simple AD, or AD Connector. If none of these sound appealing, there is always the option to use Federation with a SAML 2.0 solution like OKTA, PING, or Active Directory Federation Services (ADFS). If all of these option have given you a case of decision fatigue, then hopefully this post and the associate links will help you to decide how your environment should be setup.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Manage Multiple AWS Accounts with Role Switching</title>
      <link>https://theithollow.com/2018/04/30/manage-multiple-aws-accounts-with-role-switching/</link>
      <pubDate>Mon, 30 Apr 2018 14:05:52 +0000</pubDate>
      <guid>https://theithollow.com/2018/04/30/manage-multiple-aws-accounts-with-role-switching/</guid>
      <description>&lt;p&gt;A pretty common question that comes up is how to manage multiple accounts within AWS from a user perspective. Multi-Account setups are common to provide control plane separation between Production, Development, Billing and Shared Services accounts but do you need to setup Federation with each of these accounts or create an IAM user in each one? That makes those accounts kind of cumbersome to manage and the more users we have the more chance one of them could get hacked.&lt;/p&gt;</description>
    </item>
    <item>
      <title>AWS Directory Service - AD Connector</title>
      <link>https://theithollow.com/2018/04/23/aws-directory-service-ad-connector/</link>
      <pubDate>Mon, 23 Apr 2018 14:05:05 +0000</pubDate>
      <guid>https://theithollow.com/2018/04/23/aws-directory-service-ad-connector/</guid>
      <description>&lt;p&gt;Just because you&amp;rsquo;ve started moving workloads into the cloud, doesn&amp;rsquo;t mean you can forget about Microsoft Active Directory. Many customers simply stand up their own domain controllers on EC2 instances to provide domain services. But if you&amp;rsquo;re moving to AWS there are also some great services you can take advantage of, to provide similar functionality. This post focuses on AD Connector which makes a connection to your on-premises or EC2 installed domain controllers. AD Connector doesn&amp;rsquo;t run your Active Directory but rather uses your existing active directory intances within AWS. As such, in order to use AD Connector you would need to have a VPN connection or Direct Connect to provide connectivity back to your data center. Also, you&amp;rsquo;ll need to be prepared to have credentials to connect to the domain. Domain Admin credentials will work, but as usual you should use as few privileges as possible so delegate access to a user with the follow permissions:&lt;/p&gt;</description>
    </item>
    <item>
      <title>AWS Directory Service - Simple AD</title>
      <link>https://theithollow.com/2018/04/16/aws-directory-service-simple-ad/</link>
      <pubDate>Mon, 16 Apr 2018 14:12:58 +0000</pubDate>
      <guid>https://theithollow.com/2018/04/16/aws-directory-service-simple-ad/</guid>
      <description>&lt;p&gt;Just because you&amp;rsquo;ve started moving workloads into the cloud, doesn&amp;rsquo;t mean you can forget about Microsoft Active Directory. Many customers simply stand up their own domain controllers on EC2 instances to provide domain services. But if you&amp;rsquo;re moving to AWS, there are also some great services you can take advantage of to provide similar functionality. This post focuses on Simple AD is based on Samba4 and handles a subset of the features that the &lt;a href=&#34;https://theithollow.com/2018/04/09/aws-directory-service-microsoft-ad/&#34;&gt;Microsoft AD&lt;/a&gt; type Directory Service provides. This service still allows you to use Kerberos authentication and manage users and computers as well as provide DNS services. One of the major differences between this service and Microsoft AD is that you can&amp;rsquo;t create a trust relationship with your existing domain, so if you need that functionality look at Microsoft AD instead. Simple AD gives you a great way to quickly stand up new domains and cut down on the things you need to manage such as OS patches, etc.&lt;/p&gt;</description>
    </item>
    <item>
      <title>AWS Directory Service - Microsoft AD</title>
      <link>https://theithollow.com/2018/04/09/aws-directory-service-microsoft-ad/</link>
      <pubDate>Mon, 09 Apr 2018 14:55:20 +0000</pubDate>
      <guid>https://theithollow.com/2018/04/09/aws-directory-service-microsoft-ad/</guid>
      <description>&lt;p&gt;Just because you&amp;rsquo;ve started moving workloads into the cloud, doesn&amp;rsquo;t mean you can forget about Microsoft Active Directory. Many customers simply stand up their own domain controllers on EC2 instances to provide domain services. But if you&amp;rsquo;re moving to AWS there are also some great services you can take advantage of, to provide similar functionality. This post focuses on Microsoft AD which is a Server 20012 R2 based domain that provides a pair of domain controllers across Availability Zones and also handles DNS. This service is the closest service to a full blow Active Directory that you&amp;rsquo;d host on premises. You can even create a trust between the Microsoft AD deployed in AWS and your on-prem domain. You cannot extend your on-premises domain into Microsoft AD at the time of this writing though. If you wish to extend your existing domain, you should consider building your own DCs on EC2 instances and then you have full control over your options.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Protect Your AWS Accounts with GuardDuty</title>
      <link>https://theithollow.com/2018/04/02/protect-your-aws-accounts-with-guardduty/</link>
      <pubDate>Mon, 02 Apr 2018 14:05:29 +0000</pubDate>
      <guid>https://theithollow.com/2018/04/02/protect-your-aws-accounts-with-guardduty/</guid>
      <description>&lt;p&gt;Locking down an AWS environment isn&amp;rsquo;t really that if you know what threats you&amp;rsquo;re protecting against. You have services such as the Web Application Firewall, Security Groups, Network Access Control Lists, Bucket Policies and the list goes on. But many times you encounter threats from malicious attackers just trying to probe which vulnerabilities might exist in your cloud. AWS has built a service, called Amazon GuardDuty, to help monitor and protect your environment that is based on AWS machine learning tools and threat intelligence feeds. GuardDuty currently reads VPC Flow Logs (used for network traffic analysis) and CloudTrail Logs (used for control plane access analysis) along with DNS log data to protect an AWS environment. GuardDuty will use threat intelligence feeds to alert you when your workloads may be communicating with known to be malicious IP Addresses and can alert you when privileged escalation occurs as part of its machine learning about suspicious patterns.&lt;/p&gt;</description>
    </item>
    <item>
      <title>AWS Reserved Instance Considerations</title>
      <link>https://theithollow.com/2018/02/19/aws-reserved-instance-considerations/</link>
      <pubDate>Mon, 19 Feb 2018 15:10:10 +0000</pubDate>
      <guid>https://theithollow.com/2018/02/19/aws-reserved-instance-considerations/</guid>
      <description>&lt;p&gt;Reserved Instances are often used to reduce the price of Amazon EC2 instance on-demand pricing. If you&amp;rsquo;re not familiar with Reserved Instances, then you&amp;rsquo;re missing out. Reserved Instances, or RIs, are a billing construct used in conjunction with Amazon EC2 instances (virtual machines). The default usage on the AWS platform is the on-demand pricing in which you get billed by the hour or second with no commitments. Basically, when you decide to terminate an instance you stop paying for it.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Setup MFA for AWS Root Accounts</title>
      <link>https://theithollow.com/2018/02/12/setup-mfa-aws-root-accounts/</link>
      <pubDate>Mon, 12 Feb 2018 15:07:56 +0000</pubDate>
      <guid>https://theithollow.com/2018/02/12/setup-mfa-aws-root-accounts/</guid>
      <description>&lt;p&gt;Multi-Factor Authentication or MFA, is a common security precaution used to prevent someone from gaining access to an account even if an attacker has your username and password. With MFA you must also have a device that generates a time based one time password (TOTP) in addition to the standard username/password combination. The extra time it might take to login is well worth the advantages that MFA provides. Having your AWS account hijacked could be a real headache.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Add a New AWS Account to an Existing Organization from the CLI</title>
      <link>https://theithollow.com/2018/02/05/add-new-aws-account-existing-organization-cli/</link>
      <pubDate>Mon, 05 Feb 2018 15:12:17 +0000</pubDate>
      <guid>https://theithollow.com/2018/02/05/add-new-aws-account-existing-organization-cli/</guid>
      <description>&lt;p&gt;AWS Organizations is a way for you to organize your accounts and have a hierarchy not only for bills to roll up to a single paying account, but also to setup a way to add new accounts programatically.&lt;/p&gt;
&lt;p&gt;For the purposes of this discussion, take a look at my AWS lab account structure.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://assets.theithollow.com/wp-content/uploads/2018/02/AWS-AcctSetup0.png&#34;&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://assets.theithollow.com/wp-content/uploads/2018/02/AWS-AcctSetup0.png&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;From the AWS Organizations Console we can see the account structure as well.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://assets.theithollow.com/wp-content/uploads/2018/02/AWS-AcctSetup1-mask.png&#34;&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://assets.theithollow.com/wp-content/uploads/2018/02/AWS-AcctSetup1-mask.png&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;I need to create a new account in a new OU under my master billing account. This can be accomplished through the console, but it can also be done through the AWS CLI, which is what I&amp;rsquo;ll do here. NOTE: This can be done through the API as well which can be really useful for automating the building of new accounts.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Using Change Sets with Nested CloudFormation Stacks</title>
      <link>https://theithollow.com/2018/01/29/using-change-sets-nested-cloudformation-stacks/</link>
      <pubDate>Mon, 29 Jan 2018 15:10:20 +0000</pubDate>
      <guid>https://theithollow.com/2018/01/29/using-change-sets-nested-cloudformation-stacks/</guid>
      <description>&lt;p&gt;In a &lt;a href=&#34;https://theithollow.com/2018/01/22/introduction-aws-cloudformation-change-sets/&#34;&gt;previous post&lt;/a&gt;, we looked at how to use change sets with CloudFormation. This post covers how to use change sets with a nested CloudFormation Stack.&lt;/p&gt;
&lt;p&gt;If you&amp;rsquo;re not familiar with nested CloudFormation stacks, it is just what it sounds like. A root stack or top level stack will call subordinate or child stacks as part of the deployment. These nested stacks could be deployed as a standalone stack or they can be tied together by using the AWS::CloudFormation::Stack resource type. Nested stacks can be used to deploy entire environments from the individual stacks below it. In fact a root stack may not deploy any resources at all other than what comes from the nested stacks. An example of a commons stacking method might be to have a top level stack that deploys a VPC, while a nested stack is responsible for deploying subnets within that stack. You could keep chaining this together to deploy EC2 instances, S3 buckets or whatever you&amp;rsquo;d like.&lt;/p&gt;</description>
    </item>
    <item>
      <title>An Introduction to AWS CloudFormation Change Sets</title>
      <link>https://theithollow.com/2018/01/22/introduction-aws-cloudformation-change-sets/</link>
      <pubDate>Mon, 22 Jan 2018 15:05:12 +0000</pubDate>
      <guid>https://theithollow.com/2018/01/22/introduction-aws-cloudformation-change-sets/</guid>
      <description>&lt;p&gt;If you&amp;rsquo;ve done any work in Amazon Web Services you probably know the importance of CloudFormation (CFn) as part of your Infrastructure as Code (IaC) strategy. CloudFormation provides a JSON or YAML formatted document which describes the AWS infrastructure that you want to deploy. If you need to re-deploy the same infrastructure across production and development environments, this is pretty easy since the configuration is in a template stored in your source control.&lt;/p&gt;</description>
    </item>
    <item>
      <title>In the Cloud World, It&#39;s Cheaper to Upgrade</title>
      <link>https://theithollow.com/2018/01/16/cloud-world-cheaper-upgrade/</link>
      <pubDate>Tue, 16 Jan 2018 15:10:26 +0000</pubDate>
      <guid>https://theithollow.com/2018/01/16/cloud-world-cheaper-upgrade/</guid>
      <description>&lt;p&gt;If you&amp;rsquo;ve been in technology for a while, you&amp;rsquo;ve probably had to go through a hardware refresh cycle at some point. These cycles usually meant taking existing hardware, doing some capacity planning exercises and setting out to buy new hardware that is supported by the vendors. This process was usually lengthy and made CIOs break into a cold sweat just thinking about paying for more hardware, that&amp;rsquo;s probably just meant to keep the lights on. Whenever I first learned of a hardware refresh cycle, my first thoughts were &amp;ldquo;Boy, this sounds expensive!&amp;rdquo;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Use Amazon CloudWatch Logs Metric Filters to Send Alerts</title>
      <link>https://theithollow.com/2017/12/11/use-amazon-cloudwatch-logs-metric-filters-send-alerts/</link>
      <pubDate>Mon, 11 Dec 2017 16:14:47 +0000</pubDate>
      <guid>https://theithollow.com/2017/12/11/use-amazon-cloudwatch-logs-metric-filters-send-alerts/</guid>
      <description>&lt;p&gt;With all of the services that Amazon has to offer, it can sometimes be difficult to manage your cloud environment. Face it, you need to manage multiple regions, users, storage buckets, accounts, instances and the list just keeps going on. Well the fact that the environment can be so vast might make it difficult to notice if something nefarious is going on in your cloud. Think of it this way, if a new EC2 instance was deployed in one of your most used regions, you might see it and wonder what it was, but if that instance (or 50 instances) was deployed in a region that you never login to, would you notice that?&lt;/p&gt;</description>
    </item>
    <item>
      <title>Use AWS Config Managed Rules to Protect Your Accounts</title>
      <link>https://theithollow.com/2017/11/27/use-aws-config-managed-rules-protect-accounts/</link>
      <pubDate>Mon, 27 Nov 2017 15:10:54 +0000</pubDate>
      <guid>https://theithollow.com/2017/11/27/use-aws-config-managed-rules-protect-accounts/</guid>
      <description>&lt;p&gt;If you&amp;rsquo;re an Amazon Web Services customer and you&amp;rsquo;re not using the built in AWS config rules, you should be. AWS Config is a service that shows you the configuration changes that have happened on your AWS accounts. Whether that&amp;rsquo;s changes to your user accounts, changes to networks, modifications to S3 buckets or plenty of other configurations. AWS Config will keep this audit log of your changes in a specified S3 bucket which could be used for all sorts of other solutions such as updating your ServiceNow configuration management database. See &lt;a href=&#34;http://www.servicenow.com/solutions/technology-solutions/lifecycle-management/cloud-lifecycle.html&#34;&gt;this post from ServiceNow&lt;/a&gt; on some details of the solution.&lt;/p&gt;</description>
    </item>
    <item>
      <title>AWS Dedicated Hosts</title>
      <link>https://theithollow.com/2017/11/13/aws-dedicated-hosts/</link>
      <pubDate>Mon, 13 Nov 2017 15:15:46 +0000</pubDate>
      <guid>https://theithollow.com/2017/11/13/aws-dedicated-hosts/</guid>
      <description>&lt;p&gt;Sometimes it&amp;rsquo;s just not desirable to have your Amazon EC2 instances deployed all willy-nilly across the AWS infrastructure. Sure it&amp;rsquo;s nice not having to manage the underlying infrastructure but in some cases you actually need to be able to manage the hosts themselves. One example is when you have licensing that is &amp;ldquo;old-fashioned&amp;rdquo; and uses physical core counts. With the default tenancy model, host core counts just don&amp;rsquo;t make sense, so what can we do?&lt;/p&gt;</description>
    </item>
    <item>
      <title>Manage vSphere Virtual Machines through AWS SSM</title>
      <link>https://theithollow.com/2017/11/06/manage-vsphere-virtual-machines-aws-ssm/</link>
      <pubDate>Mon, 06 Nov 2017 15:15:18 +0000</pubDate>
      <guid>https://theithollow.com/2017/11/06/manage-vsphere-virtual-machines-aws-ssm/</guid>
      <description>&lt;p&gt;Amazon Web Services has some great tools to help you operate your EC2 instances with their Simple Systems Manager services. These services include ensuring &lt;a href=&#34;https://theithollow.com/2017/07/24/patch-compliance-ec2-systems-manager/&#34;&gt;patches are deployed&lt;/a&gt; within maintenance windows specified by you, &lt;a href=&#34;https://theithollow.com/2017/09/26/aws-ec2-systems-manager-state-manager/&#34;&gt;automation routines&lt;/a&gt; that are used to ensure state and &lt;a href=&#34;https://theithollow.com/2017/07/17/run-commands-ec2-systems-manager/&#34;&gt;run commands&lt;/a&gt; on a fleet of servers through the AWS console. These tools are great but wouldn&amp;rsquo;t be be even better if I could use these tools to manage my VMware virtual machines too? Well, you&amp;rsquo;re in luck, because EC2 SSM can do just that and better yet, the service itself is free! Now, if you&amp;rsquo;ve followed along with the &amp;quot; &lt;a href=&#34;https://theithollow.com/2017/10/02/aws-ec2-simple-systems-manager-reference/&#34;&gt;AWS EC2 Simple Systems Manager Reference&lt;/a&gt;&amp;quot; guide you&amp;rsquo;ve probably already seen the goodies that we&amp;rsquo;ve got available, so this post is used to show you how you can use these same tools on your vSphere, Hyper-V or other on-premises platforms.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Move an EC2 Instance to Another Region</title>
      <link>https://theithollow.com/2017/10/23/move-ec2-instance-another-region/</link>
      <pubDate>Mon, 23 Oct 2017 14:12:31 +0000</pubDate>
      <guid>https://theithollow.com/2017/10/23/move-ec2-instance-another-region/</guid>
      <description>&lt;p&gt;Sometimes, you just need to change the data center where you&amp;rsquo;re running your virtual machines. You could be doing this for disaster recovery reasons, network latency reasons, or just because you&amp;rsquo;re shutting down a region. In an on-prem environment, you might move workloads to a different data center by vMotion, VMware Site Recovery Manager, Zerto, Recoverpoint for VMs, Veeam, or one of the other great tools for a virtualized environment. But how about if that VM is running in an AWS region and you want to move it to another region?&lt;/p&gt;</description>
    </item>
    <item>
      <title>Understanding AWS Tenancy</title>
      <link>https://theithollow.com/2017/10/16/understanding-aws-tenancy/</link>
      <pubDate>Mon, 16 Oct 2017 15:00:10 +0000</pubDate>
      <guid>https://theithollow.com/2017/10/16/understanding-aws-tenancy/</guid>
      <description>&lt;p&gt;When it comes to deploying EC2 instances within Amazon Web Services VPCs, you may find yourself confused when presented with those tenancy options. This post aims to describe the different options that you have with AWS tenancy and how they might be used.&lt;/p&gt;
&lt;p&gt;First and foremost, what do we mean by tenancy? Well, tenancy determines who is the owner of a resource. It might be easiest to think of tenancy in terms of housing. For instance if you have a house then you could consider it a dedicated tenant since only one family presumably lives there. However, if you have an apartment building, there is a good chance that several families have rooms in a single building which would be more like a shared tenancy model.&lt;/p&gt;</description>
    </item>
    <item>
      <title>AWS EC2 Simple Systems Manager Reference</title>
      <link>https://theithollow.com/2017/10/02/aws-ec2-simple-systems-manager-reference/</link>
      <pubDate>Mon, 02 Oct 2017 14:07:07 +0000</pubDate>
      <guid>https://theithollow.com/2017/10/02/aws-ec2-simple-systems-manager-reference/</guid>
      <description>&lt;p&gt;Please use this post as a landing page to get you started with using the EC2 Simple Systems Manager services from Amazon Web Services. Simple Systems Manager or (SSM) is a set of services used to manage EC2 instances as well as on-premises machines (known as managed instances) with the SSM agent installed on them. You can use these services to maintain state, run ad-hoc commands, and configure patch compliance among other things.&lt;/p&gt;</description>
    </item>
    <item>
      <title>AWS EC2 Systems Manager - State Manager</title>
      <link>https://theithollow.com/2017/09/26/aws-ec2-systems-manager-state-manager/</link>
      <pubDate>Tue, 26 Sep 2017 14:06:57 +0000</pubDate>
      <guid>https://theithollow.com/2017/09/26/aws-ec2-systems-manager-state-manager/</guid>
      <description>&lt;p&gt;Sometimes you need to ensure that things are always a certain way when you deploy AWS EC2 instances. This could be things like making sure your servers are always joined to a domain when being deployed, or making sure you run an Ansible playbook every hour. The point of the AWS EC2 SSM State Manager service is to define a consistent state for your EC2 instances.&lt;/p&gt;
&lt;p&gt;This post will use a fictional use case where I have a an EC2 instance or instances that are checking every thirty minutes to see if they should use a new image for their Apache website. The instance will check against the EC2 Simple Systems Manager Parameter Store, which we&amp;rsquo;ve discussed in a &lt;a href=&#34;https://theithollow.com/2017/09/11/ec2-systems-manager-parameter-store/&#34;&gt;previous post&lt;/a&gt;, and will download the image from the S3 location retrieved from that parameter.&lt;/p&gt;</description>
    </item>
    <item>
      <title>AWS EC2 Simple Systems Manager Documents</title>
      <link>https://theithollow.com/2017/09/18/aws-ec2-simple-systems-manager-documents/</link>
      <pubDate>Mon, 18 Sep 2017 14:32:16 +0000</pubDate>
      <guid>https://theithollow.com/2017/09/18/aws-ec2-simple-systems-manager-documents/</guid>
      <description>&lt;p&gt;Amazon Web Services uses Systems Manager Documents to define actions that should be taken on your instances. This could be a wide variety of actions including updating the operating system, copying files such as logs to another destination or re-configuring your applications. These documents are written in Javascript Object Notation (JSON) and are stored within AWS for use with theother Simple Systems Manager (SSM) services such as the Automation Service or Run command.&lt;/p&gt;</description>
    </item>
    <item>
      <title>EC2 Systems Manager Parameter Store</title>
      <link>https://theithollow.com/2017/09/11/ec2-systems-manager-parameter-store/</link>
      <pubDate>Mon, 11 Sep 2017 14:15:52 +0000</pubDate>
      <guid>https://theithollow.com/2017/09/11/ec2-systems-manager-parameter-store/</guid>
      <description>&lt;p&gt;Generally speaking, when you deploy infrastructure through code, or run deployment scripts you&amp;rsquo;ll need to have a certain amount of configuration data. Much of your code will have install routines but what about the configuration information that is specific to your environment? Things such as license keys, service accounts, passwords, or connection strings are commonly needed when connecting multiple services together. So how do you code that exactly? Do you pass the strings in at runtime as a parameter and then hope to remember those each time you execute code? Do you bake those strings into the code and then realize that you&amp;rsquo;ve got sensitive information stored in your deployment scripts?&lt;/p&gt;</description>
    </item>
    <item>
      <title>Patch Compliance with EC2 Systems Manager</title>
      <link>https://theithollow.com/2017/07/24/patch-compliance-ec2-systems-manager/</link>
      <pubDate>Mon, 24 Jul 2017 14:05:31 +0000</pubDate>
      <guid>https://theithollow.com/2017/07/24/patch-compliance-ec2-systems-manager/</guid>
      <description>&lt;p&gt;Deploying security patches to servers is almost as much fun as managing backup jobs. But everyone has to do it, including companies that have moved their infrastructure to AWS. As we&amp;rsquo;ve learned with previous posts, Amazon EC2 Systems Manager allows us to use some native AWS tools for management of our EC2 instances, and patch management is no exception.&lt;/p&gt;
&lt;p&gt;EC2 Systems Manager allows you to do patch compliance where you can set a baseline and then based on a defined maintenance window a scheduled scan and deployment can be initiated on those EC2 instances. This assumes that you&amp;rsquo;ve already installed the SSM Agent and setup the basic IAM permissions for the instances to communicate with the Systems Manager service. The details can be found in the previous post.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Run Commands through EC2 Systems Manager</title>
      <link>https://theithollow.com/2017/07/17/run-commands-ec2-systems-manager/</link>
      <pubDate>Mon, 17 Jul 2017 14:05:12 +0000</pubDate>
      <guid>https://theithollow.com/2017/07/17/run-commands-ec2-systems-manager/</guid>
      <description>&lt;p&gt;In a previous post we covered the different capabilities and basic setup of EC2 Systems Manager, including the IAM roles that needed to be created and the installation of the SSM Agent. In this post we&amp;rsquo;ll focus on running some commands through the EC2 Systems Manager Console.&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;ve already got an Amazon Linux instance deployed within our VPC. I&amp;rsquo;ve placed this instance in a public facing subnet and it is a member of a security group that allows HTTP traffic over port 80.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Amazon EC2 Systems Manager Services</title>
      <link>https://theithollow.com/2017/07/10/amazon-ec2-systems-manager-services/</link>
      <pubDate>Mon, 10 Jul 2017 14:05:29 +0000</pubDate>
      <guid>https://theithollow.com/2017/07/10/amazon-ec2-systems-manager-services/</guid>
      <description>&lt;p&gt;We love Amazon EC2 instances because of how easy they are to deploy and we have a huge catalog of templates (AMIs) to choose from which really speeds up our provisioning. But once those instances are up and running it would be really nice to have some methods of managing those instances. Luckily, Amazon has developed several capabilities to help manage Amazon EC2 instances after they&amp;rsquo;ve been deployed. These capabilities are used to execute scripts, manage patches and kick off automation routines within an EC2 instance, directly from the AWS console.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Migrate vSphere VMs to Amazon with AWS Server Migration Service</title>
      <link>https://theithollow.com/2017/06/26/migrate-vsphere-vms-amazon-aws-server-migration-service/</link>
      <pubDate>Mon, 26 Jun 2017 14:05:01 +0000</pubDate>
      <guid>https://theithollow.com/2017/06/26/migrate-vsphere-vms-amazon-aws-server-migration-service/</guid>
      <description>&lt;p&gt;AWS is taking the virtualization world by storm. Workloads that used to get spun up on vSphere are now being deployed in AWS in many cases. But what if you&amp;rsquo;ve got workloads in vSphere that need to be moved? Sure, it probably makes sense to build new servers in AWS and decommission the old ones but sometimes it&amp;rsquo;s OK to lift and shift. Amazon has a service that can help with this process called the AWS Server Migration Service.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Setup Amazon Storage Gateway</title>
      <link>https://theithollow.com/2017/06/13/setup-amazon-storage-gateway/</link>
      <pubDate>Tue, 13 Jun 2017 14:10:17 +0000</pubDate>
      <guid>https://theithollow.com/2017/06/13/setup-amazon-storage-gateway/</guid>
      <description>&lt;p&gt;Amazon&amp;rsquo;s S3 is a cost effective way to store file but many organizations are used to mapping NFS shares to machines for file storage purposes. Amazon Storage Gateways are a good way to cache or store files on an NFS mount and then back them up to an S3 bucket. This post goes through the setup of an AWS Storage Gateway in an EC2 instance for caching files and storing them in an S3 bucket. This same solution (and a similar but different process) can be used to mount block devices through iSCSI or setup a Tape Gateway for backup products.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Setup ADFS for Amazon Web Services SAML Authentication</title>
      <link>https://theithollow.com/2017/05/15/setup-adfs-amazon-web-services-saml-authentication/</link>
      <pubDate>Mon, 15 May 2017 14:10:59 +0000</pubDate>
      <guid>https://theithollow.com/2017/05/15/setup-adfs-amazon-web-services-saml-authentication/</guid>
      <description>&lt;p&gt;It&amp;rsquo;s a pretty common design request these days to have a single authentication source. I mean, do you really want to have to manage a bunch of different logins instead of having to remember one? Also, five different accounts give attackers five different avenues to try to exploit. So many times we use our existing Active Directory infrastructure as our single source of authentication. Amazon Web Services (AWS) needs a way for people to login and will allow you to use your own Active Directory credentials through Security Assertion Markup Language (SAML). This post will walk you through the setup of Active Directory Federation Services (ADFS) on Windows Server 2016 and configuring it to be your credentials for AWS.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Using Packer to Create vSphere and AWS Images</title>
      <link>https://theithollow.com/2017/03/06/using-packer-create-vsphere-aws-images/</link>
      <pubDate>Mon, 06 Mar 2017 15:15:52 +0000</pubDate>
      <guid>https://theithollow.com/2017/03/06/using-packer-create-vsphere-aws-images/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://www.packer.io/&#34;&gt;Packer&lt;/a&gt; is a free tool from &lt;a href=&#34;https://www.hashicorp.com/&#34;&gt;Hashicorp&lt;/a&gt; that allows you to build new images. Keeping base vSphere templates up to date is not too difficult of a task for many, but as we add things like AWS accounts and regions, it&amp;rsquo;s pretty easy to have sprawl to deal with. We&amp;rsquo;d like to make sure that an image in our vSphere datacenter looks the same as an image in our public clouds.&lt;/p&gt;</description>
    </item>
    <item>
      <title>AWS Service Catalog</title>
      <link>https://theithollow.com/2017/02/27/aws-service-catalog/</link>
      <pubDate>Mon, 27 Feb 2017 15:06:51 +0000</pubDate>
      <guid>https://theithollow.com/2017/02/27/aws-service-catalog/</guid>
      <description>&lt;p&gt;Many cloud initiatives require having a portal for users to choose which workloads can be deployed. Think of this as a supermarket full of servers, networks, databases, or all of the above. There are product offerings from VMware, Cisco, RightScale and Redhat, used for these deployment methodologies. If you&amp;rsquo;re an AWS customer though, you&amp;rsquo;ve got your own catalog available from the native AWS tools called the &amp;ldquo;Service Catalog&amp;rdquo; service. This service enables you to deploy and publish &lt;a href=&#34;https://aws.amazon.com/cloudformation/&#34;&gt;CloudFormation templates&lt;/a&gt; for your users so that they don&amp;rsquo;t have to know how RDS, or EC2 instances work. They can select from the catalog and deploy anything you can build in an Amazon CFT. Think of the possibilities.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Pros and Cons of Amazon&#39;s Key Management Service</title>
      <link>https://theithollow.com/2017/02/13/pros-cons-amazons-key-management-service/</link>
      <pubDate>Mon, 13 Feb 2017 15:02:06 +0000</pubDate>
      <guid>https://theithollow.com/2017/02/13/pros-cons-amazons-key-management-service/</guid>
      <description>&lt;p&gt;Not everyone who encrypts data uses a key management solution. Since the days we started worrying about storage of personally identifiable information (PII) we&amp;rsquo;ve had different methods of protecting it. In a small environment, simple PGP (Pretty Good Privacy) keys were used to manually encrypt data and decrypt it. Storing keys for a few different partners that you routinely exchange data with was simple enough to do. But what about today when we&amp;rsquo;re storing sensitive data in databases, on storage volumes and in other people&amp;rsquo;s data centers, like Amazon Web Services. How do we manage numerous keys and make sure that those keys are properly maintained?&lt;/p&gt;</description>
    </item>
    <item>
      <title>AWS Step Functions</title>
      <link>https://theithollow.com/2017/01/17/aws-step-functions/</link>
      <pubDate>Tue, 17 Jan 2017 15:01:40 +0000</pubDate>
      <guid>https://theithollow.com/2017/01/17/aws-step-functions/</guid>
      <description>&lt;p&gt;This year at AWS re:Invent Amazon announced a new service called &lt;a href=&#34;https://aws.amazon.com/step-functions/&#34;&gt;Step Functions&lt;/a&gt;. According to AWS, Step Functions is an easy way to coordinate the components of distributed applications and microservices using visual workflows. That pretty much sums it up! When you&amp;rsquo;ve got a series of small microservices that need to be coordinated, it can be tricky to write this code into each lambda function to call the next function. Step Functions gives you a visual editor to manage the calls to multiple Lambda functions to make your life easier. I&amp;rsquo;ve written about this before on the &lt;a href=&#34;https://www.thinkahead.com/blog/visual-orchestration-aws/&#34;&gt;AHEAD blog&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>AWS PowerShell Console with XAML</title>
      <link>https://theithollow.com/2016/11/29/aws-powershell-console-xaml/</link>
      <pubDate>Tue, 29 Nov 2016 15:05:49 +0000</pubDate>
      <guid>https://theithollow.com/2016/11/29/aws-powershell-console-xaml/</guid>
      <description>&lt;p&gt;I&amp;rsquo;ve always liked the idea of taking a series of Microsoft PowerShell scripts and putting them behind a user interface so that I can give the tool to other users. I&amp;rsquo;m not sure why this idea appeals to me, but probably because it makes me feel like a programmer, if only for a little while. I came across this &lt;a href=&#34;https://foxdeploy.com/2015/04/10/part-i-creating-powershell-guis-in-minutes-using-visual-studio-a-new-hope/&#34;&gt;post&lt;/a&gt; by &lt;a href=&#34;https://twitter.com/foxdeploy&#34;&gt;Stephen Owen&lt;/a&gt; and I had to try it out.&lt;/p&gt;
&lt;p&gt;The project that I picked for this was based on the AWS PowerShell tools that I hadn&amp;rsquo;t used yet. Let&amp;rsquo;s face it, this is a good way to check out two different things, I didn&amp;rsquo;t have much experience with: The AWS PowerShell Tools and XAML for creating GUIs.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Execute vRO Workflow from AWS Lambda</title>
      <link>https://theithollow.com/2016/07/26/vro_from_aws_lambda/</link>
      <pubDate>Tue, 26 Jul 2016 14:00:15 +0000</pubDate>
      <guid>https://theithollow.com/2016/07/26/vro_from_aws_lambda/</guid>
      <description>&lt;p&gt;The use cases here are open for debate, but you can setup a serverless call to vRealize Orchestrator to execute your custom orchestration tasks. Maybe you&amp;rsquo;re integrating this with an &lt;a href=&#34;http://amzn.to/2a0VHhe&#34;&gt;Amazon IoT button&lt;/a&gt;, or you want voice deployments with &lt;a href=&#34;http://amzn.to/2a0VFG8&#34;&gt;Amazon Echo&lt;/a&gt;, or maybe you&amp;rsquo;re just trying to provide access to your workflows based on a CloudWatch event in Amazon. In any case, it is possible to setup an Amazon Lambda call to execute a vRO workflow. In this post, we&amp;rsquo;ll actually build a Lambda function that executes a vRO workflow that deploys a CentOS virtual machine in vRealize Automation, but the workflow could really be anything you want.&lt;/p&gt;</description>
    </item>
    <item>
      <title>AWS Cloud Formation Templates in vRealize Automation</title>
      <link>https://theithollow.com/2016/03/14/aws-cloud-formation-templates-in-vrealize-automation/</link>
      <pubDate>Mon, 14 Mar 2016 14:15:46 +0000</pubDate>
      <guid>https://theithollow.com/2016/03/14/aws-cloud-formation-templates-in-vrealize-automation/</guid>
      <description>&lt;p&gt;Amazon has a pretty cool service that allows you to create a template for an entire set of infrastructure. This isn&amp;rsquo;t a template for a virtual machine, or even a series of virtual machines, but a whole environment. You can create a template with servers, security groups, networks and even PaaS services like their relational database service (RDS). Hey, in today&amp;rsquo;s world, infrastructure as code is the direction things are going and AWS has a pretty good solution for that already.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
