Episoder

  • AWS offers many purpose-built databases--meaning each "specializes" in certain types of use cases. DynamoDB is the primarily NoSQL offering, being used for high-traffic web applications, e-commerce and gaming. It's highly scalable, performant, and offers a really flexible key-value schema.In this hands-on tutorial, we'll create our first DynamoDB table through the AWS Console, and then add two items, illustrating just how flexible the schema is. All in less than 5 minutes!Here's a breakdown of this video:What is DynamoDB and why would you use it?An example schema for DynamoDBWhat is a key-value pair database?Creating our first DynamoDB table from the AWS ConsoleCreating items in our DynamoDB tableUnderstanding how flexible schemas are in DynamoDB (especially compared to a relational database)

  • Amazon Web Services (Web) has a huge global infrastructure, with millions of resources used by customers all over the world. As you’re building and deploying your own applications, how do you ensure that your resources are isolated from everything else out there?An Amazon Virtual Private Cloud (VPC) is effectively your own private network within AWS. This is what separates your resources from everything else. In this video, I’ll provide an overview of networking basics in AWS (VPC, subnets, internet gateway), dig into some detail about CIDR notation and how IP addressing works within a VPC, and wrap up with a brief discussion of network access control lists (ACLs) and security groups.Here's a breakdown of the video:Overviewing the need for a Virtual Private Cloud (VPC)What does networking in AWS have to do with a parking lot?Basic AWS networking concepts: VPC, public and private subnets, routes, internet gatewayVPCs in relation to regions and availability zonesBasics of CIDR notation and IP addressesInternet Gateway and NAT GatewayNetwork Access Control Lists (ACLs) and Security Groups

  • Mangler du episoder?

    Klikk her for å oppdatere manuelt.

  • In AWS, what’s with all the different IP addresses (Private, Public, Elastic), and how does CIDR notation work?In this video, I’ll explain in simple terms how it all works. We’ll see the differences between the types of IP addresses, and then get into details of CIDR notation (subnet masks and RFC 1918 ranges) and how that all works.Here's a breakdown of the video:What the heck are private IP addresses, public IPs, Elastic IPs and CIDR notation?The differences between IP addresses, for beginnersThe anatomy of an IP address and binary octetsHow CIDR notation works, with examplesCIDR subnet mask quick reference tableA handy site to bookmark: cidr.xyzRFC 1918 private ranges

  • Amazon Simple Storage Service (S3) can be used as inexpensive object storage (think: files, images, videos, logs, etc.). But did you know it can also be used to host a static website? Static meaning no server-side code, but it's perfect for simple HTML, images and even some client-side scripts.In a hands-on tutorial, I'll show you how to create a bucket, enable it for static website hosting, update permissions, and then upload a simple html file and image. Then voila-our website is working!The JSON code for the bucket policy can be found here: https://docs.google.com/document/d/1Y9Vjom6lbdKdfbw672FWGJ0WVO8gbemFUMsE72LqDac/edit?usp=sharing.Here's a breakdown of the video:Host a static website on Amazon S3 for free or almost free!Reviewing the Free Tier for Amazon S3S3 can only host static websites (no server-side code)Creating a new S3 bucket to host our websiteEnabling static website hosting on the S3 bucketAccess denied! Allowing public access to the bucketUpdating the bucket policy to allow read access to everyoneCreating the HTML pages for your static websiteUploading the index.html and image files to the S3 bucketViewing the static webpage in S3Deleting the S3 bucket

  • UPDATED version of the Wild Rydes project that uses GitHub (rather than CodeCommit), Amplify Gen 2, and Node 20.x.When you’re new to AWS, it can be difficult to wrap your head around ALL the services available, and how they actually fit together to build a working application. Or maybe you're just looking for a more robust project you can put on your resume? Well, you've come to the right place! That’s what we’re tackling in this video! In this hands-on tutorial, I’ll walk you through how to build a ride sharing app (for unicorns!), pulling from the AWS Wild Rydes sample project. We’ll use seven different services—GitHub, Amplify, Cognito, Lambda, IAM, API Gateway and DynamoDB—talking about why/where to use them, and how to get them to work with each other. As we go, we’ll build out each of the services, resulting in a fully-functioning ride sharing application when we’re done.🌟***WHAT YOU NEED TO FOLLOW ALONG***🌟• A text editor or place to make notes• An AWS account, logged in to the AWS Console as a user with admin access• Some basic knowledge of AWS is preferable, but you can still follow along if you’re an absolute newbie• A GitHub account• The code from my GitHub repo: https://github.com/tinytechnicaltutorials/wildrydes-siteHere's a breakdown of the video:Give us more AWS project videos!Overviewing the completed Wild Rydes application (an AWS sample project)A list of all the services used in the applicationWhat will this cost me?What you need to follow along (tools and accounts)High-level requirements for the applicationHow to copy the application code from my GitHub repository to yoursCreating a new GitHub repo using a templateCreating a new app for hosting in AWS AmplifyTesting out the Amplify deployment by launching our websiteUpdating code in GitHub to kick off CI/CD in AmplifySetting up Amazon Cognito for user authenticationHow authentication works in Amplify Gen 2Creating a new user pool in Amazon CognitoUpdating the app configuration file to use the Amazon Cognito user poolTesting Cognito integration by doing user registration and loginImplementing ride sharing functionality with Lambda and DynamoDBCreating a new DynamoDB tableCreating an IAM role to be used for a Lambda execution role, allowing PutItem on DynamoDB tableCreating a new Lambda function to choose a unicorn and write the ride sharing info to DynamoDBDeploying Lambda code and executing a test eventTesting that items are saved to the DynamoDB tableSetting up API Gateway to invoke the ride sharing functionalityCreating a new REST API in API Gateway to invoke a Lambda functionCreating an authorizer so API Gateway can work with CognitoCreating a resource and POST method in API Gateway for Lambda integrationEnabling CORS (Cross Origin Resource Sharing) for the API GatewayDeploying the API from API GatewayUpdating the config file for the new Invoke URL from API GatewayTesting our final application—WOOT!IMPORTANT!! Delete your resources (I’ll show you how)

  • Unless you’ve been living under a rock, you’ve certainly heard of containers and how popular they’ve become for doing software development. But what exactly are they, what are the benefits of using them, and what does that look like in AWS?In this high-level overview, I describe all of those things. We’ll look at how containers differ from virtual machines, and then dig into the specific container-related services from AWS: Elastic Container Service (ECS), Elastic Kubernetes Service (EKS), Fargate, and Elastic Container Registry (ECR).Here's a breakdown of the video:Video introductionWhat the heck are containers and how can they help me?Containers explained, and contrasted with virtual machinesDocker and AWSAmazon Elastic Container Service (ECS) basicsAmazon Elastic Kubernetes Service (EKS) basicsLaunch types for containers, including serverless FargateAmazon Elastic Container Registry (ECR)

  • In this video, we’ll run multiple containers and balance traffic across them using an Application Load Balancer (ALB).In a hands-on tutorial, we’ll create two security groups—one for the ALB and one for the ECS service. Then we’ll create an ECS cluster and task definition that pulls in an NGINX container from the Amazon Elastic Container Registry (ECR) Public Gallery. From there, we’ll create the ECS service, and while doing that, we’ll create the Application Load Balancer. But there’s a gotcha here! Make sure you stay to the end to find out how to get the load balancing working properly.Here's a breakdown of the video:Overviewing what we’ll be building, and the need for a load balancer with ECSUnderstanding the security groups we need to get the load balancer working in ECSCreating two security groups in the AWS ConsoleCreating an ECS ClusterCreating a new task definition for NGINXDeploying the ECS service Creating the load balancer to work with the ECS service (warning: There’s a gotcha here!)Testing our load balancerThe load balancer doesn’t work!Fixing the security groups so that our load balancer worksNow the load balancer works with our ECS containers!Summarizing what we’ve builtIMPORTANT!! Deleting your ECS task, service, cluster, task definition, load balancer and security groups

  • Route 53 is Amazon’s managed Domain Name System (DNS). You can use it to register (or transfer) domain names, and manage how traffic is routed to public and private resources.In this hands-on tutorial, I’ll explain in simple terms how it all works. We’ll take a look at common DNS record types, including A Record, CNAME Record, and the Alias that allows you to redirect traffic to AWS resources (we’ll point to an Elastic Beanstalk application).Here's a breakdown of the video:Introducing Route 53, Amazon’s managed DNS serviceOverviewing the need for the Domain Name System (DNS) to locate web resourcesUsing Route 53 to register a domain namePublic and private hosted zones in Route 53Overviewing the A Record, CNAME Record, and Alias in AWSCreating a new DNS A Record to direct traffic from a subdomain to an IP addressCreating a new DNS A record with AWS alias to direct traffic to an Elastic Beanstalk app

  • Load balancing is a key component to any application that’s highly available and scalable. In AWS, an Elastic Load Balancer distributes traffic across multiple instances, and even multiple availability zones if you choose. There are three kinds of load balancers in AWS: Application Load Balancer, Gateway Load Balancer and Network Load Balancer. This video will focus on Application Load Balancers.In this hands-on tutorial, I’ll walk you through how set up two new Linux EC2 instances that are used as web servers. Then we’ll create an Application Load Balancer and a Target Group to balance traffic between the two instances.Here's a breakdown of the video:Overviewing the resources we’ll be building and how they work togetherCreating two new Linux EC2 instances as web serversCreating an Application Load Balancer in AWSCreating a Target Group for the Load Balancer to route traffic toTesting the Load BalancerSimulating an unhealthy instance to show how Load Balancing behaves

  • You might know how to create a simple application load balancer that routes traffic to a single target group. But what if you have a more complicated use case? For example, what if you need to route GET and POST requests differently? Or route differently based on the user’s browser? Or the destination path? Or something in the query string?For that, you’ll need to work with multiple target groups, setting up listener rules to route traffic to the appropriate place.In this hands-on tutorial, I’ll walk you through how set up a load balancer that uses two target groups. The load balancer will route traffic based on listener rules that we’ll define.Here's a breakdown of the video:Overviewing the load balancer we’ll be building togetherExplaining the setup for the EC2 InstancesViewing the index.html pages for the EC2 instancesCreating two target groups through the AWS ConsoleCreating the application load balancer with a default HTTP listenerAdding load balancer listener rules to route to a second target groupOverviewing all six listener rule condition types (host-header, path-pattern, http-header, http-request-method, query-string, source-ip), with examplesCreating a listener rule for query-string, forwarding to a second target groupCreating a listener rule for http-header and User-Agent, forwarding to a second target groupEditing and deleting listener rulesCreating a listener rule for my source-ip, returning a fixed response for 403 forbiddenIMPORTANT! Deleting your load balancer, target groups and EC2 instances

  • You might know how to work with a simple application load balancer that routes traffic between two EC2 instances. But what if you need 20 instances? Or 200? How can you manage that without a lot of administrative overhead?The answer is auto scaling groups (ASGs)! ASGs can scale up and down automatically based on load. You just set up the parameters and rules, and the instances will be spun up or down for you. And this ties in seamlessly with an application load balancer, which we’ll be working with in this video.In this hands-on tutorial, I’ll walk you through how to create and configure an auto scaling group that works with an application load balancer and a single target group.Here's a breakdown of the video:Reviewing what we learned previously about load balancersIntroducing auto scaling groups (ASGs)Reviewing the demo setup so farReviewing the load balancer and target group in the AWS ConsoleCreating a new auto scaling group in the AWS ConsoleCreating a new launch template in the AWS ConsoleResuming the creation of the auto scaling groupViewing the instances and activity in an auto scaling groupSimulating an unhealthy EC2 instance in the auto scaling groupIMPORTANT! Deleting your auto scaling group and launch template

  • The world runs on APIs (application programming interfaces) these days, and it’s likely that you’ll need to build APIs for your own application, or for others to consume.In AWS, it’s common to create Lambda functions to do a very specific task. But those Lambda functions aren’t going to be exposed to the outside world. Instead, you’d want the requests to go to an API endpoint, which will then call Lambda. And API Gateway is what allows you to do that.In this hands-on tutorial, we’ll build a simple “hello world” Lambda function, and then create an API Gateway GET method that calls it. And be sure to stick around to the end where I’ll show you how to delete the resources.Here's a breakdown of the video:Creating a Hello World Lambda function so we can call it from API GatewayCreating a new REST API in API Gateway Creating a GET method in API Gateway to call our Lambda functionTesting the API Gateway GET methodDeploying our API in API GatewayInvoking the API Gateway URL to call our Lambda functionIMPORTANT! Delete your Lambda function and API

  • How much will this cost? It's one of the most-asked questions related to Amazon Web Services (AWS). And whether you need to estimate for your own side projects, or your boss is asking you to come up with an estimate for the whole company to migrate to AWS, it would be nice to have a calculator to help.And you're in luck! In this hands-on tutorial, I'll give you a basic run-through of the AWS Pricing Calculator (at https://calculator.aws), showing you how to create a new estimate and then add two services (EC2 and DynamoDB) with On-Demand Pricing. At the end, we'll have an estimate that includes monthly and yearly costs.Here's a breakdown of the video:I need to calculate AWS costs. How do I get started? The AWS Pricing Calculator!Adding EC2 instances to a new cost estimateAdding a DynamoDB database to the cost estimateViewing the final cost estimate for AWS services

  • Amazon CloudFront is a content distribution network (CDN) that caches content like images and videos, making them faster to load. With points of presence all over the world, you can easily get your content closer to you and your users.In this hands-on tutorial, we create a simple website (an index.html page with a picture) and upload the files to an S3 bucket. Then we create a new CloudFront distribution that points to the S3 bucket, setting up new origin access control. And then voila! We can load our website using the CloudFront distribution domain name.✔ If you want to use the code in the index.html file, you can find it here: https://drive.google.com/file/d/13WGDEQwJNyl3ucIjzzIfhuApAQYyWmhz/view?usp=sharing Here's a breakdown of the video:Overviewing CloudFront and its locationsHow CloudFront works (using a cat picture, of course)What we're going to build together in CloudFrontCreating an S3 bucket and uploading an index.html page and pictureAccess denied error trying to access files in an S3 bucketCreating a new CloudFront distributionChoosing the origin domain for CloudFrontSetting up origin access control for CloudFrontUpdating the S3 bucket policy for CloudFront accessTesting our webpage and picture through CloudFront distribution domain nameIMPORTANT! Delete your CloudFront distribution, origin access and S3 bucket

  • In AWS, a Virtual Private Cloud (VPC) is a private network for your resources. When you create a new account, a default VPC is created automatically. But it's a best practice to use a custom VPC for your resources, which means you can end up with multiple VPCs. So how can they talk to each other?In this hands-on tutorial, I'll walk you through how to peer two VCPs, which essentially lets them act as a single network, with EC2 instances being able to communicate across VPCs. We'll start by creating an EC2 instance in each VPC, then creating a peering connection between the two, and finally updating the route tables for each VPC.If you want to use the User Data script to create an HTML page on the EC2 instances, check out the script here: https://docs.google.com/document/d/1s8iNjZkDwq42fnpM-AeE27F1FEtbRYP24RicUi0VIbk/edit?usp=sharing Here's a breakdown of the video:What is VPC peering in AWS and why would you use it?Creating an EC2 instance in each VPCTesting the connection between instances in two VPCsCreating a new VPC peering connection and accepting the requestModifying the route tables for the VPC peering connectionTesting the updated connection between the two VPCsIMPORTANT! Delete your resources!

  • Elastic Beanstalk is Amazon’s “platform as a service” solution, allowing you to “just write code,” and then Elastic Beanstalk does all the work of setting up and maintaining the underlying infrastructures (EC2 instances, load balancers, auto-scaling groups and more).In this hands-on tutorial, we’ll deploy a sample Python web application (built-in with Elastic Beanstalk), setting up an application and an environment (and first of all, what’s the difference?). After deployment is complete, we’ll take a look at our masterpiece of an app, see what happened behind the scenes, and then finally, we’ll delete the application and environment.Here's a breakdown of the video:Getting started with Elastic Beanstalk by creating a new applicationThe difference between an application and environment in Elastic BeanstalkCreating a new application in Elastic BeanstalkCreating and configuring a new environment (with sample code) in Elastic BeanstalkService role vs. EC2 instance profileCreating a new service role in Elastic BeanstalkCreating a new EC2 instance profile for an instance in Elastic Beanstalk, no more "instance profile does not exist" errorsSelecting an existing EC2 instance profile from Elastic BeanstalkSetting up network and database for Elastic BeanstalkConfiguring instances in Elastic BeanstalkWatching deployment progress with Elastic BeanstalkViewing the application and behind-the-scenes with Elastic Beanstalk after deploymentIMPORTANT! Deleting the application and environment in Elastic Beanstalk

  • Amazon CloudWatch is the ultimate tool for monitoring and managing your resources in AWS. From metrics to logs, alarms to dashboards, there are lots of ways to collect and view data about your environment.In this short video, I’ll provide an overview of CloudWatch, how metrics work (including basic vs. detailed monitoring, and standard vs. high resolution). Then we dive into the AWS Console for a tour of some EC2 metrics.Here's a breakdown of the video:Why Amazon CloudWatch?Core capabilities of CloudWatchIntroducing CloudWatch metrics (stored in namespaces)Example metric for CPUUtilization of an EC2 instanceBasic vs. detailed monitoring in CloudWatch (1 minute vs. 5 minute)Metric resolution in CloudWatch (standard vs. high resolution)Examples: Using basic and detailed monitoring combined with standard and high resolutionViewing CloudWatch metrics in the AWS Console, and for a specific regionWorking with EC2 Per-Instance Metrics (CPUUtilization, NetworkIn, NetworkOut)Working with CloudWatch charts, time ranges, zooming in and outBasic and detailed monitoring and metric resolution in the ConsoleChanging CloudWatch chart types and other available actionsViewing CloudWatch metrics from an EC2 instanceEnabling detailed monitoring from EC2 (for publishing data every 1 minute)

  • People often ask me what AWS projects they can build to put on their resume/CV, and how to showcase their AWS skills to potential employers. Well, how about actually building the resume itself on AWS? That's what we'll do in this video!In a hands-on tutorial, I'll walk you through how to build a simple resume/CV that uses HTML, CSS and JavaScript (with a little help from ChatGPT). Then we'll upload the files to an S3 bucket that we configure for static website hosting, with public access. From there, we'll move to Route 53 so we can use a custom domain on our resume (and if you have a domain from an external provider like GoDaddy or NameCheap, I'll show you how to get started with that). Finally, we'll set up an SSL/TLS certificate with AWS Certificate Manager, and then create a CloudFront distribution (that points to S3) where we can apply the certificate.In the end, you'll have a fully-working online resume that you can share with friends, family and potential employers.🤓Here's all the code and resources you'll need:• HTML, CSS and JavaScript files (3 total, in a zip file) that you can use as a starting point: https://drive.google.com/file/d/1LyJyHE_oNpZnw9FbLlqpaPTPvSvh9JSt/view?usp=sharing• S3 bucket policy to allow public read access to your files: https://docs.google.com/document/d/1Y9Vjom6lbdKdfbw672FWGJ0WVO8gbemFUMsE72LqDac/edit?usp=sharing• LinkedIn article if you need help using a domain name from an external provider like GoDaddy: https://www.linkedin.com/pulse/pointing-third-party-registrar-aws-route-53-guilherme-renkel-wehmuth/🤓 A written tutorial for this project: https://www.freecodecamp.org/news/aws-project-build-a-resumeHere's a breakdown of the video:A sneak peek at the resume we'll be building on AWSWhy you should watch this and build out your own resumeOverview of what we're building and the services we'll useHow much will this cost?Creating HTML, CSS and JavaScript files-with the help of ChatGPTHow to use the code that I provideCreating an S3 bucketChoosing a name for the S3 bucket that will work with Route 53Configuring the S3 bucket for static website hostingCreating a bucket policy to allow public read access in the S3 bucketUploading resume code files to the S3 bucketTesting things out with the S3 bucket website endpointRegistering a domain name with Route 53How to work with domains from external providers, like GoDaddy or NameCheapCreating an A Record in Route 53 to point to an S3 bucket websiteViewing the status of DNS propagation in Route 53Requesting a public SSL/TLS certificate in AWS Certificate ManagerHow to do DNS validation for a public SSL/TLS certificate in AWS Certificate ManagerUsing an SSL/TLS certificate for a website in AWSCreating a CloudFront distribution to point to our static website in S3Launching the CloudFront distribution domain nameUpdating the A Record in Route 53 to point to the CloudFront distributionReviewing the final masterpiece of what we built-nice work!IMPORTANT!! Delete your resources (I'll show you how)

  • When it comes to pricing for Amazon EC2 instances (virtual machines), there's no shortage of options. In this video, I break down the details and do a side-by-side comparison of On-Demand, Spot, Reserved Instances and Savings Plans (EC2, Compute and SageMaker).After reviewing the theory together, I'll take you out to the AWS Console for a hands-on demo on how to get started with each.🤓 TIP: If you're working on an AWS certification like Certified Cloud Practitioner or Certified Solutions Architect Associate, then you definitely want to understand the pricing details covered in this video.Here's a breakdown of the video:Amazon EC2 pricing can be complicatedPricing for AWS on-demand EC2 instancesPricing for AWS Spot instancesPricing for AWS Reserved instancesPricing for AWS Savings PlansComparison of AWS Reserved Instances vs. Savings PlansComparison of AWS Savings Plans – EC2 vs. Compute vs. SageMakerCreating an EC2 Spot Instance in the AWS ConsoleCreating an EC2 Reserved Instance in the AWS ConsoleWorking with AWS Savings Plans (EC2, Compute and SageMaker)

  • If you want to create and host a simple static website (meaning no server-side code), it’s easier than ever with AWS Amplify Hosting and Amazon S3. This is the new recommended way to do things. And you can do it for free (if you’re part of the Free Tier) or for only pennies outside of the Free Tier.Amazon Simple Storage Service (S3) is used as inexpensive object storage (think: files, images, videos, logs, etc.). And then Amplify gives you the actual hosting part of things, along with many additional features like the ability to use a custom domain, to use custom headers, get monitoring and more.In this hands-on tutorial, I’ll show you how to create an S3 bucket, create a new Amplify app that points to the bucket, and then how to make updates to the website once it’s deployed. Also be sure to stick around to the end where I’ll show you how to delete all the resources we created.🌟***WHAT YOU NEED TO FOLLOW ALONG***🌟• An AWS account• The index.html page used in the video can be found here: https://drive.google.com/file/d/1O0PMMRr8YNy-Le09YNg-XGaZ_-78SthD/view?usp=sharingHere's a breakdown of the video:Host a static website on Amazon S3 and Amplify for free or almost free!Reviewing the index.html file and image for a simple static websiteWhat will this cost? Reviewing the Free Tier for Amazon S3 and AWS AmplifyCreating a new S3 bucket to host our website filesCreating a new Amplify app from the S3 Console to host static files from S3Creating a new Amplify app from the Amplify Console to host static files from S3Viewing the Amplify application URLThe S3 bucket policy that is automatically created for usMaking updates to website files and re-deploying the changesWhy use Amplify Hosting for a static website with S3?Using a custom domain name with a static Amplify and S3 appAdditional features available with AWS Amplify Hosting for a static websiteIMPORTANT! Deleting the Amplify app and S3 bucket