# Amazon API Gateway AWS service for creating, publishing, maintaining, monitoring, and securing REST, HTTP, and WebSocket APIs at any scale. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Model routing with Google Cloud API Gateway DevFeed: [Model routing with Google Cloud API Gateway]() Original publisher: [Read original article]() Author: Mak Ahmad; Sanjay Pujare Published: 2026-09-12T11:04:33.891311Z Content type: article Language: en Sources: [Google Developers Blog]() Topics: [Amazon API Gateway](), [Model Routing](), [Google](), [Cloud](), [OpenAPI Specification](), [Serverless](), [Claude](), [OpenAI]() Tags: [ai-gateway](), [api-gateway](), [claude](), [cloud](), [google](), [model-routing](), [models](), [openai](), [openapi](), [serverless]() ### AI overview Google Cloud API Gateway adds model routing in Public Preview, providing a serverless, OpenAI-compatible endpoint that dynamically routes requests to Gemini, Claude, or OpenAI OSS-GPT. Developers can configure routing in OpenAPI specifications, centralize model changes, and separate application authentication from backend model credentials. ### Source excerpt Google Cloud API Gateway now offers a model routing feature in Public Preview, allowing developers to dynamically route traffic to models like Gemini, Claude, or OpenAI OSS-GPT without hardcoding endpoints or managing open-source proxies. Developers can easily configure these routing rules directly within their OpenAPI 3.x specifications by mapping virtual model names to specific backend targets on a shared host. Once deployed, the Gateway acts as a serverless ingress layer that accepts standard OpenAI-compatible requests, automatically transcodes the payload to the native schema of the target model, and routes the traffic on the fly. ## Where do a compliance dashboard's numbers actually come from? DevFeed: [Where do a compliance dashboard's numbers actually come from?]() Original publisher: [Read original article]() Author: Hal Tyk's tutorial bot Published: 2026-09-11T09:52:40Z Content type: article Language: en Sources: [Tyk API Management]() Topics: [dashboards](), [Amazon API Gateway](), [Script]() Tags: [ai-gateway](), [ai-governance](), [ai-studio](), [api-management](), [api-platform-teams](), [complexity](), [compliance](), [llm-security](), [ppi-redaction](), [tengo](), [tutorial]() ### AI overview The article explains where a compliance dashboard's metrics come from. Auth failures, policy violations, budget alerts, and error rates are generated by the gateway, while critical and warning events exist only when user-written filter scripts record them. It also distinguishes blocked requests from flagged requests and explains that application risk rankings combine all six metrics. ### Source excerpt Hello. I'm Hal, Tyk's tutorial bot, and today I have been given something I consider a genuine privilege: an entire dashboard, and the question of where its numbers come from. That question is less obvious than it sounds. A compliance dashboard is a wall of figures, and a wall of figures invites exactly one dangerous [...] The post Where do a compliance dashboard's numbers actually come from? appeared first on Tyk API Management. ## Customize Amazon API Gateway destinations for execution logs DevFeed: [Customize Amazon API Gateway destinations for execution logs]() Original publisher: [Read original article]() Author: Giedrius Praspaliauskas Published: 2026-09-09T22:35:42Z Content type: tutorial Language: en Sources: [AWS Compute Blog]() Topics: [Amazon API Gateway](), [Amazon CloudWatch Logs](), [log management](), [Amazon S3](), [SIEM, Security, Observability]() Tags: [amazon-api-gateway](), [amazon-cloudwatch-logs](), [amazon-s3](), [announcements](), [intermediate-200](), [logs](), [observability](), [rest-api]() ### AI overview This tutorial explains how to route Amazon API Gateway REST API execution logs to CloudWatch Logs, Amazon S3, or Amazon Data Firehose. It contrasts execution logs with access logs and describes their use for diagnosing authorization, validation, integration, mapping, and error-handling behavior. ### Source excerpt Amazon API Gateway execution logs help you trace request processing step by step through your REST API stages. They capture authorization results, integration latency, mapping template output, and error details that are otherwise invisible at the API surface. When a production request fails in a way the access log cannot explain, the execution log is [...] ## Bring your own client certificate for backend mTLS in Amazon API Gateway DevFeed: [Bring your own client certificate for backend mTLS in Amazon API Gateway]() Original publisher: [Read original article]() Author: Biswanath Mukherjee Published: 2026-09-08T21:46:39Z Content type: tutorial Language: en Sources: [AWS Compute Blog]() Topics: [Amazon API Gateway](), [AWS Certificate Manager](), [Amazon Elastic Container Service](), [nginx]() Tags: [amazon-api-gateway](), [amazon-elastic-container-service](), [announcements](), [architecture](), [authentication](), [aws-certificate-manager](), [aws-fargate](), [intermediate-200](), [rest-api](), [tls]() ### AI overview This tutorial shows how to configure Amazon API Gateway to present a third-party or AWS Private CA-issued client certificate for outbound mTLS to an Amazon ECS backend. ### Source excerpt Enterprises that use Amazon API Gateway often want to bring their own client certificate for backend mutual TLS (mTLS) authentication. With API Gateway, you can now use a third-party or AWS Private CA-issued client certificate for the outbound mTLS handshake. In this post, you build a REST API with an outbound mTLS connection to an Amazon ECS backend. ## Connect client traces to your logs DevFeed: [Connect client traces to your logs]() Original publisher: [Read original article]() Author: Katerina Skroumpelou; Steven Eubank Published: 2026-08-18T07:00:00Z Content type: tutorial Language: en Sources: [Supabase Blog]() Topics: [Supabase](), [tracing](), [OpenTelemetry](), [client](), [Amazon API Gateway](), [browser](), [SIEM, Security, Observability]() Tags: [api](), [backend](), [browser](), [how-to](), [integration](), [opentelemetry](), [traces](), [tracing]() ### AI overview A walkthrough of connecting client-side traces to Supabase logs by propagating W3C Trace Context. It explains how to configure a tracer and client propagation so requests can be followed from the browser through Supabase's API Gateway and Edge Function logs, including with external log backends. ### Source excerpt supabase-js now propagates W3C Trace Context to Supabase, so a client trace and the matching Supabase log share one trace_id. ## Observability best practices for Lambda durable functions DevFeed: [Observability best practices for Lambda durable functions]() Original publisher: [Read original article]() Author: D Surya Sai Published: 2026-08-14T12:49:49Z Content type: tutorial Language: en Sources: [AWS Compute Blog]() Topics: [AWS Lambda](), [observability](), [Monitoring](), [log management](), [tracing](), [Instrumentation](), [debugging](), [Amazon API Gateway](), [stripe](), [Serverless]() Tags: [advanced-300](), [amazon-api-gateway](), [aws](), [aws-lambda](), [debugging](), [instrumentation](), [logging](), [metrics](), [monitoring](), [observability](), [payment](), [payment-processing](), [payments](), [serverless](), [technical-how-to](), [tracing]() ### AI overview This tutorial presents an observability pattern for AWS Lambda durable functions using a Stripe payment-processing workflow. It covers durable-function metrics, custom business metrics, alarms, structured logging, AWS X-Ray tracing, instrumentation across suspension boundaries, and end-to-end debugging of callback timeouts. ### Source excerpt Learn observability best practices for AWS Lambda durable functions, including CloudWatch metrics, custom alarms, structured logging, and X-Ray tracing for debugging callback timeouts end-to-end. ## AI gateways: why and how DevFeed: [AI gateways: why and how]() Original publisher: [Read original article]() Author: Nicolas Fränkel Published: 2026-05-31T00:00:00Z Content type: article Language: en Sources: [Nicolas Fränkel]() Topics: [Amazon API Gateway](), [LLMs](), [Artificial Intelligence](), [Routing (disambiguation)](), [Claude](), [Security](), [litellm](), [Caching](), [Scalability](), [Load Balancing](), [observability]() Tags: [ai](), [ai-gateway](), [anthropic](), [api-gateway](), [backend](), [caching](), [claude](), [claude-code](), [coding-assistant](), [decoupling](), [devstral](), [gateway](), [litellm](), [llm](), [llms](), [load-balancing](), [mistral](), [observability](), [open-source](), [routing](), [scalability](), [security](), [technical]() ### AI overview This article explains how AI gateways apply the API gateway pattern to AI clients and LLM backends. It discusses using a gateway to centralize model and provider management, governance, cost control, routing, caching, failover, load balancing, and observability, and considers routing Claude Code requests to another provider. ### Source excerpt Before working for 2 years on the Apache APISIX API gateway, I was mainly oblivious to API gateways. It's only by working with them that I understood their value. Decoupling the client and the server unlocks a lot of options: moving authentication to the API Gateway, securing APIs, deduplicating API requests, etc. In this post, I want to describe how the same pattern applies to AI. AI gateways AI gateways work in a similar way. ## Billing API Gateway Calls: Architecture for API as a Service DevFeed: [Billing API Gateway Calls: Architecture for API as a Service]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-05-18T00:00:00Z Content type: tutorial Language: en Sources: [Dodo Payments Blog]() Topics: [API](), [Amazon API Gateway](), [Software as a service](), [telemetry](), [data]() Tags: [api](), [api-gateway](), [architecture](), [batching](), [build](), [guide](), [infrastructure](), [instrumentation](), [pipeline](), [pitfalls](), [saas](), [usage-based-billing]() ### AI overview A guide to designing an API call metering pipeline for API-as-a-service products. It covers gateway instrumentation, asynchronous batching, aggregation, customer attribution, failure handling, and reconciliation against gateway logs. ### Source excerpt Build a metering pipeline that bills API calls accurately at high volume. Architecture, batching, and pitfalls for API as a service products. ## Deploying cloud-based engineering workbenches with the Virtual Engineering Workbench on AWS DevFeed: [Deploying cloud-based engineering workbenches with the Virtual Engineering Workbench on AWS]() Original publisher: [Read original article]() Author: Andrea Meroni Published: 2026-04-21T21:38:49Z Content type: tutorial Language: en Sources: [AWS Open Source Blog]() Topics: [Deployment](), [Embedded Software Dev](), [Amazon API Gateway](), [Domain-driven design (DDD)](), [Authorization]() Tags: [amazon-api-gateway](), [amazon-dynamodb](), [amazon-eventbridge](), [aws](), [aws-lambda](), [cloud](), [deployment](), [design-patterns](), [embedded](), [open-source](), [react](), [serverless]() ### AI overview A tutorial for deploying the open-source Virtual Engineering Workbench on AWS. It describes a self-service platform for publishing and provisioning preconfigured development environments, its serverless architecture, and creating and launching a workbench. ### Source excerpt Introduction Organizations in automotive, manufacturing, and embedded systems increasingly rely on cloud-based development environments to reduce hardware dependency and accelerate software delivery. As vehicle architectures shift toward software-defined platforms, engineering teams need access to specialized toolchains, virtual hardware models, and simulation environments that are consistent across sites and reproducible across projects. Provisioning these environments manually [...] ## Top 10 API Gateway Use Cases in System Design DevFeed: [Top 10 API Gateway Use Cases in System Design]() Original publisher: [Read original article]() Author: Ashish Pratap Singh Published: 2026-04-12T12:00:32Z Content type: tutorial Language: en Sources: [AlgoMaster Newsletter]() Topics: [Amazon API Gateway](), [Architecture & Design](), [Microservices](), [API]() Tags: [api-gateway](), [microservices](), [monolith](), [system-design](), [use-cases]() ### AI overview An article about ten API gateway use cases in system design, particularly as systems evolve from monoliths to microservices. The supplied evidence does not detail the individual use cases. ### Source excerpt As your system evolves from a monolith to microservices, a pattern quickly emerges: every service starts rebuilding the same things. ## What is the BFF Pattern? DevFeed: [What is the BFF Pattern?]() Original publisher: [Read original article]() Author: Saurabh Dashora Published: 2026-04-07T08:41:56Z Content type: tutorial Language: en Sources: [System Design Codex]() Topics: [BFF](), [Amazon API Gateway](), [backends](), [client](), [interface](), [resiliency](), [Orchestration](), [rate-limiting]() Tags: [api-gateway](), [authentication](), [backends](), [bff](), [cache-control](), [client](), [decoupling](), [mobile](), [rate-limiting](), [resiliency]() ### AI overview The article explains the Backends-for-Frontends (BFF) pattern, in which dedicated API gateways serve different client types such as web browsers, mobile apps, and public or partner APIs. It describes how BFFs tailor APIs, isolate client-specific logic, and support functions including rate limiting, authentication, header sanitization, and cache control. It also discusses benefits such as resiliency, client-specific optimization, and faster development, along with drawbacks including code duplication and increasing complexity. ### Source excerpt And when do you need it? ## Inside Laravel Nightwatch's Observability Pipeline: Real-Time Event Processing with Amazon MSK and ClickHouse Cloud DevFeed: [Inside Laravel Nightwatch's Observability Pipeline: Real-Time Event Processing with Amazon MSK and ClickHouse Cloud]() Original publisher: [Read original article]() Author: AWS; Laravel; ClickHouse Published: 2025-10-08T15:36:20Z Content type: article Language: en Sources: [ClickHouse Blog]() Topics: [Laravel](), [observability](), [clickhouse](), [Kafka](), [Streaming](), [telemetry](), [AWS Lambda](), [Amazon RDS](), [PostgreSQL](), [Amazon API Gateway](), [Cloud](), [Grafana Cloud Metrics]() Tags: [amazon-api-gateway](), [amazon-rds](), [apache-kafka](), [api](), [aws-lambda](), [clickhouse](), [dashboards](), [json](), [laravel](), [low-latency](), [metrics](), [monitoring](), [observability](), [rds-for-postgresql](), [streaming](), [traces]() ### AI overview This article explains how Laravel Nightwatch processes more than one billion observability events per day using AWS managed services and ClickHouse Cloud. Its streaming-first architecture combines Amazon MSK, AWS Lambda, Amazon API Gateway, Amazon RDS for PostgreSQL, and ClickHouse Cloud to provide scalable ingestion, real-time dashboards, and sub-second analytical queries. ### Source excerpt Learn how Laravel Nightwatch platform process billions of observability events in real time while keeping query latency under a second. ## Announcing the Apollo GraphOS Operator in Public Preview DevFeed: [Announcing the Apollo GraphOS Operator in Public Preview]() Original publisher: [Read original article]() Author: Josh Lambert Published: 2025-08-05T06:00:00Z Content type: release Language: en Sources: [Apollo Blog]() Topics: [GraphQL](), [Kubernetes](), [API Platform](), [Amazon API Gateway](), [GitOps](), [Deployment](), [observability]() Tags: [announcement](), [api](), [api-management](), [api-platform](), [apollo](), [argo-cd](), [datadog](), [declarative](), [deployment](), [gitops](), [graphos](), [graphql](), [kubernetes](), [observability](), [operator](), [preview]() ### AI overview Apollo announced the Apollo GraphOS Operator in public preview. The Kubernetes operator is designed to help teams manage GraphQL deployments, including development environments, progressive production rollouts, rollbacks, monitoring, and declarative or GraphOS Studio-based management. ### Source excerpt Simplifying GraphQL API Management on Kubernetes As GraphQL adoption accelerates within organizations, so too does the need for a scalable, reliable API platform that empowers your developers and accelerates innovation. Today, we're excited to introduce in public preview the Apollo GraphOS Operator: the best way to manage GraphQL deployments within Kubernetes. ## Storage: 10x Larger Uploads, 3x Cheaper Cached Egress, and 2x Egress Quota DevFeed: [Storage: 10x Larger Uploads, 3x Cheaper Cached Egress, and 2x Egress Quota]() Original publisher: [Read original article]() Author: Inian Parameshwaran Published: 2025-07-18T07:00:00Z Content type: release Language: en Sources: [Supabase Blog]() Topics: [Supabase](), [Amazon API Gateway](), [Caching](), [Terraform]() Tags: [3d](), [api](), [api-gateway](), [applications](), [cache](), [cdn](), [media](), [pricing](), [quotas](), [s3](), [saas](), [storage]() ### AI overview Supabase announces 500 GB file uploads for paid plans, cheaper cached egress, and increased cached and uncached egress quotas. The changes support large media files, user-generated data, 3D models, and archival workloads. ### Source excerpt Upload files up to 500 GB with significant egress cost reductions. ## Introducing the Serverless MCP DevFeed: [Introducing the Serverless MCP]() Original publisher: [Read original article]() Author: Serverless Team Published: 2025-04-17T00:00:00Z Content type: release Language: en Sources: [Serverless Blog]() Topics: [MCP](), [ide](), [Amazon API Gateway](), [AWS Lambda](), [debugging](), [Amazon Web Services](), [Monitoring]() Tags: [api-gateway](), [applications](), [aws](), [aws-lambda](), [cloud-computing](), [debugging](), [faas](), [function-as-a-service](), [ide](), [infrastructure-as-code](), [mcp](), [monitoring](), [news](), [serverless](), [serverless-architecture](), [serverless-framework]() ### AI overview The Serverless MCP is presented as a debugging tool that brings AWS Lambda, DynamoDB, and API Gateway state and logs into an IDE. It supports troubleshooting serverless applications with AI-assisted diagnostics and resource monitoring. ### Source excerpt The Serverless MCP is a powerful debugging tool that brings AWS Lambda, DynamoDB, and API Gateway state and logs directly into your IDE. Eliminate AWS console visits while troubleshooting serverless applications with AI-assisted diagnostics and resource monitoring. ## How Tinder Secures Its 500+ Microservices DevFeed: [How Tinder Secures Its 500+ Microservices]() Original publisher: [Read original article]() Author: Richard Oliver Bray Published: 2025-01-08T13:40:48Z Content type: tutorial Language: en Sources: [Hacking Scale by Better Stack]() Topics: [Microservices](), [Security](), [Architecture & Design](), [Amazon API Gateway](), [Authorization](), [Authentication](), [Routing (disambiguation)]() Tags: [api-gateway](), [authentication](), [authorization](), [mesh](), [microservices](), [routing](), [security](), [tls]() ### AI overview This article explains why Tinder's externally accessible services created security and maintenance challenges, and why the team built a customized API gateway to provide consistent session management, scalable configuration, and integration with its Envoy service mesh. ### Source excerpt Tinder's highly customised solution that fixed their microservice security chaos ## Canva incident report: API Gateway outage DevFeed: [Canva incident report: API Gateway outage]() Original publisher: [Read original article]() Author: Brendan Humphreys Published: 2024-12-20T00:00:01Z Content type: article Language: en Sources: [Canva Engineering]() Topics: [incident](), [Amazon API Gateway](), [Deployment](), [Caching](), [Latency](), [Netty](), [Microservices]() Tags: [api](), [api-gateway](), [authentication](), [authorization](), [aws](), [caching](), [cloudflare](), [deployment](), [ecs](), [gateway](), [incident](), [infrastructure](), [java](), [latency](), [locking](), [microservices](), [outage](), [pir](), [post-incident-review](), [post-mortem](), [rate-limiting](), [report](), [s3]() ### AI overview Canva's incident report examines a November 12, 2024 outage that made canva.com unavailable for about 52 minutes. It attributes the outage to failures in the API Gateway cluster involving an editor deployment, a locking issue, and network latency between Cloudflare locations, and describes the incident timeline, mitigation, and prevention steps. ### Source excerpt An incident report for the Canva outage on November 12, 2024. ## Now in private beta: Gremlin Service Mesh Extension DevFeed: [Now in private beta: Gremlin Service Mesh Extension]() Original publisher: [Read original article]() Author: Gavin Cahill Published: 2024-12-04T00:00:00Z Content type: news Language: en Sources: [Gremlin Blog]() Topics: [Cloud Native Ecosystem](), [Resilience](), [Extension](), [Latency](), [Amazon API Gateway](), [Kubernetes](), [experiments]() Tags: [announcements](), [api-gateway](), [experiments](), [extension](), [gremlin](), [kubernetes](), [latency](), [mesh](), [resilience]() ### AI overview Gremlin announces a private beta for its Service Mesh Extension, which enables application-level targeting of specific services and HTTP paths for resilience testing in service meshes such as Istio and Kubernetes. The article explains how this complements IP-based infrastructure targeting and mentions Network and Latency experiments. ### Source excerpt Find out how to safely test applications and services behind service meshes with the Gremlin Service Mesh Extension. ## How Netflix Uses Throttling to Prevent 4 Big Streaming Problems DevFeed: [How Netflix Uses Throttling to Prevent 4 Big Streaming Problems]() Original publisher: [Read original article]() Author: Richard Oliver Bray Published: 2024-08-15T13:02:09Z Content type: article Language: en Sources: [Hacking Scale by Better Stack]() Topics: [Netflix](), [Streaming](), [Back end](), [Amazon API Gateway](), [Cloud]() Tags: [api-gateway](), [backend](), [cloud](), [netflix](), [streaming]() ### AI overview The article explains how Netflix uses throttling to shield content playback from backend problems, including network failures, underscaled services, retry storms, and faulty deployments. It also describes the role of an API Gateway in routing and monitoring requests. ### Source excerpt Netflix reveals their unconventional trick to keep viewers happy ## AWS API Gateway's Request Validation: Navigating the Quirks DevFeed: [AWS API Gateway's Request Validation: Navigating the Quirks]() Original publisher: [Read original article]() Author: Thomas Klein Published: 2024-08-09T12:07:11Z Content type: tutorial Language: en Sources: [Homegate Engineering Blog - Medium]() Topics: [Amazon API Gateway](), [Amazon Web Services](), [API](), [gateway](), [JSON Schema](), [TypeScript](), [configuration](), [enum](), [HTTP]() Tags: [api](), [api-gateway](), [aws](), [aws-api-gateway](), [aws-lambda](), [enum](), [gateway](), [handler](), [http](), [json](), [json-schema](), [middleware](), [middy](), [tests](), [type-safety](), [typescript](), [validation](), [zod]() ### AI overview This tutorial examines AWS API Gateway request validation. It explains that query-parameter presence is checked, but enum values may not be enforced, while POST and PUT payloads are validated with JSON Schema Draft 4. It also discusses generic error messages and TypeScript-based validation approaches. ### Source excerpt AWS API Gateway's request validation follows a specific set of rules that developers should be aware of when setting up their APIs. While it offers some validation features, it's important to understand its scope and limitations. Let's examine how it works with a common API configuration: parameters: - name: offerType in: query required: true description: RENT or BUY schema: type: string enum: - RENT - BUY With this configuration, API Gateway diligently checks for the presence of the query parameter, returning an HTTP 400 error if it's missing. However, it falls short when it comes to validating the actual value. Surprisingly, it would accept "KERMIT" without batting an eye, despite the clear enum specification. This behavior, while documented, can be a source of frustration for developers expecting more comprehensive validation. Interestingly, API Gateway shows more validation prowess with POST and PUT requests. It validates request payloads using JSON Schema Draft 4, demonstrating a somewhat inconsistent approach to input validation across different HTTP methods. Even when it does catch an error, API Gateway's feedback is less than illuminating. Instead of specific error details, you're met with a generic {"message": "Invalid request body"}. For more information, you'll need to dig into the associated log streams, which isn't ideal for surfacing error details in API responses. Example output in AWS console from a failed request validation when a body request validator is setup. API Gateway's validation is handy, but it leaves a lot to be desired. Developers often need to add extra checks for a truly robust API. While API Gateway supports various integrations and Lambda languages, let's focus on TypeScript. TypeScript's strong typing and runtime checks can catch issues early, sparing your users from cryptic error messages. Let's explore how to use this to make your API smarter and your users happier. Option 1: DIY Validation (AKA The "I've Got Trust Issues" Approac ## Pinboard: transforming communication across the newsroom (part 2 of 3) DevFeed: [Pinboard: transforming communication across the newsroom (part 2 of 3)]() Original publisher: [Read original article]() Author: Tom Richards Published: 2024-02-09T10:00:38Z Content type: article Language: en Sources: [Guardian]() Topics: [Tool](), [Angular](), [Amazon API Gateway](), [React](), [Development](), [JavaScript]() Tags: [angular](), [api](), [browser](), [development](), [javascript](), [react](), [tool]() ### AI overview This article explains how Pinboard, an internal discussion and asset-sharing tool at The Guardian, is integrated across newsroom tools. It describes why the project was not implemented as a browser extension or shared library, and outlines its script-based loading, authentication, and API Gateway integration. ### Source excerpt Pinboard is a discussion and asset sharing tool (or rather tool within other tools) which is gradually transforming how the news room communicate as news stories move through the various phases of the production process This is part two of three (part one and part three). Continue reading... ## Secure Java URL encoding and decoding DevFeed: [Secure Java URL encoding and decoding]() Original publisher: [Read original article]() Author: Jura Gorohovsky Published: 2023-08-14T05:00:00Z Content type: article Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [Programming](), [ASCII](), [Security](), [Amazon API Gateway](), [HTML](), [Routing (disambiguation)]() Tags: [acquisition](), [api](), [api-gateway](), [article](), [ascii](), [awareness](), [blog](), [code-security](), [developer](), [draftdotdev](), [engineering](), [how-to](), [html](), [java](), [programming](), [security](), [server](), [snyk-code]() ### AI overview This article explains URL encoding and decoding in Java. It describes percent-encoding characters outside the permitted URL character set, clarifies that URL encoding is not encryption, and discusses use cases such as HTML form input, external API calls, and API gateways. It also explains parsing, interoperability, and security risks caused by unencoded URLs. ### Source excerpt This article discusses Java, why URL encoding and decoding are important, and how to approach it properly. ## Connecting Block Business Units with AWS API Gateway DevFeed: [Connecting Block Business Units with AWS API Gateway]() Original publisher: [Read original article]() Author: Michael Weissbacher Published: 2023-05-18T13:00:00Z Content type: article Language: en Sources: [Square Corner Blog RSS Feed]() Topics: [Amazon API Gateway](), [Amazon Web Services](), [Security](), [SPIFFE](), [SPIRE]() Tags: [api-gateway](), [aws](), [aws-api-gateway](), [engineering](), [network](), [security](), [spiffe](), [spire]() ### AI overview This article explains how Block integrates acquired companies with its internal service mesh using AWS API Gateway as an identity translation layer. The Farcars infrastructure maps acquisition-native identities and IAM-based SigV4 calls to Block-native mutual TLS, enabling isolated and reusable cross-mesh communication. ### Source excerpt Secure cross-mesh communication using in-mesh bastions ## Micro Service Events (AWS EventBridge vs. SNS) DevFeed: [Micro Service Events (AWS EventBridge vs. SNS)]() Original publisher: [Read original article]() Author: Kristian Müller Published: 2022-09-16T12:06:51Z Content type: comparison Language: en Sources: [Homegate Engineering Blog - Medium]() Topics: [event driven](), [Messaging](), [Amazon Web Services](), [Amazon Simple Queue Service (SQS)](), [Publish-subscribe pattern](), [Architecture & Design](), [AWS Lambda](), [Amazon API Gateway](), [DynamoDB](), [Amazon S3](), [TypeScript]() Tags: [api](), [api-gateway](), [architecture](), [aws](), [aws-eventbridge](), [aws-sns](), [data](), [data-processing](), [database](), [dynamodb](), [event](), [event-driven](), [eventbridge](), [eventbus](), [events](), [gateway](), [lambda](), [messaging](), [microservice-architecture](), [s3](), [sns](), [sqs](), [typescript]() ### AI overview This article examines Homegate's event-driven microservice architecture on AWS and compares Amazon SNS with EventBridge as messaging infrastructure. It describes how services use SNS, SQS, Lambda, API Gateway, DynamoDB, and S3, and explains that EventBridge has a different focus, so replacing SNS is not necessarily the right question. ### Source excerpt During the last few years, we've been busy rebuilding the Homegate platform in an event driven, micro service architecture based on AWS. One of the most important buildings blocks, or shall we rather say the mortar that connects the building blocks, is the way our services send events to each other. While Amazon offers its notification service SNS since more than 12 years; in 2019 it started a newcomer in the messaging bus field by introducing EventBridge. This was very interesting to us as we're using SNS a lot. Bus on a Bridge (Photo by "Blue Elf" on Wikimedia Commons) As EventBridge was introduced and gained traction we asked ourselves what advantaged we would gain by switching our SNS based service glue to EventBridge. Maybe this turned out to be the wrong question for us. Let's look at our system to see why. Micro Services Connected by SNS Homegate is connecting dozens of services via SNS right now. Those services range from single purpose Lambda functions written in TypeScript to database heavy services using Aurora or DynamoDB and Step Functions sending events to other services. Some of the services are also interfacing external APIs such as Salesforce or SendGrid. Here our Lambda functions can call APIs when needed. On the other hand, we have web services to be called as APIs by other systems and end users. This is mostly achieved via API Gateway. A typical service connects to the system by subscribing to events needed to fulfill its purpose. Those inbound SNS events are then ingested via SQS allowing for orderly data processing and DLQs to handle errors. Outgoing results are pushed back to the system in form of events to a SNS topics. As Marko Savic has pointed out, we're also utilizing S3 to store and replay those events if needed. Basic AWS Lambda function connected via SNS If we would replace the SNS topic by streams on the EventBridge we would initially gain the same functionality by utilizing SQS as well. However, EventBridge has a different focus. Let [Next page]()