<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>The Basics on My AWS Rocks!</title><link>https://myaws.name/tags/the-basics/</link><description>Recent content in The Basics on My AWS Rocks!</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 31 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://myaws.name/tags/the-basics/index.xml" rel="self" type="application/rss+xml"/><item><title>Wait! IP4 has a cost?</title><link>https://myaws.name/wait-ip4-has-a-cost/</link><pubDate>Sun, 11 Aug 2024 00:00:00 +0000</pubDate><guid>https://myaws.name/wait-ip4-has-a-cost/</guid><description>&lt;p&gt;&lt;strong&gt;Caveat:&lt;/strong&gt; I started this post in April because lots of people were shocked at the cost appearing on their bill. I got half way and though it wasn&amp;rsquo;t worth publishing as the chatter would die down. However 4 months later I am still  seeing people ask what can they do about IPv4 costs so thought I&amp;rsquo;d finish it off.&lt;/p&gt;
&lt;p&gt;So you will know, or should know, that the 1st February 2024 saw AWS introduce charges for all public IPv4 addresses in use within an AWS account.&lt;/p&gt;</description></item><item><title>My bill is how much‽</title><link>https://myaws.name/my-bill-is-how-much/</link><pubDate>Thu, 21 Dec 2023 00:00:00 +0000</pubDate><guid>https://myaws.name/my-bill-is-how-much/</guid><description>&lt;p&gt;One of the most common post by newcomers to AWS seems to be bill shock or unexpected charges.&lt;/p&gt;
&lt;p&gt;Some of this is from using a service with out knowing the costs or forgetting to shut something down and incurring costs for longer than planned.&lt;/p&gt;
&lt;p&gt;Some however is where accounts have been compromised and resources used by someone else.&lt;/p&gt;
&lt;p&gt;So what can you do to prevent this?&lt;/p&gt;
&lt;p&gt;This article will look at ways of securing your account and managing your costs. It is a high level article and doesn&amp;rsquo;t go into every service mentioned in detail, however it should give you enough to protect yourself and point you to further resources.&lt;/p&gt;</description></item><item><title>You put what in a public subnet‽</title><link>https://myaws.name/you-put-what-in-a-public-subnet/</link><pubDate>Tue, 04 Apr 2023 00:00:00 +0000</pubDate><guid>https://myaws.name/you-put-what-in-a-public-subnet/</guid><description>&lt;p&gt;Its great seeing peoples designs for modern solutions and especially serverless. What is more impressive is, where VPC services are in use, they are splitting them out into separate tiers and subnets.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;😕 &lt;strong&gt;But why do so many people put things in public subnets that don&amp;rsquo;t need to be?&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;In this article I&amp;rsquo;ll look at what I think should be in public subnets and why you try not to put anything in a public subnet you don&amp;rsquo;t need to.&lt;/p&gt;</description></item><item><title>Creating a Well-Architected VPC</title><link>https://myaws.name/aws-vpc-101/</link><pubDate>Wed, 20 Apr 2022 00:00:00 +0000</pubDate><guid>https://myaws.name/aws-vpc-101/</guid><description>&lt;p&gt;So this is the first in my posts walking through how to deploy a solution in AWS. Hopefully  you find it useful as VPCs are the foundation for private and secure networking in AWS and an area many struggle. This guide is designed to ensure that your VPC deployments can be Well-Architected and provide a base level of network security but is only one option for VPC layout. While it will meet a vast majority of workloads you might want to review the structure and reduce, or increase, the number of subnets as well as other components.&lt;/p&gt;</description></item><item><title>Useful AWS Training Resources</title><link>https://myaws.name/useful-aws-training-resources/</link><pubDate>Fri, 24 Dec 2021 00:00:00 +0000</pubDate><guid>https://myaws.name/useful-aws-training-resources/</guid><description>&lt;p&gt;One thing I think is important in technology is to never stop learning. For me change in technology is like a river, it never stops flowing, and at times such as re:invent it can feel like a flood. Things are changing so rapidly if you don&amp;rsquo;t keep up to date you will drown in all the announcements and changes.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;&lt;a href="https://explore.skillbuilder.aws/learn"&gt;
 &lt;img src="https://myaws.name/img/post-14/image.png" alt="AWS Skill Builder Home Page"&gt;

&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Hopefully you have all heard about the &lt;a href="https://explore.skillbuilder.aws/learn"&gt;AWS SkillBuilder&lt;/a&gt; website that has over two and a half thousand digital courses in 16 languages. What you may not know is that there is a raft of other training material out there either direct from AWS or others that can help with your learning journey.&lt;/p&gt;</description></item><item><title>Setting up your AWS account</title><link>https://myaws.name/setting-up-your-aws-account/</link><pubDate>Sun, 24 Oct 2021 00:00:00 +0000</pubDate><guid>https://myaws.name/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>Security 101</title><link>https://myaws.name/security-101/</link><pubDate>Mon, 15 Mar 2021 00:00:00 +0000</pubDate><guid>https://myaws.name/security-101/</guid><description>&lt;p&gt;Following on from the &lt;a href="https://myaws.name/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>AWS Foundational Architecture</title><link>https://myaws.name/foundational-architecture/</link><pubDate>Mon, 18 Jan 2021 00:00:00 +0000</pubDate><guid>https://myaws.name/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><item><title>AWS Basics</title><link>https://myaws.name/aws-basics/</link><pubDate>Fri, 01 Jan 2021 00:00:00 +0000</pubDate><guid>https://myaws.name/aws-basics/</guid><description>&lt;p&gt;Lets discuss some of the basics you need to begin to rock your AWS solutions.&lt;/p&gt;
&lt;h1 id="the-principles"&gt;The Principles&lt;/h1&gt;
&lt;h2 id="everything-as-code"&gt;Everything As Code&lt;/h2&gt;
&lt;p&gt;Firstly everything has to be via code! Doing things via the console is not the way to go long term. As soon as you can look at using the Command Line Interface (CLI). Even using the CLI will start to give you a better understanding of how AWS works under the hood and allow you to design and build better solutions. See the links at the bottom on how to install the CLI.&lt;/p&gt;</description></item></channel></rss>