{"slug": "kong-gateway-enterprise-3-12-x-x-eol", "title": "Kong Gateway Enterprise 3.12.x.x EOL", "summary": "Kong released Kong Gateway 3.16, adding runtime control, API monetization, and FIPS 140-3 support, the U.S. and Canadian government standard for validating cryptographic modules issued by NIST and CCCS and enforced through CMVP. Kong also detailed Kong Gateway 3.14, which simplifies security and policy configuration, and reported that its Konnect Terraform provider has surpassed 300,000 installs in nearly a year with 1.7 times as many resources available. Kong's Alex Drag outlined six stages for standing up a production AI agent, including React and Discover, the latter requiring MCP Servers.", "body_md": "Consider a bank using an AI agent to investigate potentially fraudulent transactions. A transaction is processed and the bank’s fraud detection system identifies suspicious activity. That event is published to Kafka: fraud.suspected The bank’s Fraud\n\nAlex Drag\n\n# Kong API Gateway 3.16: Runtime control, API monetization, and FIPS 140-3\n\nIf you've run Kong at scale, you know the moment: a spike in 5xxs from one specific data plane node, a customer opening a ticket about intermittent failures, or a partner integration that fails calls no one else does. Debug-level logs would tell you\n\nFIPS 140-3 is the U.S. and Canadian government standard for validating cryptographic modules - the code that does encryption, key generation, and digital signatures. It's issued by NIST and CCCS and enforced through CMVP, the Cryptographic Module Va\n\nStanding up a production agent means taking it through six stages: React : the agent must be able to react to events as they occur internal or external to the business Discover : Once running, can the agent find what it needs? This means MCP Servers\n\nAlex Drag\n\n# Kong Gateway 3.14: More Control, Less Toil With Simplified Security and Policies\n\nManaging gateway configurations at scale is harder than it looks. When a plugin needs to apply to most routes, but not all, teams could either duplicate configuration across routes and violate DRY (“Don’t Repeat Yourself”) principles, or write custo\n\nIt’s been almost a year since we released our Konnect Terraform provider . In that time we’ve seen over 300,000 installs, have 1.7 times as many resources available, and have expanded the provider to include data sources to enable federated managem\n\nMichael Heap\n\n# Event-Driven AI: Agents Shouldn’t Have to Keep Asking if Something Happened\n\nConsider a bank using an AI agent to investigate potentially fraudulent transactions. A transaction is processed and the bank’s fraud detection system identifies suspicious activity. That event is published to Kafka: fraud.suspected The bank’s Fraud\n\nAlex Drag\n\n# Kong API Gateway 3.16: Runtime control, API monetization, and FIPS 140-3\n\nIf you've run Kong at scale, you know the moment: a spike in 5xxs from one specific data plane node, a customer opening a ticket about intermittent failures, or a partner integration that fails calls no one else does. Debug-level logs would tell you\n\nFIPS 140-3 is the U.S. and Canadian government standard for validating cryptographic modules - the code that does encryption, key generation, and digital signatures. It's issued by NIST and CCCS and enforced through CMVP, the Cryptographic Module Va\n\nStanding up a production agent means taking it through six stages: React : the agent must be able to react to events as they occur internal or external to the business Discover : Once running, can the agent find what it needs? This means MCP Servers\n\nAlex Drag\n\n# Kong Gateway 3.14: More Control, Less Toil With Simplified Security and Policies\n\nManaging gateway configurations at scale is harder than it looks. When a plugin needs to apply to most routes, but not all, teams could either duplicate configuration across routes and violate DRY (“Don’t Repeat Yourself”) principles, or write custo\n\nIt’s been almost a year since we released our Konnect Terraform provider . In that time we’ve seen over 300,000 installs, have 1.7 times as many resources available, and have expanded the provider to include data sources to enable federated managem\n\nMichael Heap\n\n# Event-Driven AI: Agents Shouldn’t Have to Keep Asking if Something Happened\n\nConsider a bank using an AI agent to investigate potentially fraudulent transactions. A transaction is processed and the bank’s fraud detection system identifies suspicious activity. That event is published to Kafka: fraud.suspected The bank’s Fraud\n\nAlex Drag\n\n# Kong API Gateway 3.16: Runtime control, API monetization, and FIPS 140-3\n\nIf you've run Kong at scale, you know the moment: a spike in 5xxs from one specific data plane node, a customer opening a ticket about intermittent failures, or a partner integration that fails calls no one else does. Debug-level logs would tell you\n\nFIPS 140-3 is the U.S. and Canadian government standard for validating cryptographic modules - the code that does encryption, key generation, and digital signatures. It's issued by NIST and CCCS and enforced through CMVP, the Cryptographic Module Va\n\nStanding up a production agent means taking it through six stages: React : the agent must be able to react to events as they occur internal or external to the business Discover : Once running, can the agent find what it needs? This means MCP Servers\n\nAlex Drag\n\n# Kong Gateway 3.14: More Control, Less Toil With Simplified Security and Policies\n\nManaging gateway configurations at scale is harder than it looks. When a plugin needs to apply to most routes, but not all, teams could either duplicate configuration across routes and violate DRY (“Don’t Repeat Yourself”) principles, or write custo\n\nIt’s been almost a year since we released our Konnect Terraform provider . In that time we’ve seen over 300,000 installs, have 1.7 times as many resources available, and have expanded the provider to include data sources to enable federated managem\n\nMichael Heap\n\n## Ready to see Kong in action?\n\nGet a personalized walkthrough of Kong's platform tailored to your architecture, use cases, and scale requirements.", "url": "https://wpnews.pro/news/kong-gateway-enterprise-3-12-x-x-eol", "canonical_source": "https://konghq.com/blog/product-releases/kong-gateway-enterprise-3-12-x-x-eol", "published_at": "2026-10-06 20:33:00+00:00", "updated_at": "2026-10-06 20:47:43.142291+00:00", "lang": "en", "topics": ["ai-agents", "ai-infrastructure", "developer-tools", "agent-protocols"], "entities": ["Kong", "Kong Gateway 3.16", "Kong Gateway 3.14", "Konnect Terraform provider", "NIST", "CCCS", "CMVP", "Alex Drag"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/kong-gateway-enterprise-3-12-x-x-eol", "markdown": "https://wpnews.pro/news/kong-gateway-enterprise-3-12-x-x-eol.md", "text": "https://wpnews.pro/news/kong-gateway-enterprise-3-12-x-x-eol.txt", "jsonld": "https://wpnews.pro/news/kong-gateway-enterprise-3-12-x-x-eol.jsonld"}}