[{"data":1,"prerenderedAt":303},["ShallowReactive",2],{"content-svc-api-gateway-paved-path-building-an-api-platform-on-aws-plan":3},{"markdown":4,"frontMatterAttributes":5,"bodyRaw":33,"menu":34,"menuType":298,"isCollapseableMenu":37,"nextDocItem":83,"previousDocItem":60,"contributorPaths":299,"contentName":302,"slug":79,"readingTime":76},"\u003Ch2>Protocol selection\u003C\u002Fh2>\n\u003Cp>As you start planning the API, you will need to pick an appropriate protocol for the API based on the workload characteristics. API Gateway supports RESTful (REST and HTTP) and WebSocket APIs.\u003C\u002Fp>\n\u003Cp>API Gateway creates RESTful APIs that:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Are HTTP-based.\u003C\u002Fli>\n\u003Cli>Enable stateless client-server communication.\u003C\u002Fli>\n\u003Cli>Implement standard HTTP methods such as GET, POST, PUT, PATCH, and DELETE.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>API Gateway creates WebSocket APIs that:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Adhere to the WebSocket protocol, which enables stateful, full-duplex communication between client and server.\u003C\u002Fli>\n\u003Cli>Route incoming messages based on message content.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cimg src=\"\u002Fassets\u002Fexternal\u002Fservice\u002Fapi-gateway\u002Fpaved-path\u002Fbuilding-an-api-platform-on-aws\u002Fassets\u002F3_protocols.png\" alt=\"API Protocols\">\u003C\u002Fp>\n\u003Ch2>Endpoint type selection\u003C\u002Fh2>\n\u003Cp>Next, select the endpoint type for the API based on the origin of API traffic.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Edge-optimized:\u003C\u002Fstrong> Best for geographically distributed clients. API requests are routed to the nearest CloudFront Point of Presence (POP). \u003C\u002Fp>\n\u003Cp>\u003Cstrong>Regional:\u003C\u002Fstrong> Intended for clients in the same region. When a client running on an EC2 instance calls an API in the same region, or when an API should serve a small number of clients with high demands, a regional API reduces the connection overhead.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Private:\u003C\u002Fstrong> Endpoint that can only be accessed from your Amazon Virtual Private Cloud (VPC) using an interface VPC endpoint.\u003C\u002Fp>\n\u003Cp>\u003Cem>Note: You can change endpoint type later if necessary.\u003C\u002Fem>\u003C\u002Fp>\n\u003Ch2>API topology\u003C\u002Fh2>\n\u003Cp>In settings with a large number of APIs, you must also choose API topology based on consumption patterns and needs such as tenant isolation in SaaS implementations. The common topologies are centralized and distributed APIs:\u003C\u002Fp>\n\u003Cp>\u003Cimg src=\"\u002Fassets\u002Fexternal\u002Fservice\u002Fapi-gateway\u002Fpaved-path\u002Fbuilding-an-api-platform-on-aws\u002Fassets\u002F3_topology.png\" alt=\"API topology\">\u003C\u002Fp>\n\u003Cp>Each of the topologies have their own advantages and disadvantages. Centralized APIs allow for the simpler API branding and centralized governance, security, and observability. Distributed APIs are easier to implement as they do not require access to the shared resources accounts.\u003C\u002Fp>\n\u003Cp>\u003Cem>Note: See documentation articles on \u003Ca href=\"https:\u002F\u002Fdocs.aws.amazon.com\u002Fapigateway\u002Flatest\u002Fdeveloperguide\u002Frest-api-mappings.html\">API mappings\u003C\u002Fa> and \u003Ca href=\"https:\u002F\u002Fdocs.aws.amazon.com\u002Fapigateway\u002Flatest\u002Fdeveloperguide\u002Frest-api-routing-rules.html\">routing rules\u003C\u002Fa> for more details on how to implement centralized APIs\u003C\u002Fem>\u003C\u002Fp>\n",{"title":6,"order":7,"resources":8},"Plan",3,[9,13,17,21,24,27,30],{"link":10,"text":11,"type":12},"https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=U6Zz_Bj6yEY","Building APIs: Choosing the best API solution & strategy for workloads","Video",{"link":14,"text":15,"type":16},"https:\u002F\u002Fdocs.aws.amazon.com\u002Fwhitepapers\u002Flatest\u002Fbest-practices-api-gateway-private-apis-integration\u002Fbest-practices-api-gateway-private-apis-integration.html","Best Practices for Designing Amazon API Gateway Private APIs and Private Integration","Whitepaper",{"link":18,"text":19,"type":20},"https:\u002F\u002Faws.amazon.com\u002Fblogs\u002Fcompute\u002Fimplementing-multi-region-failover-for-amazon-api-gateway\u002F","Implementing multi-Region failover for Amazon API Gateway","Blog",{"link":22,"text":23,"type":20},"https:\u002F\u002Faws.amazon.com\u002Fblogs\u002Fcompute\u002Farchitecting-multiple-microservices-behind-a-single-domain-with-amazon-api-gateway\u002F","Architecting multiple microservices behind a single domain with Amazon API Gateway",{"link":25,"text":26,"type":20},"https:\u002F\u002Faws.amazon.com\u002Fblogs\u002Fcompute\u002Fdynamically-routing-requests-with-amazon-api-gateway-routing-rules\u002F","Dynamically routing requests with Amazon API Gateway routing rules",{"link":28,"text":29,"type":20},"https:\u002F\u002Faws.amazon.com\u002Fblogs\u002Fcompute\u002Fusing-multiple-segments-in-amazon-api-gateway-base-path-mapping\u002F","Using multiple segments in Amazon API Gateway base path mapping",{"link":31,"text":32,"type":12},"https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=JDbkoICzQro","Building well architected API Gateway APIs | Serverless Office Hours","## Protocol selection\nAs you start planning the API, you will need to pick an appropriate protocol for the API based on the workload characteristics. API Gateway supports RESTful (REST and HTTP) and WebSocket APIs.\n\nAPI Gateway creates RESTful APIs that:\n- Are HTTP-based.\n- Enable stateless client-server communication.\n- Implement standard HTTP methods such as GET, POST, PUT, PATCH, and DELETE.\n\nAPI Gateway creates WebSocket APIs that:\n- Adhere to the WebSocket protocol, which enables stateful, full-duplex communication between client and server.\n- Route incoming messages based on message content.\n\n![API Protocols](\u002Fassets\u002Fexternal\u002Fservice\u002Fapi-gateway\u002Fpaved-path\u002Fbuilding-an-api-platform-on-aws\u002Fassets\u002F3_protocols.png)\n\n## Endpoint type selection\nNext, select the endpoint type for the API based on the origin of API traffic.\n\n**Edge-optimized:** Best for geographically distributed clients. API requests are routed to the nearest CloudFront Point of Presence (POP). \n\n**Regional:** Intended for clients in the same region. When a client running on an EC2 instance calls an API in the same region, or when an API should serve a small number of clients with high demands, a regional API reduces the connection overhead.\n\n**Private:** Endpoint that can only be accessed from your Amazon Virtual Private Cloud (VPC) using an interface VPC endpoint.\n\n*Note: You can change endpoint type later if necessary.*\n\n## API topology\nIn settings with a large number of APIs, you must also choose API topology based on consumption patterns and needs such as tenant isolation in SaaS implementations. The common topologies are centralized and distributed APIs:\n\n![API topology](\u002Fassets\u002Fexternal\u002Fservice\u002Fapi-gateway\u002Fpaved-path\u002Fbuilding-an-api-platform-on-aws\u002Fassets\u002F3_topology.png)\n\nEach of the topologies have their own advantages and disadvantages. Centralized APIs allow for the simpler API branding and centralized governance, security, and observability. Distributed APIs are easier to implement as they do not require access to the shared resources accounts.\n\n*Note: See documentation articles on [API mappings](https:\u002F\u002Fdocs.aws.amazon.com\u002Fapigateway\u002Flatest\u002Fdeveloperguide\u002Frest-api-mappings.html) and [routing rules](https:\u002F\u002Fdocs.aws.amazon.com\u002Fapigateway\u002Flatest\u002Fdeveloperguide\u002Frest-api-routing-rules.html) for more details on how to implement centralized APIs*",[35,57,65,80,122,171,195,218,242,264,277],{"title":36,"collapsible":37,"isCollapsed":38,"content":39},"Introduction",false,true,[40],{"title":36,"order":41,"learningGoals":42,"prerequisite":45,"resources":48,"time":53,"path":54,"id":55,"link":56},1,[43,44],"Understand API lifecycle and an AWS point of view on building an API platform using Amazon API Gateway.","Learn AWS options and partner solutions to build an API platform with Amazon API Gateway.",[46,47],"Understanding of API management","Understanding of Amazon API Gateway",[49],{"link":50,"text":51,"type":52},"https:\u002F\u002Faws.amazon.com\u002Fapi-gateway\u002F","Learn more about Amazon API Gateway","text","1 min","introduction","introduction.md","\u002Fcontent\u002Fservice\u002Fapi-gateway\u002Fpaved-path\u002Fbuilding-an-api-platform-on-aws\u002Fintroduction",{"title":58,"collapsible":37,"isCollapsed":38,"content":59},"API Lifecycle",[60],{"title":58,"order":61,"time":53,"path":62,"id":63,"link":64},2,"api_lifecycle","api_lifecycle.md","\u002Fcontent\u002Fservice\u002Fapi-gateway\u002Fpaved-path\u002Fbuilding-an-api-platform-on-aws\u002Fapi_lifecycle",{"title":6,"collapsible":37,"isCollapsed":37,"content":66},[67],{"title":6,"order":7,"resources":68,"time":76,"path":77,"id":78,"link":79},[69,70,71,72,73,74,75],{"link":10,"text":11,"type":12},{"link":14,"text":15,"type":16},{"link":18,"text":19,"type":20},{"link":22,"text":23,"type":20},{"link":25,"text":26,"type":20},{"link":28,"text":29,"type":20},{"link":31,"text":32,"type":12},"2 min","plan","plan.md","\u002Fcontent\u002Fservice\u002Fapi-gateway\u002Fpaved-path\u002Fbuilding-an-api-platform-on-aws\u002Fplan",{"title":81,"collapsible":37,"isCollapsed":38,"content":82},"Develop\u002FTest",[83],{"title":81,"order":84,"resources":85,"time":118,"path":119,"id":120,"link":121},4,[86,89,92,95,98,101,104,108,111,115],{"link":87,"text":88,"type":12},"https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=yfJZc3sJZ8E","I didn’t know Amazon API Gateway did that",{"link":90,"text":91,"type":20},"https:\u002F\u002Faws.amazon.com\u002Fblogs\u002Fcompute\u002Fbuilding-responsive-apis-with-amazon-api-gateway-response-streaming\u002F","Building responsive APIs with Amazon API Gateway response streaming",{"link":93,"text":94,"type":20},"https:\u002F\u002Faws.amazon.com\u002Fblogs\u002Fcompute\u002Fimplementing-custom-domain-names-for-private-endpoints-with-amazon-api-gateway\u002F","Implementing custom domain names for private endpoints with Amazon API Gateway",{"link":96,"text":97,"type":20},"https:\u002F\u002Faws.amazon.com\u002Fblogs\u002Fcompute\u002Fbuild-scalable-rest-apis-using-amazon-api-gateway-private-integration-with-application-load-balancer\u002F","Build scalable REST APIs using Amazon API Gateway private integration with Application Load Balancer",{"link":99,"text":100,"type":20},"https:\u002F\u002Faws.amazon.com\u002Fblogs\u002Fopensource\u002Fcreate-restful-apis-on-aws-with-openapi-specification-with-no-coding\u002F","Create RESTful APIs on AWS with OpenAPI Specification (With No Coding)",{"link":102,"text":103,"type":20},"https:\u002F\u002Faws.amazon.com\u002Fblogs\u002Fcompute\u002Fautomating-event-validation-with-amazon-eventbridge-schema-discovery\u002F","Automating event validation with Amazon EventBridge Schema Discovery",{"link":105,"text":106,"type":107},"https:\u002F\u002Fgithub.com\u002Faws-samples\u002Fserverless-samples\u002Ftree\u002Fmain\u002Fserverless-rest-api","Sample REST API implementations","Example",{"link":109,"text":110,"type":107},"https:\u002F\u002Fgithub.com\u002Faws-samples\u002Fserverless-samples\u002Ftree\u002Fmain\u002Fapigw-ai-agents","API developer experience customization and centralized guidance using AI Agents",{"link":112,"text":113,"type":114},"https:\u002F\u002Fcatalog.workshops.aws\u002Fapigateway","The Amazon API Gateway Workshop","Workshop",{"link":116,"text":117,"type":114},"https:\u002F\u002Fcatalog.workshops.aws\u002Fserverless-patterns\u002Fen-US","Serverless Patterns","3 min","develop","develop.md","\u002Fcontent\u002Fservice\u002Fapi-gateway\u002Fpaved-path\u002Fbuilding-an-api-platform-on-aws\u002Fdevelop",{"title":123,"collapsible":37,"isCollapsed":38,"content":124},"Secure",[125],{"title":123,"order":126,"resources":127,"time":118,"path":168,"id":169,"link":170},5,[128,132,135,139,142,145,148,151,154,157,160,163,166,167],{"link":129,"text":130,"type":131},"https:\u002F\u002Fdocs.aws.amazon.com\u002Fapigateway\u002Flatest\u002Fdeveloperguide\u002Fsecurity.html","Security in Amazon API Gateway","Documentation",{"link":133,"text":134,"type":16},"https:\u002F\u002Fdocs.aws.amazon.com\u002Fwhitepapers\u002Flatest\u002Fsecurity-overview-amazon-api-gateway\u002Fabstract-and-introduction.html","Security Overview of Amazon API Gateway",{"link":136,"text":137,"type":138},"https:\u002F\u002Fserverlessland.com\u002Fcontent\u002Fguides\u002Fapi-gateway-governance\u002Fintroduction","Amazon API Gateway governance in depth","Guide",{"link":140,"text":141,"type":20},"https:\u002F\u002Faws.amazon.com\u002Fblogs\u002Fcompute\u002Fenhancing-api-security-with-amazon-api-gateway-tls-security-policies\u002F","Enhancing API security with Amazon API Gateway TLS security policies",{"link":143,"text":144,"type":20},"https:\u002F\u002Faws.amazon.com\u002Fblogs\u002Fcompute\u002Faccessing-private-amazon-api-gateway-endpoints-through-custom-amazon-cloudfront-distribution-using-vpc-origins\u002F","Accessing private Amazon API Gateway endpoints through custom Amazon CloudFront distribution using VPC Origins",{"link":146,"text":147,"type":20},"https:\u002F\u002Faws.amazon.com\u002Fabout-aws\u002Fwhats-new\u002F2024\u002F04\u002Famazon-cognito-customers-access-apis-verified-permissions\u002F","Amazon Cognito customers can secure access to APIs using Amazon Verified Permissions",{"link":149,"text":150,"type":20},"https:\u002F\u002Faws.amazon.com\u002Fblogs\u002Fmt\u002Fconfiguring-machine-to-machine-authentication-with-amazon-cognito-and-amazon-api-gateway-part-1\u002F","Configuring machine to machine Authentication with Amazon Cognito and Amazon API Gateway – Part 1",{"link":152,"text":153,"type":20},"https:\u002F\u002Faws.amazon.com\u002Fblogs\u002Fmt\u002Fconfiguring-machine-to-machine-authentication-with-amazon-cognito-and-amazon-api-gateway-part-2\u002F","Configuring machine to machine Authentication with Amazon Cognito and Amazon API Gateway – Part 2",{"link":155,"text":156,"type":20},"https:\u002F\u002Faws.amazon.com\u002Fblogs\u002Fcompute\u002Fconsuming-private-amazon-api-gateway-apis-using-mutual-tls\u002F","Consuming private Amazon API Gateway APIs using mutual TLS",{"link":158,"text":159,"type":20},"https:\u002F\u002Faws.amazon.com\u002Fblogs\u002Farchitecture\u002Fhow-seatgeek-uses-aws-to-control-authorization-authentication-and-rate-limiting-in-a-multi-tenant-saas-application\u002F","How SeatGeek uses AWS Serverless to control authorization, authentication, and rate-limiting in a multi-tenant SaaS application",{"link":161,"text":162,"type":12},"https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=GvyyJQ5m7x0","Scaling and securing private workloads using Amazon API Gateway",{"link":164,"text":165,"type":12},"https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=H4hCygngTrU","API Gateway private integrations | Serverless Office Hours",{"link":112,"text":113,"type":114},{"link":116,"text":117,"type":114},"secure","secure.md","\u002Fcontent\u002Fservice\u002Fapi-gateway\u002Fpaved-path\u002Fbuilding-an-api-platform-on-aws\u002Fsecure",{"title":172,"collapsible":37,"isCollapsed":38,"content":173},"Deploy\u002FPublish",[174],{"title":172,"order":175,"resources":176,"time":53,"path":192,"id":193,"link":194},6,[177,180,183,186,188,191],{"link":178,"text":179,"type":20},"https:\u002F\u002Faws.amazon.com\u002Fblogs\u002Fcompute\u002Fzero-downtime-blue-green-deployments-with-amazon-api-gateway\u002F","Zero downtime blue\u002Fgreen deployments with Amazon API Gateway",{"link":181,"text":182,"type":20},"https:\u002F\u002Faws.amazon.com\u002Fblogs\u002Fcompute\u002Fperforming-canary-deployments-for-service-integrations-with-amazon-api-gateway\u002F","Performing canary deployments for service integrations with Amazon API Gateway",{"link":184,"text":185,"type":20},"https:\u002F\u002Faws.amazon.com\u002Fblogs\u002Fdevops\u002Fautomating-your-api-testing-with-aws-codebuild-aws-codepipeline-and-postman\u002F","Automating your API testing with AWS CodeBuild, AWS CodePipeline, and Postman",{"link":105,"text":187,"type":107},"Sample REST API implementations with CI\u002FCD pipelines",{"link":189,"text":190,"type":114},"https:\u002F\u002Fcatalog.workshops.aws\u002Fcomplete-aws-sam\u002Fen-US","The Complete AWS SAM Workshop",{"link":116,"text":117,"type":114},"deploy","deploy.md","\u002Fcontent\u002Fservice\u002Fapi-gateway\u002Fpaved-path\u002Fbuilding-an-api-platform-on-aws\u002Fdeploy",{"title":196,"collapsible":37,"isCollapsed":38,"content":197},"Scale",[198],{"title":196,"order":199,"resources":200,"time":53,"path":215,"id":216,"link":217},7,[201,204,208,211,214],{"link":202,"text":203,"type":20},"https:\u002F\u002Faws.amazon.com\u002Fblogs\u002Fcompute\u002Fbuilding-a-multi-region-serverless-application-with-amazon-api-gateway-and-aws-lambda\u002F","Building a Multi-region Serverless Application with Amazon API Gateway and AWS Lambda",{"link":205,"text":206,"type":207},"https:\u002F\u002Frepost.aws\u002Fquestions\u002FQUSs8ODCyJSRWR7mawaUIl4g\u002Fmulti-region-strategy-for-api-gateway","Multi Region strategy for API Gateway","re:Post",{"link":209,"text":210,"type":20},"https:\u002F\u002Faws.amazon.com\u002Fblogs\u002Fcompute\u002Fbuilding-resilient-private-apis-using-amazon-api-gateway\u002F","Building resilient private APIs using Amazon API Gateway",{"link":212,"text":213,"type":20},"https:\u002F\u002Faws.amazon.com\u002Fblogs\u002Fcompute\u002Farchitecting-for-scale-with-amazon-api-gateway-private-integrations\u002F","Architecting for scale with Amazon API Gateway private integrations",{"link":161,"text":162,"type":12},"scale","scale.md","\u002Fcontent\u002Fservice\u002Fapi-gateway\u002Fpaved-path\u002Fbuilding-an-api-platform-on-aws\u002Fscale",{"title":219,"collapsible":37,"isCollapsed":38,"content":220},"Monitor",[221],{"title":219,"order":222,"resources":223,"time":238,"path":239,"id":240,"link":241},8,[224,227,230,233,235],{"link":225,"text":226,"type":131},"https:\u002F\u002Fdocs.aws.amazon.com\u002Fapigateway\u002Flatest\u002Fdeveloperguide\u002Frest-api-monitor.html","Monitoring REST APIs",{"link":228,"text":229,"type":131},"https:\u002F\u002Fdocs.aws.amazon.com\u002Fapigateway\u002Flatest\u002Fdeveloperguide\u002Fhttp-api-monitor.html","Monitoring your HTTP API",{"link":231,"text":232,"type":131},"https:\u002F\u002Fdocs.aws.amazon.com\u002Fapigateway\u002Flatest\u002Fdeveloperguide\u002Fwebsocket-api-monitor.html","Monitoring WebSocket APIs",{"link":105,"text":234,"type":107},"Sample REST API implementations with business specific metrics, dashboards and alerts in IaC templates",{"link":236,"text":237,"type":114},"https:\u002F\u002Fcatalog.workshops.aws\u002Fserverless-observability","AWS Serverless Observability Workshop","5 min","monitor","monitor.md","\u002Fcontent\u002Fservice\u002Fapi-gateway\u002Fpaved-path\u002Fbuilding-an-api-platform-on-aws\u002Fmonitor",{"title":243,"collapsible":37,"isCollapsed":38,"content":244},"Insights",[245],{"title":243,"order":246,"resources":247,"time":76,"path":261,"id":262,"link":263},9,[248,251,254,257,260],{"link":249,"text":250,"type":20},"https:\u002F\u002Faws.amazon.com\u002Fblogs\u002Fcompute\u002Fvisualizing-amazon-api-gateway-usage-plans-using-amazon-quicksight\u002F","Visualizing Amazon API Gateway usage plans using Amazon QuickSight",{"link":252,"text":253,"type":20},"https:\u002F\u002Faws.amazon.com\u002Fblogs\u002Fbig-data\u002Flog-analytics-the-easy-way-with-amazon-opensearch-serverless\u002F","Log analytics the easy way with Amazon OpenSearch Serverless",{"link":255,"text":256,"type":20},"https:\u002F\u002Faws.amazon.com\u002Fblogs\u002Fawsmarketplace\u002Fhow-to-gain-api-observability-with-amazon-api-gateway-and-moesif-in-minutes\u002F","How to gain API observability with Amazon API Gateway and Moesif in minutes",{"link":258,"text":259,"type":107},"https:\u002F\u002Fgithub.com\u002Faws-samples\u002Fserverless-samples\u002Ftree\u002Fmain\u002Fapigw-log-analytic","Logging API Gateway access logs, analyzing and visualizing them using Amazon QuickSight",{"link":236,"text":237,"type":114},"insights","insights.md","\u002Fcontent\u002Fservice\u002Fapi-gateway\u002Fpaved-path\u002Fbuilding-an-api-platform-on-aws\u002Finsights",{"title":265,"collapsible":37,"isCollapsed":38,"content":266},"Monetize",[267],{"title":265,"order":268,"resources":269,"time":76,"path":274,"id":275,"link":276},10,[270,271],{"link":249,"text":250,"type":20},{"link":272,"text":273,"type":20},"https:\u002F\u002Faws.amazon.com\u002Fblogs\u002Fcompute\u002Fmonetize-your-apis-in-aws-marketplace-using-api-gateway\u002F","Monetize your APIs in AWS Marketplace using API Gateway","monetize","monetize.md","\u002Fcontent\u002Fservice\u002Fapi-gateway\u002Fpaved-path\u002Fbuilding-an-api-platform-on-aws\u002Fmonetize",{"title":278,"collapsible":37,"isCollapsed":38,"content":279},"Discover",[280],{"title":278,"order":281,"resources":282,"time":76,"path":295,"id":296,"link":297},11,[283,286,289,292],{"link":284,"text":285,"type":131},"https:\u002F\u002Fdocs.aws.amazon.com\u002Fapigateway\u002Flatest\u002Fdeveloperguide\u002Fportals.html","API Gateway developer portals",{"link":287,"text":288,"type":20},"https:\u002F\u002Faws.amazon.com\u002Fblogs\u002Fcompute\u002Fimprove-api-discoverability-with-the-new-amazon-api-gateway-portal\u002F","Improve API discoverability with the new Amazon API Gateway Portal",{"link":290,"text":291,"type":20},"https:\u002F\u002Faws.amazon.com\u002Fblogs\u002Fapn\u002Fintegrating-readme-with-amazon-api-gateway-to-keep-your-developer-hub-up-to-date\u002F","Integrating ReadMe with Amazon API Gateway to Keep Your Developer Hub Up to Date",{"link":293,"text":294,"type":20},"https:\u002F\u002Faws.amazon.com\u002Fblogs\u002Fapn\u002Fhow-to-streamline-api-development-on-amazon-api-gateway-using-smartbear-swaggerhub\u002F","How to Streamline API Development on Amazon API Gateway Using SmartBear’s API Hub","discover","discover.md","\u002Fcontent\u002Fservice\u002Fapi-gateway\u002Fpaved-path\u002Fbuilding-an-api-platform-on-aws\u002Fdiscover","LESSON",[300,301],"content\u002Fcontributors\u002Farthi-jaganathan.json","content\u002Fcontributors\u002Fgiedrius-praspaliauskas.json","Building an API platform on AWS",1792665265461]