We dive deep into Strapi, an open-source headless CMS that's changing how we approach content management and CRUD applications. In this episode, we explore how Strapi separates content from presentation, allowing marketing teams to manage content independently while developers maintain full control over the frontend experience. We discuss the powerful features that caught our attention, including the visual content type builder, dynamic zones, components, and the innovative blocks editor that stores content as JSON rather than HTML. We also cover practical aspects like local development workflows, data synchronization between environments, and deployment strategies on AWS. While we highlight some rough edges around documentation and minor bugs, we share our overall positive experience and provide insights into when Strapi might be the right choice for your next project.

In this episode, we mentioned the following resources:

• Strapi CMS: https://strapi.io/
• Strapi on GitHub: https://github.com/strapi/strapi
• Strapi Docs: https://docs.strapi.io/
• Strapi S3 Provider: https://www.npmjs.com/package/@strapi/provider-upload-aws-s3
• Strapi installation and pre-requisites: https://docs.strapi.io/cms/installation/cli
• The React Block Content renderer: https://github.com/strapi/blocks-react-renderer
• Contentful: https://www.contentful.com/
• Storyblok: https://www.storyblok.com/
• Sanity: https://www.sanity.io/
• HyGraph: https://hygraph.com/
• Byline CMS: https://bylinecms.app/

Do you have any AWS questions you would like us to address?

Leave a comment here or connect with us on X/Twitter, BlueSky or LinkedIn:

- ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/eoins⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠⁠⁠⁠⁠⁠https://bsky.app/profile/eoin.sh⁠⁠⁠⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/in/eoins/⁠⁠

⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠- ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/loige⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠⁠⁠⁠⁠⁠https://bsky.app/profile/loige.co⁠⁠⁠⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/in/lucianomammino/

What if “Java is too old for serverless” is the myth holding your team back in 2025?

We put it to the test with Mark Sailes (ex-AWS, Java-on-Lambda expert). In this AWS Bites episode we get specific: when Java is the right call for Lambda and when it isn’t, how to hit real latency targets, and the exact levers that matter in production—SnapStart, provisioned concurrency, smart JVM/GC settings, and whether GraalVM is worth it. We compare vanilla Java, Micronaut, Quarkus, and Spring Boot for startup and memory, share realistic p95/p99 expectations, and outline fast feedback loops with Testcontainers and LocalStack.If Java on Lambda sounds risky, this might change your mind. Stick around for Mark’s tuning checklist and our verdict on when to bet on Java vs pick another runtime.

Big shoutout to fourTheorem for powering yet another episode of AWS Bites. At fourTheorem, we believe the cloud should be simple, scalable, and cost-effective, and we help teams do just that. Whether you’re diving into containers, stepping into event-driven architecture, or scaling a global SaaS platform on AWS, or trying to keep cloud spend under control our team has your back. Visit ⁠⁠⁠⁠https://fourTheorem.com⁠⁠⁠⁠ to see how we can help you build faster, better, and with more confidence using AWS cloud!

In this episode, we mentioned the following resources:

• Mark Sailes's website and books: https://www.sailes.co.uk/books
• Mark's YouTube channel: https://youtube.com/@javainthecloud
• Running Java effectively on serverless (ServerlessLand): https://serverlessland.com/content/service/lambda/guides/effectively-running-java-on-serverless/1-introduction
• Lambda execution visualizer: https://lambda-sim.sailes.co.uk/
• Lambda SnapStart for Java simulator: https://www.sailes.co.uk/learn/lambda-snapstart
• Penna logging library for Java: https://github.com/hkupty/penna
• Testcontainers for Java: https://java.testcontainers.org/
• Localstack: https://docs.localstack.cloud/aws/
• Micronaut: https://micronaut.io/
• Quarkus: https://quarkus.io/
• GraalVM: https://www.graalvm.org/
• AWS response to the Log4j issue: https://aws.amazon.com/security/security-bulletins/AWS-2021-005/

Do you have any AWS questions you would like us to address?

Leave a comment here or connect with us on X/Twitter, BlueSky or LinkedIn:

- ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/eoins⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠⁠⁠⁠⁠https://bsky.app/profile/eoin.sh⁠⁠⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/in/eoins/⁠

⁠⁠⁠⁠⁠⁠⁠⁠⁠- ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/loige⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠⁠⁠⁠⁠https://bsky.app/profile/loige.co⁠⁠⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/in/lucianomammino/

What if AWS built an IDE to rival your favorite editor? Turns out they did!In this episode of AWS Bites, we dive into Kiro, an AI centric fork of VS Code that tries to turn an empty repo and a loose idea into working software. Kiro imports your VS Code world, then guides you through requirements, design, and a clear task plan before an agent gets to work. We share what clicked, what tripped us up, and how Kiro’s spec driven approach compares to Cursor or Claude Code. We also cover status, limits, pricing, and what this could become if AWS leans in with deep cloud integration. Stick around for our take on whether you should switch or wait.

Big shoutout to fourTheorem for powering yet another episode of AWS Bites. At fourTheorem, we believe the cloud should be simple, scalable, and cost-effective, and we help teams do just that. Whether you’re diving into containers, stepping into event-driven architecture, or scaling a global SaaS platform on AWS, or trying to keep cloud spend under control our team has your back. Visit ⁠⁠⁠https://fourTheorem.com⁠⁠⁠ to see how we can help you build faster, better, and with more confidence using AWS cloud!

In this episode, we mentioned the following resources:

• Kiro website: https://kiro.dev/
• Kiro docs on Agent Hooks: https://kiro.dev/docs/hooks/
• Kiro docs on Steering: https://kiro.dev/docs/steering/
• Kiro pricing plans blog: https://kiro.dev/blog/pricing-plans-are-live/
• Cargo Lambda: https://www.cargo-lambda.info/
• Episode 64: how do you write Lambda functions in Rust?: https://awsbites.com/64-how-do-you-write-lambda-functions-in-rust/
• Kiro GitHub issue: https://github.com/kirodotdev/Kiro/issues/2004
• Amazon Q developer CLI: https://github.com/aws/amazon-q-developer-cli

Do you have any AWS questions you would like us to address?

Leave a comment here or connect with us on X/Twitter, BlueSky or LinkedIn:

- ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/eoins⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠⁠⁠⁠https://bsky.app/profile/eoin.sh⁠⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/in/eoins/

⁠⁠⁠⁠⁠⁠⁠- ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/loige⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠⁠⁠⁠https://bsky.app/profile/loige.co⁠⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/in/lucianomammino/

What if AWS had its own version of Killed by Google? Well… turns out it kind of does.In this episode of AWS Bites, we explore the AWS Product Lifecycle page, the official place where AWS quietly lists products and services that are being deprecated, shut down, or closed to new customers. If you rely on AWS in production, this is a page you’ll want to bookmark.We walk through what’s on the list today, from Amazon Pinpoint to IoT Analytics and beyond, and we even throw in some predictions of what might be next to hit the chopping block. App Runner vs Beanstalk? API Gateway REST vs HTTP? Let the speculation begin!

Big shoutout to fourTheorem for powering yet another episode of AWS Bites. At fourTheorem, we believe the cloud should be simple, scalable, and cost-effective, and we help teams do just that. Whether you’re diving into containers, stepping into event-driven architecture, or scaling a global SaaS platform on AWS, or trying to keep cloud spend under control our team has your back. Visit ⁠⁠https://fourTheorem.com⁠⁠ to see how we can help you build faster, better, and with more confidence using AWS cloud!

In this episode, we mentioned the following resources:

• AWS Product Lifecycle Page: ⁠⁠https://aws.amazon.com/products/lifecycle/⁠⁠
• AWS Blog – Introducing the AWS Product Lifecycle Page: ⁠⁠https://aws.amazon.com/blogs/aws/introducing-the-aws-product-lifecycle-page-and-aws-service-availability-updates/⁠⁠
• AWS Bites Episode 98 – Amazon Pinpoint Quota Changes: ⁠⁠https://awsbites.com/98⁠⁠
• AWS Bites Episode 74 – API Gateway REST vs HTTP: ⁠⁠https://awsbites.com/74⁠⁠
• AWS Bites Episode 76 – AWS Copilot: ⁠⁠https://awsbites.com/76⁠⁠
• AWS Bites Episode 143 – Is App Runner Better than Fargate?: ⁠⁠https://awsbites.com/143⁠⁠
• API Gateway Routing Rules: ⁠⁠https://aws.amazon.com/blogs/compute/dynamically-routing-requests-with-amazon-api-gateway-routing-rules/⁠⁠
• Alexa+ and the future of generative AI at Amazon: ⁠⁠https://www.aboutamazon.com/news/devices/new-alexa-generative-artificial-intelligence⁠⁠

Do you have any AWS questions you would like us to address?

Leave a comment here or connect with us on X/Twitter, BlueSky or LinkedIn:- ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/eoins⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠⁠⁠https://bsky.app/profile/eoin.sh⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠⁠⁠https://www.linkedin.com/in/eoins/⁠⁠⁠⁠⁠⁠- ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/loige⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠⁠⁠https://bsky.app/profile/loige.co⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠⁠⁠https://www.linkedin.com/in/lucianomammino/

Amazon Aurora DSQL promises to bring a truly serverless experience to SQL databases. But does it actually deliver? In this episode of AWS Bites, we put Aurora DSQL to the test. We explore what makes it exciting, how it compares to traditional Aurora Serverless, and where it falls short. You’ll hear what changed since our last Aurora deep dive, and why DSQL might be the PostgreSQL-compatible serverless database you’ve been waiting for.

Big shoutout to fourTheorem for powering yet another episode of AWS Bites. At fourTheorem, we believe the cloud should be simple, scalable, and cost-effective, and we help teams do just that. Whether you’re diving into containers, stepping into event-driven architecture, or scaling a global SaaS platform on AWS, or trying to keep cloud spend under control our team has your back. Visit ⁠https://fourTheorem.com⁠ to see how we can help you build faster, better, and with more confidence using AWS cloud!

In this episode, we mentioned the following resources:

• AWS Blog – Amazon Aurora DSQL is Now Generally Available: ⁠https://aws.amazon.com/blogs/aws/amazon-aurora-dsql-is-now-generally-available/⁠
• AWS Blog – Introducing Amazon Aurora DSQL: ⁠https://aws.amazon.com/blogs/database/introducing-amazon-aurora-dsql/⁠
• Aurora DSQL Deep Dive by Amazon: ⁠https://www.youtube.com/watch?v=GCdAngjKZY4⁠
• DSQL Example Application by fourTheorem: ⁠https://github.com/fourTheorem/dsql-example/⁠
• PlanetScale Docs – Why Does PlanetScale Not Recommend Constraints: ⁠https://planetscale.com/docs/vitess/operating-without-foreign-key-constraints#why-does-planetscale-not-recommend-constraints-⁠
• Marc Bowes – How to Spend a Dollar with DSQL: ⁠https://marc-bowes.com/dsql-how-to-spend-a-dollar.html⁠
• Alessandro Volpicella – Amazon DSQL Pricing Guide: ⁠https://awsfundamentals.com/blog/amazon-dsql-pricing-guide⁠
• BinaryHeap Blog – First Look at DSQL (The Naughty List): ⁠https://binaryheap.com/first-look-dsql/⁠
• AWS Bites – Aurora Deep Dive (Episode 122): ⁠https://awsbites.com/122⁠

Do you have any AWS questions you would like us to address?

Leave a comment here or connect with us on X/Twitter, BlueSky or LinkedIn:- ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/eoins⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠⁠https://bsky.app/profile/eoin.sh⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠⁠https://www.linkedin.com/in/eoins/⁠⁠⁠⁠⁠- ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/loige⁠⁠⁠⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠⁠https://bsky.app/profile/loige.co⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠⁠https://www.linkedin.com/in/lucianomammino/

Cost is always top of mind when building in the cloud, and recently AWS has introduced some changes worth paying attention to. In this episode of AWS Bites, we explore a shift that caught many by surprise: the “free” INIT phase for Lambda’s managed runtimes is going away. That cold start time that used to fly under the billing radar? It's now part of the cost. We dig into what this means for your workloads, who might feel the impact, and whether this gives languages like Rust and Go an extra edge. But it’s not all bad news. AWS has also rolled out new pricing tiers for CloudWatch Logs, making it cheaper for high-volume accounts. On top of that, there are new options to send logs directly to S3 or Firehose, helping simplify pipelines and reduce costs. We close with a few tips to help you keep your Lambda and logging spend under control. If you're building on AWS and care about efficiency, this is one you won't want to miss.

Big shoutout to fourTheorem for powering yet another episode of AWS Bites. At fourTheorem, we believe the cloud should be simple, scalable, and cost-effective, and we help teams do just that. Whether you’re diving into containers, stepping into event-driven architecture, or scaling a global SaaS platform on AWS, or trying to keep cloud spend under control our team has your back. Visit https://fourTheorem.com to see how we can help you build faster, better, and with more confidence using AWS cloud!

In this episode, we mentioned the following resources:

• AWS Blog – Tiered Pricing for AWS Lambda: https://aws.amazon.com/blogs/compute/introducing-tiered-pricing-for-aws-lambda/
• Luc van Donkersgoed – When is the Lambda INIT phase free and when is it billed?: https://lucvandonkersgoed.com/2022/04/09/when-is-the-lambda-init-phase-free-and-when-is-it-billed/
• AWS Bites – Explaining Lambda Runtimes (Episode 104): https://awsbites.com/104-explaining-lambda-runtimes/
• AWS Blog – Standardized Billing for Lambda INIT Phase: https://aws.amazon.com/blogs/compute/aws-lambda-standardizes-billing-for-init-phase/
• Lambda Cold Start Benchmarks by Maxim David: https://maxday.github.io/lambda-perf/
• Duckbill Group Blog – Lambda Logs Just Got Cheaper: https://www.duckbillgroup.com/blog/lambda-logs-just-got-cheaper/
• AWS Bites – Becoming a Logs Ninja with CloudWatch (Episode 35): https://awsbites.com/35-how-can-you-become-a-logs-ninja-with-cloudwatch

Do you have any AWS questions you would like us to address?

Leave a comment here or connect with us on X/Twitter, BlueSky or LinkedIn:- ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/eoins⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠https://bsky.app/profile/eoin.sh⁠⁠⁠⁠ | ⁠⁠⁠⁠https://www.linkedin.com/in/eoins/⁠⁠⁠⁠- ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/loige⁠⁠⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠https://bsky.app/profile/loige.co⁠⁠⁠⁠ | ⁠⁠⁠⁠https://www.linkedin.com/in/lucianomammino/

Picture this. You’ve got a web app built with Rust and Solid.js. It started life running on a dusty on-prem server, but now it's time to move it to the cloud. The clock is ticking. You could take the well-worn AWS path: set up a VPC, configure subnets, attach an ALB, define IAM roles, and deploy with Fargate. Or you could try something different. In this episode of AWS Bites, we share the real story of migrating a monolithic containerized app to AWS App Runner. It promises to take your code, build it, deploy it, and scale it with minimal effort. But does it really deliver? We compare App Runner with Fargate based on hands-on experience. You’ll learn where App Runner shines, where it gets in the way, and how we handled everything from custom domains to background job processing. You’ll also hear when we would still choose Fargate, and why. If you've ever hoped for a Heroku-like experience on AWS, or you want to simplify your container deployments without giving up too much control, this episode is for you.

AWS Bites is brought to you in association with fourTheorem. At fourTheorem, we believe serverless should be simple, scalable, and cost-effective — and we help teams do just that. Whether you’re diving into containers, stepping into event-driven architecture, or scaling a global SaaS platform on AWS, our team has your back. Visit https://fourTheorem.com to see how we can help you build faster, better, and with more confidence using AWS cloud!

In this episode, we mentioned the following resources:

• Last Week in AWS: The 17 Ways to Run Containers on AWS: https://www.lastweekinaws.com/blog/the-17-ways-to-run-containers-on-aws/
• GitHub Issue - App Runner scale to zero discussion: https://github.com/aws/apprunner-roadmap/issues/9
• Custom Domain with CloudFormation (Mark van Holsteijn, Xebia): https://xebia.com/blog/configure-custom-domain-for-aws-apprunner-service-using-cloudformation/
• AWS Docs - App Runner hosted zone IDs: https://docs.aws.amazon.com/general/latest/gr/apprunner.html

Do you have any AWS questions you would like us to address?

Leave a comment here or connect with us on X/Twitter, BlueSky or LinkedIn:- ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/eoins⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠https://bsky.app/profile/eoin.sh⁠⁠⁠ | ⁠⁠⁠https://www.linkedin.com/in/eoins/⁠⁠⁠- ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/loige⁠⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠https://bsky.app/profile/loige.co⁠⁠⁠ | ⁠⁠⁠https://www.linkedin.com/in/lucianomammino/

We discuss common use cases and challenges for copying data between S3 buckets and S3-compatible object storage services. We share our experience building an open source Node.js CLI tool called S3-Migrate to efficiently migrate data with separate source and destination credentials. We cover performance considerations like streaming, chunk sizes, concurrency and parallelism.

AWS Bites is brought to you in association with fourTheorem. If you need a friendly partner to support you and work with you to de-risk any AWS migration or development project, check them out at ⁠⁠⁠fourtheorem.com⁠⁠⁠

In this episode, we mentioned the following resources:

• s3-migrate CLI tool: https://github.com/lmammino/s3-migrate
• DigitalOcean Spaces Object Storage: https://docs.digitalocean.com/products/spaces/
• Cloudflare R2: https://www.cloudflare.com/en-gb/developer-platform/products/r2/
• Backblaze B2: https://www.backblaze.com/cloud-storage
• Wasabi Cloud Storage: https://wasabi.com/
• Linode / Akamai Object Storage: https://www.linode.com/products/object-storage/
• MinIO (Self-hosted S3-compatible storage): https://min.io/
• Basecamp / Hey’s move away from S3: https://world.hey.com/dhh/it-s-five-grand-a-day-to-miss-our-s3-exit-b8293563
• AWS re:Post - How to move objects between S3 buckets: https://repost.aws/knowledge-center/move-objects-s3-bucket
• AWS Labs - Utility for S3 Migration: https://github.com/awslabs/utility-for-s3-migration
• s3s3mirror (Java-based tool): https://github.com/cobbzilla/s3s3mirror
• rclone S3 Support: https://rclone.org/s3/
• knox-copy (Ruby-based, deprecated): https://github.com/goodeggs/knox-copy
• Flexify.io (paid cloud migration service): https://flexify.io/

Do you have any AWS questions you would like us to address?

Leave a comment here or connect with us on X/Twitter, BlueSky or LinkedIn:- ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/eoins⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ | ⁠⁠https://bsky.app/profile/eoin.sh⁠⁠ | ⁠⁠https://www.linkedin.com/in/eoins/⁠⁠- ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/loige⁠⁠⁠⁠⁠⁠ | ⁠⁠https://bsky.app/profile/loige.co⁠⁠ | ⁠⁠https://www.linkedin.com/in/lucianomammino/

In this episode, we provide an overview of AWS Step Functions and dive deep into the powerful new JSONata and variables features. We explain how JSONata allows complex JSON transformations without custom Lambda functions, enabling more serverless workflows. The variables feature also helps avoid the previous 256KB state size limit. We share examples from real projects showing how these features simplify workflows, reduce costs and enable new use cases.

AWS Bites is brought to you in association with fourTheorem. If you need a friendly partner to support you and work with you to de-risk any AWS migration or development project, check them out at ⁠⁠fourtheorem.com⁠⁠

In this episode, we mentioned the following resources:

• JSONata and variables official launch post: https://aws.amazon.com/blogs/compute/simplifying-developer-experience-with-variables-and-jsonata-in-aws-step-functions/
• JSONata exerciser: https://try.jsonata.org/
• Stedi JSONata playground: https://www.stedi.com/jsonata/playground
• Episode 103: Building GenAI Features with Bedrock https://awsbites.com/103-building-genai-features-with-bedrock/
• Episode 63: How to automate transcripts with Amazon Transcribe and OpenAI Whisper https://awsbites.com/63-how-to-automate-transcripts-with-amazon-transcribe-and-openai-whisper/

Do you have any AWS questions you would like us to address?

Leave a comment here or connect with us on X/Twitter, BlueSky or LinkedIn:- ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/eoins⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ | ⁠https://bsky.app/profile/eoin.sh⁠ | ⁠https://www.linkedin.com/in/eoins/⁠- ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/loige⁠⁠⁠⁠⁠ | ⁠https://bsky.app/profile/loige.co⁠ | ⁠https://www.linkedin.com/in/lucianomammino/

In this episode, we explore DuckDB, an open-source analytical database known for its speed and simplicity. Discover how DuckDB stands out in various applications and compare it to other tools like SQLite, Athena, Pandas, and Polars. We also demonstrate integrating DuckDB with AWS Lambda and Step Functions for serverless analytics.

AWS Bites is brought to you by fourTheorem. If you are looking for a partner to architect, develop and modernise on AWS, give fourTheorem a call. Check out ⁠fourtheorem.com⁠

In this episode, we mentioned the following resources:

• Our `duck-query-lambda`, A Lambda runtime for DuckDB queries: https://github.com/fourTheorem/duck-query-lambda
• DuckDB's official website: https://duckdb.org/
• LibSQL: https://github.com/tursodatabase/libsql

Do you have any AWS questions you would like us to address?

Leave a comment here or connect with us on X/Twitter, BlueSky or LinkedIn:- ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/eoins⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ | https://bsky.app/profile/eoin.sh | https://www.linkedin.com/in/eoins/- ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/loige⁠⁠⁠⁠ | https://bsky.app/profile/loige.co | https://www.linkedin.com/in/lucianomammino/