<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Foundations on My AWS Rocks!</title><link>https://www.myaws.rocks/tags/foundations/</link><description>Recent content in Foundations on My AWS Rocks!</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 24 Oct 2021 00:00:00 +0000</lastBuildDate><atom:link href="https://www.myaws.rocks/tags/foundations/index.xml" rel="self" type="application/rss+xml"/><item><title>Setting up your AWS account</title><link>https://www.myaws.rocks/setting-up-your-aws-account/</link><pubDate>Sun, 24 Oct 2021 00:00:00 +0000</pubDate><guid>https://www.myaws.rocks/setting-up-your-aws-account/</guid><description>&lt;p&gt;So you want to get your own AWS account and get started with hands on deployments. What should you do?
&lt;h2 id="getting-started"&gt;Getting Started&lt;/h2&gt;
&lt;p&gt;Firstly take a look at the AWS &lt;a href="https://aws.amazon.com/getting-started/"&gt;Getting Started Guide&lt;/a&gt;. In particular follow at least the first 3 steps of the setting up your environment. This will go through account creation, securing your root account and creating an admin account for you to use on a daily basis.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;a href="https://aws.amazon.com/getting-started/"&gt;&lt;strong&gt;How to Setup Your Development Environment for AWS | Introduction&lt;/strong&gt; &lt;/br&gt;
Learn how to setup your development environment for AWS. This tutorial includes setting up and securing your account, installing the AWS CLI, and getting started with Cloud9.&lt;/a&gt;&lt;/p&gt;</description></item><item><title>CloudFormation 101</title><link>https://www.myaws.rocks/cloudformation-101/</link><pubDate>Thu, 01 Apr 2021 00:00:00 +0000</pubDate><guid>https://www.myaws.rocks/cloudformation-101/</guid><description>&lt;p&gt;In this post we will look at the basics of CloudFormation, what you need to know and how to get started in writing templates.&lt;/p&gt;
&lt;p&gt;
 &lt;figure&gt;
 &lt;img src="https://www.myaws.rocks/img/post-8/cloudformation.png" alt="Image of a cloud formation template"&gt;
 &lt;center&gt;&lt;figcaption&gt;AWS CloudFormation Template&lt;/figcaption&gt;&lt;/center&gt;
 &lt;/figure&gt;

&lt;/p&gt;
&lt;p&gt;So you may be asking why I am writing a post about template basics when I have said I&amp;rsquo;ll try not repeat information available on AWS.&lt;/p&gt;
&lt;p&gt;Two reasons. Primarily to demystify the template and secondly to provide pointers to resources you might find useful as you improve your CloudFormation knowledge.&lt;/p&gt;</description></item><item><title>Security 101</title><link>https://www.myaws.rocks/security-101/</link><pubDate>Mon, 15 Mar 2021 00:00:00 +0000</pubDate><guid>https://www.myaws.rocks/security-101/</guid><description>&lt;p&gt;Following on from the &lt;a href="https://www.myaws.rocks/foundational-architecture/"&gt;foundational architecture&lt;/a&gt; post I thought I&amp;rsquo;d give a dive into security of the AWS cloud. For me this is the most important element to understand before even creating an AWS account as if you get this wrong it can be costly in more ways than one. There are a few items that need to be looked at when considering security. These include, but are not limited to:&lt;/p&gt;</description></item><item><title>Why use the AWS Well-Architected Framework</title><link>https://www.myaws.rocks/well-architected-part2/</link><pubDate>Mon, 15 Feb 2021 00:00:00 +0000</pubDate><guid>https://www.myaws.rocks/well-architected-part2/</guid><description>&lt;p&gt;This is the second in a three part series on the AWS Well-Architected Framework. It is based on my presentation at the AWS Thames Valley user group &lt;strong&gt;&amp;ldquo;How to design well when there is no rule book&amp;rdquo;&lt;/strong&gt; . In the first part of this series I looked at what the Well-Architected Framework is. In this part we will look at why you should use the Well-Architected Framework.&lt;/p&gt;
&lt;p&gt;I split the &lt;strong&gt;what&lt;/strong&gt; of the framework into 3 categories; Cloud Roadmap, Design Principle; Cloud Assessment.&lt;/p&gt;</description></item><item><title>What is the AWS Well-Architected Framework</title><link>https://www.myaws.rocks/well-architected-part1/</link><pubDate>Mon, 01 Feb 2021 00:00:00 +0000</pubDate><guid>https://www.myaws.rocks/well-architected-part1/</guid><description>&lt;p&gt;
 &lt;figure&gt;
 &lt;img src="https://www.myaws.rocks/img/post-4/Well-Architected.jpg" alt="The AWS Well Architected elements shown pictorally"&gt;
 &lt;center&gt;&lt;figcaption&gt;AWS Well Architected elements&lt;/figcaption&gt;&lt;/center&gt;
 &lt;/figure&gt;

&lt;/p&gt;
&lt;p&gt;This is the first in a three part series on the AWS Well-Architected Framework. It is based on my presentation at the AWS Thames Valley user group &lt;strong&gt;&amp;ldquo;How to design well when there is no rule book&amp;rdquo;&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;This first part looks at what the Well-Architected Framework is.&lt;/p&gt;
&lt;p&gt;On the &lt;a href="https://aws.amazon.com/architecture/well-architected"&gt;AWS website&lt;/a&gt;they describe the framework as:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;The AWS Well-Architected Framework describes the key concepts, design principles, and architectural best practices for designing and running workloads in the cloud. By answering a set of foundational questions, you learn how well your architecture aligns with cloud best practices and are provided guidance for making improvements.&lt;/p&gt;</description></item><item><title>AWS Foundational Architecture</title><link>https://www.myaws.rocks/foundational-architecture/</link><pubDate>Mon, 18 Jan 2021 00:00:00 +0000</pubDate><guid>https://www.myaws.rocks/foundational-architecture/</guid><description>&lt;p&gt;When building a house, the most important thing to get right is the foundations. With out a good foundation everything that is built on top will have issues and, worse case, completely fail. Building IT solutions is no different. We have to ensure the basic foundations are in place in order to build good solutions for the business we are working for.&lt;/p&gt;
&lt;p&gt;Often I see organizations trying to implement the foundations once they have built the first few systems or they realize that &amp;ldquo;this cloud craze is real&amp;rdquo;. Many times it is after a proof of concept has suddenly become a production system. What ever the reason for the delay it always causes rework, at a cost to the business, and can cause friction or resentment from engineers who implemented the first solutions.&lt;/p&gt;</description></item></channel></rss>