James Martin

Customers often ask if Amazon Q Developer is only for Amazon Web Services (AWS) workloads. The short answer is no. Our developer platform can add value to your on-premises development and multi-cloud needs, regardless of your platform. Our partners at Heroku have a great use case for this. Check out their blog post on how the Amazon Q Developer / Heroku integration simplifies their customer workflows.

14

Folks I've spoken to about Amazon have likely heard me talk about the importance of the PR/FAQ process, a.k.a. "the working backwards process". This blog posts gives a very nice example of a PR/FAQ. https://lnkd.in/edTeuVRQ. Note that the blog doesn't capture the presumably 100s of reviews/discussions/rewrites that this doc represents, which is a part of the real value. When the process is done it all looks so simple, but getting a large organization to make a decision to something simple and do it in a BIG way is the challenge the fun of it all.

64

3 Comments

Infusing resiliency into our applications typically introduces complexity. AWS Step Functions (SF) have been my go-to for managing more complex workflows, shifting some of that complexity to a managed service and away from our code. However, adopting SF comes with challenges and may not be a viable option depending on your context. The concept of persistent execution with Temporal is an interesting alternative to consider. You can check more here:

20

45 days until #AWS #reinvent2024 in Las Vegas. Here is my top 10 list of the sessions I'm excited about: 1️⃣ OPN311 | Harnessing Apache ActiveMQ: ActiveMQ 6.x features and roadmap - with JB Onofré and Jules Graybill 2️⃣ ANT327 | What's new: Data streaming on AWS - with Ashish Palekarand Anusha Dasarakothapalli 3️⃣ ANT412 | Ingest streaming data into Apache Iceberg tables with AWS Streaming - with Ravikiran Rao and Amar Surjit 4️⃣ ANT324 | Accelerate value from data: Migrating from batch to steam processing - with Usama Naseem and Sofie Zilberman 5️⃣ ANT342 | Operate and scale managed Apache Kafka and Apache Flink clusters - with Sai Maddali and Ali Alemi 6️⃣ API401 | Multi-tenant Amazon SQS queues: Mitigating noisy neighbors - with Vinodh Kannan Sadayamuthu and Dirk Fröhner 7️⃣ API312 | Best practices to migrate your existing message broker to AWS - with Vinodh Kannan Sadayamuthu and Daniel Fargano 8️⃣ ANT318 | Building serverless streaming data pipelines for real-time analytics - with Mostafa Mansour and Gregory K. 9️⃣ AUT319 | Learnings from BMW's global software development platform on AWS - with Christian Mueller 🔟 FSI310 | BBVA Corporate & Investment Banking: Building a multi-region, multi-country data platform at scale - with Ignacio Fernandez and Federico Esteban What sessions have you marked as favorites? Drop the session ID in the comments. The catalog is available here:

105

3 Comments

Well done #AWS for promptly fixing an S3 billing edge-case! Interesting S3 cost issue in this blog: "How an empty S3 bucket can make your AWS bill explode". In brief: external unauthorised (denied) requests to a new empty S3 bucket were being charged - $1,300 within two days. The author had inadvertently chosen the same bucket name that was the placeholder default configuration in a popular open-source tool!    https://lnkd.in/eNEqedR8 That blog was published on 29th April 2024. On 13th May, AWS fixed this problem: "Amazon S3 will no longer charge for several HTTP error codes". https://lnkd.in/eMXuhhu8 To quote that announcement: "bucket owners will never incur request or bandwidth charges for requests that return an HTTP 403 (Access Denied) error response if initiated from outside their individual AWS account or AWS Organization."

6

According to Gartner® “Infrastructure and Operations (I&O) teams commonly struggle to manage Kubernetes (K8s) clusters at scale due to the talent shortage 🤼 — especially on heterogeneous scenarios (multicluster, hybrid, edge, etc.) or supporting multiple downstream teams. Besides inherent Kubernetes complexities, K8s teams must cope with the increase in the average number of clusters per organization from a few to dozens. As the cluster count grows and spans, the stack becomes more complex and diverse across different infrastructures (cloud, on-premises, and edge). This negatively impacts practitioners’ ability to maintain the clusters and demands more attention from I&O teams." 👉 struggling with managing complex Kubernetes? 🗓 schedule free consultancy => https://lnkd.in/dyErkV_C #angelscloud, #k8s, #Kubernetes, #digitaltransformation #multicluster #cloud

3

New Episode: 260: Amazon Dispatches AWS CEO Adam Selipsky with Prime 2-day delivery Episode 260 of The Cloud Pod podcast, bringing you all the latest news from Cloud and AI including AWS, Azure, Google, OCI, GPT-4.o, C7i-flex, AWS CEO Changes and Amazon Polly #aws #gcp #azure #cloud #cloudpodcast #podcast

18

Want to learn how to enable your team to have more time to spend on #velocity versus frustrating operational tasks - without compromising #customerexperience while reducing the cost of your #operations? Join @ayeletsachto at DASH on June 25th where she'll share learnings from our two-year program, which reduced the cost of Google Kubernetes Engine Operations as our fleet increased without compromising the #reliability of our systems! #SRE

1

Building on Amazon ElastiCache for Valkey momentum we launched support for v8 today, which features performance, scalability and memory optimization gains. For those headed to re:invent, we are bringing a number of In-Memory Developers, Specialist Solution Architects and Product Managers to highlight what's new and outline migration best practices and future areas of innovation. https://lnkd.in/gM3dgJyn

23

1 Comment

AWS Lambda is turning 10 🎊 Very interesting read on the Amazon culture of the PR/FAQ process and the actual document that brought AWS Lambda to life #aws #lambda #serverless

10

In case you missed our session at #reInvent, the recording is now available here: https://lnkd.in/gCkXTYHf You will learn about all the exciting product announcements from #AWS on Amazon QuickSight and #CapitalOne’s approach and long-standing commitment to put data and intelligence at the fingertips of our business users and customers to drive better decisions

31

2 Comments

This is a game changer for the zero trust efforts we're leading with the Centers for Medicare and Medicaid. The ability to now point a cloudfront distribution directly to an internal load balancer hosted in a private subnet removes a lot of the complex and awkward things we've had to do to achieve the effect of having cloudfront be the sole entry point into an application. https://lnkd.in/gnwT9F_r

11

A core tenet for #AWS has always been that, if it was possible to take care of scaling, resilience, availability, security, and cost management of our customer's infrastructure components, we should do so. Eventually, this became known as "serverless", which encompasses much more than executing code without the need for servers. Amazon SQS and S3 were the first AWS services launched, and they were "serverless" from day one. A good example of this philosophy in practice is Aurora Serverless, which provides on-demand auto-scaling for Amazon Aurora databases. It proactively scales up resources during peak periods to ensure the predictable performance when you require it. When demand subsides, it seamlessly scales back down, reducing waste. And with granular, second-by-second billing, you can truly optimize for cost. Remember, the essence of frugal architecture is robust monitoring driving the ability to optimize costs. To dive deeper into how Aurora Serverless exemplifies this principle, I recommend reading the latest paper here: https://lnkd.in/e4uPK6wv #AWS #serverless #databases

1,024

16 Comments

Rocky Linux is now available for Amazon WorkSpaces! Customers can now choose Rocky Linux alongside other popular OS options in Amazon WorkSpaces. This addition empowers businesses to maintain their preferred Linux environment while leveraging the scalability and security of Amazon Web Services (AWS)'s cloud-based virtual desktops. #aws #euc #vdi #linux CIQ #rockylinux #daas #remotedesktop #amazonworkspaces https://lnkd.in/dU5MxrDk

44

2 Comments

Something that's been in the works for a long time: details of the formal correctness proof (in Dafny) of AWS's policy authorization engine, which makes 2+ billion decisions per second about who can access what, on practically every call to AWS. Talk is by Lucas Wagner and Sean McLaughlin https://lnkd.in/eiJYQeqw

214

6 Comments

Here's a practical example of how Formal Methods can make code faster: AWS's new proven-correct authorization engine is 65% faster (even at p99.9) than the previous version. https://lnkd.in/gVCdurKh Sean says in the talk "we wouldn't have attempted a lot of optimizations we did without this backing of proof". Formal methods allow us to optimize systems more boldly, by removing the risk that optimizations will affect correctness. They also allow our teams to move faster, with lower risk, by building confidence in correctness early on in the software development process.

435

4 Comments