Richard Crowley’s Post

AWS Announces IPv4 Usage Charges! Dive into the details of AWS's latest pricing update, a move that marks a significant shift in how IPv4 addresses are billed. This strategic change aims to encourage efficient usage and transition to IPv6, impacting developers and businesses alike. https://lnkd.in/eE_fFzUk

Interesting - like the commentary about AWS moving to IPv6 at a glacial pace. That pretty much describes most enterprises. Total status and complacency. There just has not been sufficient external drivers to incent the work.

What's new at AWS 📢 ⚕ #AmazonECS now supports AWS Graviton-based Spot compute with AWS Fargate Spot. ⚕AWS Graviton processors are custom-built by AWS to deliver the best price-performance for cloud workloads. ⚕This capability helps customers to run fault-tolerant Arm-based applications with up to 70% discount compared to Fargate prices. ⚕Since Amazon ECS with AWS Fargate enables customers to deploy and build workloads at scale in a serverless manner. ⚕In addition to that, with this feature, customers can further optimize for costs by running fault-tolerant Arm-based workloads on AWS Fargate Spot. ⚕To get started leveraging this feature: 💥 Configure task definition with cpu-architecture = ARM64 💥 Choose FARGATE_SPOT as the capacity provider. ⚕This new Fargate spot leverages the spare AWS Graviton-based compute capacity available in the AWS cloud for running service or task. ⚕This capability is now available on AWS Fargate platform version 1.4.0 or higher. ⚕Most importantly Amazon ECS on AWS Fargate capacity providers, supported to use both Fargate and Fargate Spot capacity with Amazon ECS tasks. 📌 Explore more about Amazon ECS Fargate: https://lnkd.in/ek5EFXB4 #aws #awscloud #ecs #fargate #serverless #spot #whatsnew #learning #cloudarchitect

Another step in the right (IPv6) direction :)

For those studying system design w/ AWS, there's this card game developed by Amazon which is pretty fun! It's called Card Clash and there's a demo here: https://lnkd.in/gcsgQWwX Gotta vendor lock the kids when they are young, am I right? 😆 #aws #amazon #systemdesign #fullstack

🚀Week Nine: Exploring AWS Global Infrastructure and EC2 Services This week, I delved into AWS's global infrastructure, including regions and availability zones, and explored how to use EC2 services for scalable computing. Here are the key points I covered: 🔹 Global Infrastructure ➔Region and Availability Zone: Regions are isolated geographical areas with multiple Availability Zones (AZs) for fault tolerance and stability. Importance of Region Setup: Reduces latency, supports disaster recovery, and meets compliance requirements. ➔Local Zones: Extend AWS regions for low-latency access, ideal for applications like gaming and real-time communications. 🔹 EC2 Services Getting Server on Rent: Customize virtual servers with options for CPUs, storage, OS, RAM, and more. 🔹 Accessing EC2 Remotely: ➔Windows 10: Use AWS Management Console and SSH clients like PuTTY. ➔Kali Linux: Connect using the SSH command in the terminal. Deploying Applications: Install web servers and deploy applications accessible via web browsers. 🔹 Automation: Use user data and shell scripts for automated configuration and deployment tasks. 🔹 For a detailed walkthrough of my AWS journey, read my full blog post here: https://lnkd.in/dSpJUEyr Thanks for following along! 🚀 #AWSCloudPractitioner #CloudComputing #LearningJourney #CareerGrowth #CloudEngineering

An increasing number of organizations are adopting IPv6 in their environments, driven by the public IPv4 space exhaustion, private IPv4 scarcity, and the need to provide service availability to IPv6-only clients. While undergoing this transformation, customers sometimes find it difficult to assess application behavior in IPv6-enabled environments on AWS. In this blog post, we show how you can leverage Amazon VPC Lattice to adopt IPv6 for your workloads on AWS, and seamlessly migrate from an existing IPv4-only to an IPv6-enabled service architecture. #AWS #Amazon #VPC #Lattice #IPv6 #IPv4

I made some tests with EC2 on IPv6 VPC is DualStack with EngressOnly IGW, no NAT. We can ssh into EC2 instances with IPv6 addresses ✔ Instances in private Subnet can communicate to the Internet with the EngressOnly IGW.✔ A webserver also works fine with IPv6 ( in public or private Subnet)✔ AAAA-Recordset in Route53 will route to the instance ( CNAME not) ✔ Loadbalancer also works - and Route53 A Alias ✔ SessionsManager does not yet support IPv6 ✖ Please have a look in this blog https://lnkd.in/dWcX-v8W A blog to get an overview on IPv6 https://lnkd.in/d3kWwbrA Github Repo IPv6 (under construction) https://lnkd.in/dH2DRzwf SCC Brasil Blog Overview https://lnkd.in/dCQFPTdA #sccbrasil #oscloudgurus #aws #awscommunitybuilders

Hey there everyone! You might or might not have heard, but AWS is charging for AWS-provided IPv4 now! In an effort to move people to IPv6, they've opted to bill for it. While the $0.005/hr charge might not be much on the surface, it could be an annoyingly large expense at scale for big organizations, and might make a noticeable difference to the smallest users as well. In this article, I compile some resources about it to help you help others navigate the road to IPv6. Fortunately there are some pretty smart AWS engineers that are way ahead on how to do it and have already put together some awesome resources about it. Take a look and let me know what you think about it in the comments. #costoptimization

Ever heard of AWS Lambda@Edge? It's like having mini-servers scattered around the globe, ready to spring into action. They run your code closer to your users, making your app snappier. But watch out - each invocation costs you, and those costs can add up faster than you can say "globally distributed computing"! Question for you: Have you experimented with Lambda@Edge? How did it impact your performance and costs?