#AmazonApiGateway
5/ Se você é arquiteto ou dev lead, corre ler! Mão na massa e #deployemsexta (ou não! 🙈) 🍮 #PudimDrivenDevelopment #AmazonAPIGateway #AWSLambda #AmazonDynamoDB
July 24, 2025 at 6:01 PM
Amazon API Gateway introduces routing rules for REST APIs

Amazon API Gateway now supports routing rules for REST APIs using custom domain names. This new capability enables you to dynamically route incoming requests based on HTTP header values, URL base p...

#AWS #AmazonApiGateway #AwsGovcloudUs
Amazon API Gateway introduces routing rules for REST APIs
Amazon API Gateway now supports routing rules for REST APIs using custom domain names. This new capability enables you to dynamically route incoming requests based on HTTP header values, URL base paths, or a combination of both. This flexibility enables various use cases, including A/B testing, API versioning, and dynamic backend selection. To use this feature, you define routing rules by assigning priorities, defining conditions (HTTP headers, URL paths, or both), and associating actions. API Gateway then evaluates these rules in priority order with lower numbers taking precedence. When a request meets all conditions in a rule, API Gateway routes it to the configured REST API ID and stage. By implementing routing logic directly within API Gateway, you can eliminate proxy layers and complex URL structures while maintaining granular routing control over your API traffic. This feature is supported on both public and private REST APIs and is compatible with existing API mappings. Routing rules for custom domain names are available in all https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/ including the AWS GovCloud (US) Regions. To learn more, please refer to the https://aws.amazon.com/blogs/compute/dynamically-routing-requests-with-amazon-api-gateway-routing-rules/and the https://docs.aws.amazon.com/apigateway/latest/developerguide/rest-api-routing-mode.html.  
aws.amazon.com
June 4, 2025 at 5:05 PM
🆕 AWS SAM now supports custom domain names for private REST APIs in Amazon API Gateway, allowing developers to easily configure and manage private APIs with custom domains directly in their SAM templates.

#AWS #AmazonApiGateway #AwsServerlessApplicationModelSam
AWS SAM now supports Amazon API Gateway Custom Domain Names for private REST APIs
AWS Serverless Application Model (AWS SAM) now supports custom domain names for private REST APIs feature of Amazon API Gateway. Developers building serverless applications using SAM can now seamlessly incorporate custom domain names for private APIs directly in their SAM templates, eliminating the need to configure custom domain names separately using other tools. API Gateway allows you to create a custom domain name, like private.example.com, for your private REST APIs, enabling you to provide API callers with a simpler and intuitive URL. With a private custom domain name, you can reduce complexity, configure security measures with TLS encryption, and manage the lifecycle of the TLS certificate associated with your domain name. AWS SAM is a collection of open-source tools (e.g. SAM, SAM CLI) that make it easy for you to build and manage serverless applications through the authoring, building, deploying, testing, and monitoring phases of your development lifecycle. This launch enables you to easily configure custom domain names for your private REST APIs using SAM and SAM CLI. To get started, update SAM CLI to the latest version and modify your SAM template to set the EndpointConfiguration to PRIVATE and specify a policy document in the Policy field in the Domain property of the AWS::Serverless::Api resource. SAM will then automatically generate DomainNameV2 and BasePathMappingV2 resources under AWS::Serverless::Api. To learn more, visit the AWS SAM documentation. You can learn more about custom domain name for private REST APIs in API Gateway blog post.
aws.amazon.com
April 8, 2025 at 6:40 PM
🆕 AWS API Gateway now supports dual-stack (IPv4/IPv6) endpoints for all API types and custom domains, enabling gradual IPv6 transition. No extra charges. Available in all commercial and AWS GovCloud regions.

#AWS #AmazonApiGateway #AwsGovcloudUs
API Gateway launches support for dual-stack (IPv4 and IPv6) endpoints
Amazon API Gateway (APIGW) introduces dual-stack support for all endpoint types, custom domains and APIGW management APIs. You can now configure your REST, HTTP or WebSocket APIs as well as custom domains, to accept calls from IPv6 clients alongside the existing IPv4 support. You can also call APIGW management APIs from dual-stack clients. With simultaneous support for both IPv4 and IPv6 clients, you are able to gradually transition from IPv4 to IPv6 environments, without needing to switch all over at once. This enables you to meet IPv6 compliance requirements and avoid IPv4 address constraints. There is no additional charge for this support. This support is now available in all API Gateway commercial and AWS GovCloud (US) Regions. To learn more, see API Gateway developer guide and IPv6 on AWS.
aws.amazon.com
March 31, 2025 at 11:40 PM
#うひーメモ
2023-11-01 09:11:07
WebSocket APIをAmazon API Gatewayで実装してみる
#Program
#websocketapi
#amazonapigateway
#apigateway
WebSocket APIをAmazon API Gatewayで実装してみる
概要こんにちはジャパン・グローバルゲートウェイの中谷です現在APIGatewayの勉強をしているのですがやはり机上の知識だけでは挙動を把握しづらいところがあるのでWebSocketA
qiita.com
November 1, 2023 at 12:11 AM
API Gateway launches support for dual-stack (IPv4 and IPv6) endpoints

Amazon API Gateway (APIGW) introduces dual-stack support for all endpoint types, custom domains and APIGW management APIs. You can now configure your REST, HTTP or WebSocket APIs as wel...

#AWS #AmazonApiGateway #AwsGovcloudUs
API Gateway launches support for dual-stack (IPv4 and IPv6) endpoints
Amazon API Gateway (APIGW) introduces dual-stack support for all endpoint types, custom domains and APIGW management APIs. You can now configure your REST, HTTP or WebSocket APIs as well as custom domains, to accept calls from IPv6 clients alongside the existing IPv4 support. You can also call APIGW management APIs from dual-stack clients. With simultaneous support for both IPv4 and IPv6 clients, you are able to gradually transition from IPv4 to IPv6 environments, without needing to switch all over at once. This enables you to meet IPv6 compliance requirements and avoid IPv4 address constraints. There is no additional charge for this support. This support is now available in all API Gateway commercial and AWS GovCloud (US) Regions. To learn more, see https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-ip-address-type.html and https://docs.aws.amazon.com/whitepapers/latest/ipv6-on-aws/internet-protocol-version-6.html.  
aws.amazon.com
April 1, 2025 at 12:05 AM
✍️ New blog post by Indika_Wimalasuriya

Amazon API Gateway Observability Best Practices with Datadog

#amazonapigateway #aws #observability #sre
Amazon API Gateway Observability Best Practices with Datadog
AWS API Gateway is a fully managed service from AWS that allows you to create, publish, and maintain...
dev.to
August 3, 2025 at 4:39 AM
Quinta feira.

Tag do recurso é "AMAZONAPIGATEWAY"

E ao invés de eu ler "Amazon API Gateway" como um ser humano normal...

Li "Amazona Pig Ate Way"
June 27, 2024 at 11:55 AM
AWS SAM now supports Amazon API Gateway Custom Domain Names for private REST APIs

https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/what-is-sam.html (AWS SAM) now supports custom domain names for private RES...

#AWS #AmazonApiGateway #AwsServerlessApplicationModelSam
AWS SAM now supports Amazon API Gateway Custom Domain Names for private REST APIs
https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/what-is-sam.html (AWS SAM) now supports custom domain names for private REST APIs feature of https://docs.aws.amazon.com/apigateway/latest/developerguide/welcome.html. Developers building serverless applications using SAM can now seamlessly incorporate custom domain names for private APIs directly in their SAM templates, eliminating the need to configure custom domain names separately using other tools. API Gateway allows you to create a custom domain name, like private.example.com, for your private REST APIs, enabling you to provide API callers with a simpler and intuitive URL. With a private custom domain name, you can reduce complexity, configure security measures with TLS encryption, and manage the lifecycle of the TLS certificate associated with your domain name. AWS SAM is a collection of open-source tools (e.g. SAM, SAM CLI) that make it easy for you to build and manage serverless applications through the authoring, building, deploying, testing, and monitoring phases of your development lifecycle. This launch enables you to easily configure custom domain names for your private REST APIs using SAM andhttps://docs.aws.amazon.com/serverless-application-model/latest/developerguide/using-sam-cli.html. To get started, update SAM CLI to the latest version and modify your SAM template to set the EndpointConfiguration to PRIVATE and specify a policy document in the Policy field in the Domain property of the AWS::Serverless::Api resource. SAM will then automatically generate DomainNameV2 and BasePathMappingV2 resources under AWS::Serverless::Api. To learn more, visit the https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/sam-resource-api.html. You can learn more about custom domain name for private REST APIs in https://aws.amazon.com/blogs/compute/implementing-custom-domain-names-for-private-endpoints-with-amazon-api-gateway/.  
aws.amazon.com
April 8, 2025 at 7:05 PM
Amazon API Gateway now supports Custom Domain Name for private REST APIs

Amazon API Gateway (APIGW) now gives you the ability to manage your private REST APIs using custom user-friendly private DNS name like private.example.com, simplifying API discovery....

#AWS #AwsGovcloudUs #AmazonApiGateway
Amazon API Gateway now supports Custom Domain Name for private REST APIs
Amazon API Gateway (APIGW) now gives you the ability to manage your private REST APIs using custom user-friendly private DNS name like private.example.com, simplifying API discovery. This feature enhances your security posture by continuing to encrypt your private API traffic with Transport Layer Security (TLS), while providing full control over managing the lifecycle of the TLS certificate associated with your domain. API providers can get started with this feature in four simple steps using APIGW console and/or API(s). First, create a private custom domain. Second, configure an Amazon Certificate Manager (ACM) provided or imported certificate for the domain. Third, map multiple private APIs using base path mappings. Fourth, control invokes to the domain using resource policies. API providers can optionally share the domain across accounts using Amazon Resource Access Manager (RAM) to provide consumers the ability to access APIs from different accounts. Once a domain is shared using RAM, a consumer can use VPC endpoint(s) to invoke multiple private custom domains across accounts. Custom domain name for private REST APIs is now available on API Gateway in https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/ including the AWS GovCloud (US) Regions. Please visit the https://docs.aws.amazon.com/apigateway/latest/developerguide/apigateway-private-custom-domains.html and https://aws.amazon.com/blogs/compute/implementing-custom-domain-names-for-private-endpoints-with-amazon-api-gateway/ to learn more.  
aws.amazon.com
November 21, 2024 at 10:05 PM
Amazon API Gateway now supports HTTP APIs, mTLS, multi-level base path mappings, and WAF in additional regions

https://aws.amazon.com/api-gateway/ (APIGW) now supports all features of HTTP APIs as well as Mutual TLS and multi-level base path mappings on REST APIs in the...

#AWS #AmazonApiGateway
Amazon API Gateway now supports HTTP APIs, mTLS, multi-level base path mappings, and WAF in additional regions
https://aws.amazon.com/api-gateway/ (APIGW) now supports all features of HTTP APIs as well as Mutual TLS and multi-level base path mappings on REST APIs in the following additional Regions: Middle East (UAE), Asia Pacific (Jakarta), Asia Pacific (Osaka), Asia Pacific (Hyderabad), Asia Pacific (Melbourne), Europe (Zurich), Europe (Spain), Israel (Tel Aviv), and Canada West (Calgary). AWS Web Application Firewall (WAF) for REST APIs is now available in two additional regions: Asia Pacific (Kuala Lumpur) and Canada West (Calgary). HTTP APIs simplify API development for serverless applications with a simpler user interface that includes support for OAuth2.0 and automatic deployments. Mutual TLS enhances security by authenticating x509 certificate based identities at the APIGW. Multi-level base path mappings enable routing requests based on segments in custom domain paths, supporting path-based versioning and traffic redirection. Integration of AWS WAF offers APIs protections against common web exploits through configurable rules that allow, block, or monitor web requests. To learn more, see https://docs.aws.amazon.com/apigateway/latest/developerguide/welcome.html.
aws.amazon.com
March 4, 2025 at 12:05 AM
🆕 Amazon API Gateway now supports Custom Domain Name for private REST APIs

#AWS #AwsGovcloudUs #AmazonApiGateway
Amazon API Gateway now supports Custom Domain Name for private REST APIs
Amazon API Gateway (APIGW) now gives you the ability to manage your private REST APIs using custom user-friendly private DNS name like private.example.com, simplifying API discovery. This feature enhances your security posture by continuing to encrypt your private API traffic with Transport Layer Security (TLS), while providing full control over managing the lifecycle of the TLS certificate associated with your domain. API providers can get started with this feature in four simple steps using APIGW console and/or API(s). First, create a private custom domain. Second, configure an Amazon Certificate Manager (ACM) provided or imported certificate for the domain. Third, map multiple private APIs using base path mappings. Fourth, control invokes to the domain using resource policies. API providers can optionally share the domain across accounts using Amazon Resource Access Manager (RAM) to provide consumers the ability to access APIs from different accounts. Once a domain is shared using RAM, a consumer can use VPC endpoint(s) to invoke multiple private custom domains across accounts. Custom domain name for private REST APIs is now available on API Gateway in all AWS Regions, including the AWS GovCloud (US) Regions. Please visit the API Gateway documentation and AWS blog post to learn more.
aws.amazon.com
November 21, 2024 at 9:23 PM
🆕 Amazon API Gateway adds HTTP APIs, mTLS, multi-level base path mappings, and WAF in new regions. Features include simplified serverless API development, enhanced security, and protection against web exploits. Available in Middle East, Asia Pacific, Europe, and Canada.

#AWS #AmazonApiGateway
Amazon API Gateway now supports HTTP APIs, mTLS, multi-level base path mappings, and WAF in additional regions
Amazon API Gateway (APIGW) now supports all features of HTTP APIs as well as Mutual TLS and multi-level base path mappings on REST APIs in the following additional Regions: Middle East (UAE), Asia Pacific (Jakarta), Asia Pacific (Osaka), Asia Pacific (Hyderabad), Asia Pacific (Melbourne), Europe (Zurich), Europe (Spain), Israel (Tel Aviv), and Canada West (Calgary). AWS Web Application Firewall (WAF) for REST APIs is now available in two additional regions: Asia Pacific (Kuala Lumpur) and Canada West (Calgary). HTTP APIs simplify API development for serverless applications with a simpler user interface that includes support for OAuth2.0 and automatic deployments. Mutual TLS enhances security by authenticating x509 certificate based identities at the APIGW. Multi-level base path mappings enable routing requests based on segments in custom domain paths, supporting path-based versioning and traffic redirection. Integration of AWS WAF offers APIs protections against common web exploits through configurable rules that allow, block, or monitor web requests. To learn more, see API Gateway developer guide.
aws.amazon.com
March 3, 2025 at 11:40 PM