{"componentChunkName":"component---src-templates-blog-detail-tsx","path":"/blog/2018-01-16-cors-api-gateway-survival-guide","result":{"data":{"currentBlog":{"id":"5928eee6-9546-5603-ad61-a9688dbafd02","frontmatter":{"thumbnail":"https://img.serverlesscloud.cn/20191231/1577795409089-CORS_principle.png","authors":["AlexDeBrie"],"categories":["guides-and-tutorials","operations-and-observability"],"date":"2018-01-16T00:00:00.000Z","title":"生存指南之 CORS + API Gateway","description":"本文介绍了跨域资源共享的基本知识，以及如何避免云函数上 Serverless web API 的问题","authorslink":["https://serverless.com/author/alexdebrie/"],"translators":["Aceyclee"],"translatorslink":["https://www.zhihu.com/people/Aceyclee"],"tags":["CORS","API 网关"],"keywords":"CORS,API Gateway,Serverless web API","outdated":null},"wordCount":{"words":237,"sentences":40,"paragraphs":40},"fileAbsolutePath":"/opt/build/repo/content/blog/2018-01-16-cors-api-gateway-survival-guide.md","fields":{"slug":"/blog/2018-01-16-cors-api-gateway-survival-guide/","keywords":["go","java","serverless","云函数","Access","Allow","Control","headers","product","response","event","Origin"]},"html":"

构建 Web API 是 Serverless 应用中最流行的用例之一，您能在不增加其他操作开销的情况下，获得简单、可扩展的后端优势。

\n

然而，如果您的网页正在调用后端 API，那么必须处理 跨域资源共享 (CORS) 的问题 ，如果您的网页向与您当前所在域的不同域发出 HTTP 请求，则它必须是 CORS 友好的。

\n

如果您发现以下错误：

\n
\n

No 'Access-Control-Allow-Origin' header is present on the requested resource

\n
\n

那么本文可能对您有所帮助。

\n

接下来，我们将介绍 Serverless + CORS 的相关信息，目录如下：

\n\n

TL;DR

\n

快速开始 🔜 如果您想快速解决 Serverless 应用中的 CORS，可以执行以下操作：

\n
    \n
  1. 要处理 preflight requests，在每个 HTTP 端点中添加 enableCORS: true 和 integratedResponse: true 标记：
    2. \n
\n\n \n 复制代码\n \n \n
# serverless.yml\nservice: products-service\n\nprovider:\n  name: tencent\n  region: ap-guangzhou\n  runtime: Nodejs8.9 # Nodejs8.9 or Nodejs6.10\n\nplugins:\n  - serverless-tencent-scf\n\nfunctions:\n  getProduct:\n    handler: handler.getProduct\n    events:\n      - apigw:\n          name: api\n          parameters:\n            path: /product\n            stageName: release\n            # 修改成你的 API 服务 ID\n            serviceId: service-xxx\n            httpMethod: GET\n            # 开启集成相应，这里必须开启，才能自定义响应 headers\n            integratedResponse: true,\n            # 开启 CORS\n            enableCORS: true\n  createProduct:\n    handler: handler.createProduct\n    events:\n      - apigw:\n          name: api\n          parameters:\n            path: /product\n            stageName: release\n            # 修改成你的 API 服务 ID\n            serviceId: service-xxx\n            httpMethod: POST\n            # 开启集成相应，这里必须开启，才能自定义响应 headers\n            integratedResponse: true,\n            # 开启 CORS\n            enableCORS: false
\n
    \n
  1. 要处理 CORS headers，请在响应中返回 CORS headers。主要标头是 Access-Control-Allow-Origin 和 Access-Control-Allow-Credentials。示例如下：
    2. \n
\n {\n const product = retrieveProduct(event);\n\n const response = {\n statusCode: 200,\n headers: {\n 'Access-Control-Allow-Origin': '*',\n 'Access-Control-Allow-Credentials': true,\n },\n body: JSON.stringify({\n product: product,\n }),\n };\n\n callback(null, response);\n};\n\nmodule.exports.createProduct = (event, context, callback) => {\n // Do work to create Product\n const product = createProduct(event);\n\n const response = {\n statusCode: 200,\n headers: {\n 'Access-Control-Allow-Origin': '*',\n 'Access-Control-Allow-Credentials': true,\n },\n body: JSON.stringify({\n product: product,\n }),\n };\n\n callback(null, response);\n};`, `42322916826022120000`)\"\n >\n \n 复制代码\n \n \n
'use strict';\n\n// mock function\nfunction retrieveProduct(event) {\n  return {\n    id: 1,\n    name: 'good1',\n    price: 10,\n  };\n}\n\n// mock function\nfunction createProduct(event) {\n  const { queryString } = event;\n  return {\n    id: Number(queryString.id),\n    name: 'good1',\n    price: 10,\n  };\n}\n\nmodule.exports.getProduct = (event, context, callback) => {\n  const product = retrieveProduct(event);\n\n  const response = {\n    statusCode: 200,\n    headers: {\n      'Access-Control-Allow-Origin': '*',\n      'Access-Control-Allow-Credentials': true,\n    },\n    body: JSON.stringify({\n      product: product,\n    }),\n  };\n\n  callback(null, response);\n};\n\nmodule.exports.createProduct = (event, context, callback) => {\n  // Do work to create Product\n  const product = createProduct(event);\n\n  const response = {\n    statusCode: 200,\n    headers: {\n      'Access-Control-Allow-Origin': '*',\n      'Access-Control-Allow-Credentials': true,\n    },\n    body: JSON.stringify({\n      product: product,\n    }),\n  };\n\n  callback(null, response);\n};
\n

CORS preflight requests

\n

如果您不是在进行「simple request」，那么浏览器会用 OPTIONS 方法，发送 preflight\nrequest 到资源里，您请求的资源将使用 安全发送到资源 的方法返回，并且可以选择返回有效发送的标头。

\n

我们拆开来看看：

\n

浏览器什么时候发送 preflight requests?

\n

您的浏览器会对几乎所有的跨域请求发送一个 preflight requests。（例外是「simple requests」，但这只是请求的一小部分）。大体上看，一个简单请求只是一个 GET request 或者 POST request，如果您不在此范围内，则需要进行预检。

\n

对 preflight requests 的响应是什么？

\n

对一个 preflight requests 的 响应包括其允许访问的资源，它允许在该资源的方法，如 GET, POST,\nPUT 等。还可以包括被允许在该资源标头，如 Authentication。

\n

如何处理 Serverless 中的 preflight requests?

\n

要设置 preflight requests，您只需要在 API Gateway 的端点上配置一个 OPTIONS 。幸运的是，你可以非常简单地使用 Serverless Framework 来完成。

\n

只需要在 serverless.yml 添加设置 enableCORS: true：

\n\n \n 复制代码\n \n \n
# serverless.yml\n\nservice: products-service\n\nprovider:\n  name: tencent\n  region: ap-guangzhou\n  runtime: Nodejs8.9 # Nodejs8.9 or Nodejs6.10\n\nplugins:\n  - serverless-tencent-scf\n\nfunctions:\n  getProduct:\n    handler: handler.getProduct\n    events:\n      - apigw:\n          name: api\n          parameters:\n            path: /product\n            stageName: release\n            serviceId: service-lanyfiga\n            httpMethod: GET\n            # 开启集成相应，这里必须开启，才能自定义响应 headers\n            integratedResponse: true,\n            # 开启 CORS\n            enableCORS: true\n  createProduct:\n    handler: handler.createProduct\n    events:\n      - apigw:\n          name: api\n          parameters:\n            path: /product\n            stageName: release\n            serviceId: service-lanyfiga\n            httpMethod: POST\n            # 开启集成相应，这里必须开启，才能自定义响应 headers\n            integratedResponse: true,\n            # 开启 CORS\n            enableCORS: false
\n

CORS Response Headers

\n

尽管 preflight request 仅适用于某些跨域请求，但每个跨域请求中都必须存在 CORS Response Headers，这意味着您必须将 Access-Control-Allow-Origin 添加进 handlers 的响应中。

\n

如果您使用 cookies，还需要添加 Access-Control-Allow-Credentials。

\n

要与上面的 serverless.yml 匹配，handler.js 文件应该如下设置：

\n {\n // Do work to retrieve Product\n const product = retrieveProduct(event);\n\n const response = {\n statusCode: 200,\n headers: {\n 'Access-Control-Allow-Origin': '*',\n 'Access-Control-Allow-Credentials': true,\n },\n body: JSON.stringify({\n product: product,\n }),\n };\n\n callback(null, response);\n};\n\nmodule.exports.createProduct = (event, context, callback) => {\n // Do work to create Product\n const product = createProduct(event);\n\n const response = {\n statusCode: 200,\n headers: {\n 'Access-Control-Allow-Origin': '*',\n 'Access-Control-Allow-Credentials': true,\n },\n body: JSON.stringify({\n product: product,\n }),\n };\n\n callback(null, response);\n};`, `44144032294620406000`)\"\n >\n \n 复制代码\n \n \n
// handler.js\n\n'use strict';\n\nmodule.exports.getProduct = (event, context, callback) => {\n  // Do work to retrieve Product\n  const product = retrieveProduct(event);\n\n  const response = {\n    statusCode: 200,\n    headers: {\n      'Access-Control-Allow-Origin': '*',\n      'Access-Control-Allow-Credentials': true,\n    },\n    body: JSON.stringify({\n      product: product,\n    }),\n  };\n\n  callback(null, response);\n};\n\nmodule.exports.createProduct = (event, context, callback) => {\n  // Do work to create Product\n  const product = createProduct(event);\n\n  const response = {\n    statusCode: 200,\n    headers: {\n      'Access-Control-Allow-Origin': '*',\n      'Access-Control-Allow-Credentials': true,\n    },\n    body: JSON.stringify({\n      product: product,\n    }),\n  };\n\n  callback(null, response);\n};
\n

这里需要注意 response 的 headers 属性，其中包含 Access-Control-Allow-Origin 和 Access-Control-Allow-Credentials。

\n

下面是一个简单的示例：

\n {\n const response = {\n statusCode: 200,\n body: 'Hello, world!',\n };\n\n return callback(null, response);\n};\n\n// Let's "middyfy" our handler, then we will be able to attach middlewares to it\nconst handler = middy(hello).use(cors()); // Adds CORS headers to responses\n\nmodule.exports = { handler };`, `52301056621546070000`)\"\n >\n \n 复制代码\n \n \n
// hello.js\n\nconst middy = require('middy');\nconst { cors } = require('middy/middlewares');\n\n// This is your common handler, no way different than what you are used to do every day\nconst hello = (event, context, callback) => {\n  const response = {\n    statusCode: 200,\n    body: 'Hello, world!',\n  };\n\n  return callback(null, response);\n};\n\n// Let's \"middyfy\" our handler, then we will be able to attach middlewares to it\nconst handler = middy(hello).use(cors()); // Adds CORS headers to responses\n\nmodule.exports = { handler };
\n\n

在上面的示例中，我们给定了 \"*\" 作为 Access-Control-Allow-Origin 的值。但是，如果您使用 request using credentials 则不被允许。为了使浏览器能够响应，Access-Control-Allow-Origin 需要包含发出请求的特定来源。有两种方法可以解决。

\n

首先，如果只有一个发出请求的原始网站，则可以将其硬编码到云函数的响应中：

\n {\n // Do work to retrieve Product\n const product = retrieveProduct(event);\n\n const response = {\n statusCode: 200,\n headers: {\n 'Access-Control-Allow-Origin': 'https://myorigin.com', // <-- Add your specific origin here\n 'Access-Control-Allow-Credentials': true,\n },\n body: JSON.stringify({\n product: product,\n }),\n };\n\n callback(null, response);\n};`, `37969072983685220000`)\"\n >\n \n 复制代码\n \n \n
// handler.js\n\n'use strict';\n\nmodule.exports.getProduct = (event, context, callback) => {\n  // Do work to retrieve Product\n  const product = retrieveProduct(event);\n\n  const response = {\n    statusCode: 200,\n    headers: {\n      'Access-Control-Allow-Origin': 'https://myorigin.com', // <-- Add your specific origin here\n      'Access-Control-Allow-Credentials': true,\n    },\n    body: JSON.stringify({\n      product: product,\n    }),\n  };\n\n  callback(null, response);\n};
\n

如果有多个原始网站使用您的 API，那么需要采用一种更加动态的方法。你可以检查 origin header 看看是否在被批准的来源列表中，如果是，则在 Access-Control-Allow-Origin 返回原点值。

\n {\n\n const origin = event.headers.origin;\n let headers;\n\n if (ALLOWED_ORIGINS.includes(origin) {\n headers = {\n 'Access-Control-Allow-Origin': origin,\n 'Access-Control-Allow-Credentials': true,\n },\n } else {\n headers = {\n 'Access-Control-Allow-Origin': '*',\n },\n }\n\n // Do work to retrieve Product\n const product = retrieveProduct(event);\n\n const response = {\n isBase64Encoded: false,\n statusCode: 200,\n headers\n body: JSON.stringify({\n product: product\n }),\n };\n\n callback(null, response);\n};`, `9954468033366438000`)\"\n >\n \n 复制代码\n \n \n
// handler.js\n\n'use strict';\n\nconst ALLOWED_ORIGINS = [\n\t'https://myfirstorigin.com',\n\t'https://mysecondorigin.com'\n];\n\nmodule.exports.getProduct = (event, context, callback) => {\n\n  const origin = event.headers.origin;\n  let headers;\n\n  if (ALLOWED_ORIGINS.includes(origin) {\n    headers = {\n      'Access-Control-Allow-Origin': origin,\n      'Access-Control-Allow-Credentials': true,\n    },\n  } else {\n    headers = {\n      'Access-Control-Allow-Origin': '*',\n    },\n  }\n\n  // Do work to retrieve Product\n  const product = retrieveProduct(event);\n\n  const response = {\n    isBase64Encoded: false,\n    statusCode: 200,\n    headers\n    body: JSON.stringify({\n      product: product\n    }),\n  };\n\n  callback(null, response);\n};
\n

在这个示例中，我们检查 origin header 是否匹配。如果匹配，我们会在 Access-Control-Allow-Origin 包含特定来源，并声明 Access-Control-Allow-Credentials 允许的来源。如果 origin 不是我们允许的来源之一，则我们将包含标准 headers，如果来源尝试进行凭据请求，则将被拒绝。

\n

小结

\n

处理 CORS 确实是一件麻烦的事情，但是使用 Serverless Framework 会让处理步骤变得简单得多！而这也就意味着再也不会出现 No 'Access-Control-Allow-Origin' header is present on the requested resource 这样的错误啦！👋

\n
\n

参考：

\n\n
\n

欢迎访问：Serverless 中文技术社区，您可以在 最佳实践 里体验更多关于 Serverless 应用的开发！

","tableOfContents":""},"previousBlog":{"id":"5a5e479a-32eb-589a-bc25-3a1a3b6e0126","frontmatter":{"thumbnail":"https://s3-us-west-2.amazonaws.com/assets.blog.serverless.com/inclusion/serverless-tech-inclusion1.jpg","authors":["CharmmieHendon"],"categories":["engineering-culture"],"date":"2018-01-24T00:00:00.000Z","title":"融入所处环境：科技领域的包容性和多元化","description":"我是 Charmmie Hendon，非常热衷于促进科技领域的包容性和多元化。以下是我的一些个人经历以及您如何带来改变。","authorslink":null,"translators":null,"translatorslink":null,"tags":null,"keywords":null,"outdated":null},"wordCount":{"words":222,"sentences":37,"paragraphs":36},"fileAbsolutePath":"/opt/build/repo/content/blog/2018-07-16-get-in-where-you-fit-in-inclusion-diversity-tech.md","fields":{"slug":"/blog/2018-07-16-get-in-where-you-fit-in-inclusion-diversity-tech/","keywords":["Javascript","serverless","行业","Serverless","serverless","偏见","多元化","inclusion"]}},"nextBlog":{"id":"4300b21c-7209-5256-86ff-0d38e3daec9b","frontmatter":{"thumbnail":"https://main.qcloudimg.com/raw/14f1c8eed372e76c1b139703b2f6d0fa.jpg","authors":["KieranMcCarthy"],"categories":["user-stories","engineering-culture"],"date":"2018-01-09T00:00:00.000Z","title":"我是如何在四年时间里，从厨师转行为 Serverless 应用开发者","description":"我是厨师出身，现在成为了一名 Serverless 应用开发者。","authorslink":["https://serverless.com/author/kieranmccarthy/"],"translators":["Aceyclee"],"translatorslink":["https://www.zhihu.com/people/Aceyclee"],"tags":["应用开发","Serverless"],"keywords":"Serverless 应用开发,Serverless 管理,厨师转行为 Serverless 应用开发者","outdated":null},"wordCount":{"words":285,"sentences":38,"paragraphs":36},"fileAbsolutePath":"/opt/build/repo/content/blog/2018-01-09-from-chef-to-serverless-developer-in-4-years.md","fields":{"slug":"/blog/2018-01-09-from-chef-to-serverless-developer-in-4-years/","keywords":["无服务器","无服务器开发","云函数","学习","Serverless","构建","Framework","开发者","服务器","应用","学位","简历"]}},"recommendBlogs":{"edges":[{"node":{"id":"665f9ce2-4451-59fd-bf98-1861789d3b3b","frontmatter":{"thumbnail":"https://s3-us-west-2.amazonaws.com/assets.blog.serverless.com/Serverless_logo.png","authors":["AndreaPasswater"],"categories":["guides-and-tutorials","engineering-culture"],"date":"2018-03-19T00:00:00.000Z","title":"如何为无服务器开放源代码项目做贡献","description":"想要为无服务器开放源代码项目做贡献？您可以遵循下面的指南。","authorslink":null,"translators":null,"translatorslink":null,"tags":null,"keywords":null,"outdated":null},"wordCount":{"words":96,"sentences":36,"paragraphs":36},"fileAbsolutePath":"/opt/build/repo/content/blog/2018-03-19-how-contribute-to-serverless-open-source.md","fields":{"slug":"/blog/2018-03-19-how-contribute-to-serverless-open-source/","keywords":["serverless","无服务器","serverless","github","插件","服务器","贡献","示例","blog","contribute"]}}},{"node":{"id":"a3e92579-65c3-5159-937c-32d18c5df7d7","frontmatter":{"thumbnail":"https://s3-us-west-2.amazonaws.com/assets.blog.serverless.com/why-not/why-not-header.png","authors":["AndreaPasswater"],"categories":["guides-and-tutorials","operations-and-observability","engineering-culture"],"date":"2018-03-21T00:00:00.000Z","title":"不适合选择无服务器的情境及原因","description":"无服务器既有优点也有缺点。那么，哪些情境下不适合选择无服务器？原因又是什么呢？","authorslink":null,"translators":null,"translatorslink":null,"tags":null,"keywords":null,"outdated":null},"wordCount":{"words":163,"sentences":43,"paragraphs":43},"fileAbsolutePath":"/opt/build/repo/content/blog/2018-03-21-when-why-not-use-serverless.md","fields":{"slug":"/blog/2018-03-21-when-why-not-use-serverless/","keywords":["faas","react","serverless","spa","无服务器","无服务器函数","无服务器架构","无服务器开发","服务器","twitter","serverless","blockquote","lang","script","en"]}}},{"node":{"id":"6a16520b-7886-582e-9182-64e50712d486","frontmatter":{"thumbnail":"https://s3-us-west-2.amazonaws.com/assets.blog.serverless.com/vendor+choice/serverless-data-portability.jpg","authors":["NickGottlieb"],"categories":["engineering-culture","guides-and-tutorials"],"date":"2018-06-20T00:00:00.000Z","title":"浅谈无服务器、数据锁定和供应商选择","description":"供应商选择是如今 IT 领导者需要考虑的最重要事项，而这一点可利用数据可移植性来实现。","authorslink":null,"translators":null,"translatorslink":null,"tags":null,"keywords":null,"outdated":null},"wordCount":{"words":205,"sentences":33,"paragraphs":33},"fileAbsolutePath":"/opt/build/repo/content/blog/2018-06-20-data-lockin-vendor-choice-portability.md","fields":{"slug":"/blog/2018-06-20-data-lockin-vendor-choice-portability/","keywords":["go","serverless","无服务器","无服务器架构","供应商","serverless","开发人员","数据","锁定","选择","服务"]}}},{"node":{"id":"94741abb-10ba-5db1-9756-cd1d573473fa","frontmatter":{"thumbnail":"https://s3-us-west-2.amazonaws.com/assets.blog.serverless.com/webstorm-ide/streamline-webstorm-serverless2.jpg","authors":["EslamHefnawy"],"categories":["guides-and-tutorials","engineering-culture"],"date":"2018-08-15T00:00:00.000Z","title":"如何使用 WebStorm 简化无服务器工作流程","description":"在本文中，我将和您分享如何使用 WebStorm 进行无服务器特定的 IDE 设置以及如何利用它来极大地加快无服务器工作流程。","authorslink":null,"translators":null,"translatorslink":null,"tags":null,"keywords":null,"outdated":null},"wordCount":{"words":234,"sentences":54,"paragraphs":54},"fileAbsolutePath":"/opt/build/repo/content/blog/2018-08-15-streamline-serverless-workflow-webstorm.md","fields":{"slug":"/blog/2018-08-15-streamline-serverless-workflow-webstorm/","keywords":["nodejs","serverless","无服务器","无服务器开发","serverless","WebStorm","webstorm","服务器","blog","assets"]}}},{"node":{"id":"713a0563-4bf9-5721-bacb-3b4ef609fe4a","frontmatter":{"thumbnail":"https://s3-us-west-2.amazonaws.com/assets.blog.serverless.com/camp-fire/camp-fire-housing-thumb.jpg","authors":["EricWyne"],"categories":["guides-and-tutorials","user-stories"],"date":"2018-12-05T00:00:00.000Z","title":"Serverless Twitter 机器人帮助为坎普山火受灾者安置住房","description":"加利福尼亚州的坎普山火致使数千人流离失所，为此，我构建了一个简单的 Serverless Twitter 机器人来帮助将受灾者安置在临时住房！","authorslink":["https://serverless.com/author/ericwyne/"],"translators":["Aceyclee"],"translatorslink":["zhihu.com/people/Aceyclee"],"tags":null,"keywords":null,"outdated":null},"wordCount":{"words":157,"sentences":26,"paragraphs":26},"fileAbsolutePath":"/opt/build/repo/content/blog/2018-12-05-serverless-twitter-camp-fire.md","fields":{"slug":"/blog/2018-12-05-serverless-twitter-camp-fire/","keywords":["serverless","无服务器","云函数","Serverless","org","住房","Twitter","函数","受灾","机器人","山火"]}}},{"node":{"id":"17c972d9-0583-51f6-9d5d-c2ba5f21b6a3","frontmatter":{"thumbnail":"https://img.serverlesscloud.cn/20191227/1577409288454-v2-577c2b21d600e3ea07f156f3e9d2d6b8_1200x500.jpg","authors":["Alfred Huang"],"categories":["guides-and-tutorials"],"date":"2019-08-21T00:00:00.000Z","title":"Serverless 的运行原理与组件架构","description":"本文重点探讨下开发者使用 Serverless 时经常遇到的一些问题，以及如何解决","authorslink":["https://zhuanlan.zhihu.com/ServerlessGo"],"translators":null,"translatorslink":null,"tags":["运行原理","serverless"],"keywords":"Serverless 运行原理,Serverless 组件架构","outdated":null},"wordCount":{"words":236,"sentences":33,"paragraphs":33},"fileAbsolutePath":"/opt/build/repo/content/blog/2019-08-21-serverless-operation-architecture.md","fields":{"slug":"/blog/2019-08-21-serverless-operation-architecture/","keywords":["koa","serverless","云函数","Serverless","用户","函数","请求","实例","形态","业务","serverlesscloud"]}}},{"node":{"id":"ae4fd2f8-515c-5aec-b584-38427ef33f7e","frontmatter":{"thumbnail":"https://img.serverlesscloud.cn/2020114/1578989800047-part-00492-780.jpg","authors":["Anycodes"],"categories":["guides-and-tutorials","user-stories"],"date":"2019-09-16T00:00:00.000Z","title":"突破传统 OJ 瓶颈，「判题姬」接入云函数","description":"通过 Serverless 实现在线编程","authorslink":["https://www.zhihu.com/people/liuyu-43-97"],"translators":null,"translatorslink":null,"tags":["在线编程","云函数"],"keywords":"Serverless 在线编程,Serverless OJ","outdated":null},"wordCount":{"words":169,"sentences":30,"paragraphs":30},"fileAbsolutePath":"/opt/build/repo/content/blog/2019-09-16-online-Judge.md","fields":{"slug":"/blog/2019-09-16-online-Judge/","keywords":["python","serverless","云函数","代码","函数","serverless"]}}},{"node":{"id":"545ab3d2-e14e-5cc2-8548-0e863eac942b","frontmatter":{"thumbnail":"https://s3-us-west-2.amazonaws.com/assets.blog.serverless.com/2019-10-deployment-best-practices/safeguard-header.png","authors":["FernandoMedinaCorey"],"categories":["guides-and-tutorials"],"date":"2019-10-14T00:00:00.000Z","title":"无服务器部署最佳实践","description":"了解部署无服务器应用时的一些最佳实践。","authorslink":null,"translators":null,"translatorslink":null,"tags":null,"keywords":null,"outdated":null},"wordCount":{"words":221,"sentences":46,"paragraphs":46},"fileAbsolutePath":"/opt/build/repo/content/blog/2019-10-14-serverless-deployment-best-practices.md","fields":{"slug":"/blog/2019-10-14-serverless-deployment-best-practices/","keywords":["serverless","无服务器","serverless","部署","服务器","开发人员","应用","安全措施","使用","函数"]}}}],"totalCount":31}},"pageContext":{"isCreatedByStatefulCreatePages":false,"blogId":"5928eee6-9546-5603-ad61-a9688dbafd02","previousBlogId":"5a5e479a-32eb-589a-bc25-3a1a3b6e0126","nextBlogId":"4300b21c-7209-5256-86ff-0d38e3daec9b","categories":["guides-and-tutorials","operations-and-observability"]}}}