• Building a self-synchronizing Bedrock knowledge base with S3 Vector

    This post demystifies the process of setting up S3 Vector as Bedrock Knowledge Base by walking through complete implementation in CloudFormation. Examining the infrastructure as code will reveal components, dependencies, and permissions required—bringing full transparency to the "magic" that happens when the same is build from AWS console.
  • If you must have NAT, make it regional

    Shortly after I published my post about how "You don’t need NAT gateway to deploy Lambda into VPC", AWS announced Regional NAT Gateway. Whilst IPv6 eliminates the need for NAT entirely, Regional NAT Gateway represents a major update to best practices for IPv4 VPC networking.
  • You don't need NAT gateway to deploy Lambda into VPC

    In this episode of VPC Dealers we're taking on a Lambda function that's been running in a VPC with NAT gateway for years. It works fine but those hourly charges keep adding up. Time to do what Ant did with that Maserati Biturbo - rip out the old combustion engine and drop in something electric. We're converting from NAT gateway to Egress-only gateway with IPv6, cutting the running costs while keeping all the functionality.
  • Debugging Lambda

    AWS Lambda remote debugging allows debugging Lambda functions running in the cloud directly from local IDE. With this new capability, it is possible use familiar debugging tools like breakpoints, variable inspection, and step-through debugging with functions deployed in the cloud.
  • Analyze This

    Those of you who have been working as network admin or someone who's work depends on network, you know when things stop working, network is always first to blame until proven innocent. To get to correct root cause it is important to quickly rule out, or find evidence of, network problems. This is where AWS Reachability Analyzer can help network admins but also let anyone to verify basic requirements for connectivity from point A to B (and back again) are in-place.