blocks|key|177521|text|有两种方法可以做到这一点。不幸的是，有些适用于某些类型的EB应用程序，有些适用于其他类型的应用程序。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|177522|在AWS文档中支持/推荐|177523|对于一些应用程序类型，比如Java+SE、Go、Node.js，也许还有Ruby+(+Ruby没有文档记录，但是所有其他的Nginx平台似乎都支持它)，Elasticbeanstalk对如何配置Nginx有内置的理解。|offset|length|177524|177525|要扩展Elastic+Beanstalk的默认.ebextensions/nginx/conf.d/配置，请将配置文件添加到应用程序源包中名为+nginx+的文件夹中。Elastic+Beanstalk的nginx配置会自动包含此文件夹中的.conf文件。~/workspace/my-app/|blockquote|style|BOLD|CODE|177526|177527|177528|%7C--+.ebextensions
%7C+++`--+nginx
%7C+++++++`--+conf.d
%7C+++++++++++`--+myconf.conf
`--+web.jar|code-block|syntax|javascript|177529|177530|+Configuring+the+Reverse+Proxy+-+Java+SE|177531|177532|177533|要明确增加最大上传大小，请在.ebextensions/nginx/conf.d/proxy.conf中创建一个文件，将最大正文大小设置为您喜欢的任何大小：|177534|client_max_body_size+50M;|177535|直接创建Nginx配置文件|177536|对于其他一些应用程序类型，在经过大量研究和与出色的亚马逊网络服务支持团队合作数小时后，我在.ebextensions中创建了一个配置文件来补充nginx配置。此更改允许更大的帖子正文大小。|177537|在.ebextensions目录中，我创建了一个名为01_files.config的文件，其中包含以下内容：|177538|files:
++++"/etc/nginx/conf.d/proxy.conf"+:
++++++++mode:+"000755"
++++++++owner:+root
++++++++group:+root
++++++++content:+%7C
+++++++++++client_max_body_size+20M;|177539|这将在/etc/nginx/conf.d目录中生成一个proxy.conf文件。proxy.conf文件只包含一个完成此任务的线性client_max_body_size+20M;。|177540|请注意，对于某些平台，此文件将在部署过程中创建，但会在稍后的部署阶段中删除。|177541|您可以指定Nginx文档中概述的其他指令。|177542|http://wiki.nginx.org/Configuration|177543|希望这对其他人有帮助！|177544|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/java-se-nginx.html|1|https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/go-nginx.html|2|https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/nodejs-platform-proxy.html|3|4^0|0|0|D|7|0|L|2|1|O|7|2|0|0|N|R|1J|D|26|1X|N|R|0|0|0|0|0|1|13|1|13|3|0|0|0|0|26|E|11|0|0|0|D|0|0|2M|19|D|0|0|1I|1|D|Q|F|0|0|0|2J|1T|P|0|0|12|0|0|L|0|0|Z|0|Z|4|0|0|B|0^^$0|@$1|2|3|4|5|6|7|20|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|21|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|22|8|@]|9|@$F|23|G|24|1|25]|$F|26|G|27|1|28]|$F|29|G|2A|1|2B]]|A|$]]|$1|H|3|-4|5|6|7|2C|8|@]|9|@]|A|$]]|$1|I|3|J|5|K|7|2D|8|@$F|2E|G|2F|L|M]|$F|2G|G|2H|L|M]|$F|2I|G|2J|L|M]|$F|2K|G|2L|L|N]]|9|@]|A|$]]|$1|O|3|-4|5|6|7|2M|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|2N|8|@]|9|@]|A|$]]|$1|Q|3|R|5|S|7|2O|8|@]|9|@]|A|$T|U]]|$1|V|3|-4|5|6|7|2P|8|@]|9|@]|A|$]]|$1|W|3|X|5|K|7|2Q|8|@$F|2R|G|2S|L|M]]|9|@$F|2T|G|2U|1|2V]]|A|$]]|$1|Y|3|-4|5|6|7|2W|8|@]|9|@]|A|$]]|$1|Z|3|-4|5|6|7|2X|8|@]|9|@]|A|$]]|$1|10|3|11|5|6|7|2Y|8|@$F|2Z|G|30|L|M]|$F|31|G|32|L|N]]|9|@]|A|$]]|$1|12|3|13|5|S|7|33|8|@]|9|@]|A|$T|U]]|$1|14|3|15|5|6|7|34|8|@$F|35|G|36|L|M]]|9|@]|A|$]]|$1|16|3|17|5|6|7|37|8|@$F|38|G|39|L|M]|$F|3A|G|3B|L|N]]|9|@]|A|$]]|$1|18|3|19|5|6|7|3C|8|@$F|3D|G|3E|L|M]|$F|3F|G|3G|L|N]|$F|3H|G|3I|L|N]]|9|@]|A|$]]|$1|1A|3|1B|5|S|7|3J|8|@]|9|@]|A|$T|U]]|$1|1C|3|1D|5|6|7|3K|8|@$F|3L|G|3M|L|M]|$F|3N|G|3O|L|N]]|9|@]|A|$]]|$1|1E|3|1F|5|6|7|3P|8|@$F|3Q|G|3R|L|M]]|9|@]|A|$]]|$1|1G|3|1H|5|6|7|3S|8|@$F|3T|G|3U|L|M]]|9|@]|A|$]]|$1|1I|3|1J|5|6|7|3V|8|@$F|3W|G|3X|L|M]]|9|@$F|3Y|G|3Z|1|40]]|A|$]]|$1|1K|3|1L|5|6|7|41|8|@$F|42|G|43|L|M]]|9|@]|A|$]]|$1|1M|3|-4|5|6|7|44|8|@]|9|@]|A|$]]]|1N|$1O|$5|1P|1Q|1R|A|$1S|1T]]|1U|$5|1P|1Q|1R|A|$1S|1V]]|1W|$5|1P|1Q|1R|A|$1S|1X]]|1Y|$5|1P|1Q|1R|A|$1S|1T]]|1Z|$5|1P|1Q|1R|A|$1S|1J]]]]

There are two methods you can take for this. Unfortunately some work for some EB application types and some work for others.
<h2>Supported/recommended in AWS documentation</h2>
For some application types, like <a href="https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/java-se-nginx.html" rel="noreferrer">Java SE</a>, <a href="https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/go-nginx.html" rel="noreferrer">Go</a>, <a href="https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/nodejs-platform-proxy.html" rel="noreferrer">Node.js</a>, and maybe Ruby (it's not documented for Ruby, but all the other Nginx platforms seem to support this), Elasticbeanstalk has a built-in understanding of how to configure Nginx.
<blockquote>
To extend Elastic Beanstalk's default nginx configuration, add .conf configuration files to a folder named <code>.ebextensions/nginx/conf.d/</code> in your application source bundle. Elastic Beanstalk's nginx configuration includes .conf files in this folder automatically.
</blockquote>
<blockquote>
<pre><code>~/workspace/my-app/
</code></pre>
</blockquote>
<pre><code>|-- .ebextensions
| `-- nginx
| `-- conf.d
| `-- myconf.conf
`-- web.jar
</code></pre>
<blockquote>
<a href="https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/java-se-nginx.html" rel="noreferrer">Configuring the Reverse Proxy - Java SE</a>
</blockquote>
To increase the maximum upload size specifically, then create a file at <code>.ebextensions/nginx/conf.d/proxy.conf</code> setting the max body size to whatever size you would prefer:
<pre><code>client_max_body_size 50M;
</code></pre>
<h2>Create the Nginx config file directly</h2>
For some other application types, after much research and hours of working with the wonderful AWS support team, I created a config file inside of <code>.ebextensions</code> to supplement the nginx config. This change allowed for a larger post body size.
Inside of the <code>.ebextensions</code> directory, I created a file called <code>01_files.config</code> with the following contents:
<pre><code>files:
 &quot;/etc/nginx/conf.d/proxy.conf&quot; :
 mode: &quot;000755&quot;
 owner: root
 group: root
 content: |
 client_max_body_size 20M;
</code></pre>
This generates a proxy.conf file inside of the /etc/nginx/conf.d directory. The proxy.conf file simply contains the one liner <code>client_max_body_size 20M;</code> which does the trick.
Note that for some platforms, this file will be created during the deploy, but then removed in a later deployment phase.
You can specify other directives which are outlined in Nginx documentation.
<a href="http://wiki.nginx.org/Configuration" rel="noreferrer">http://wiki.nginx.org/Configuration</a>
Hope this helps others!

blocks|key|2781524|text|files:
++++"/etc/nginx/conf.d/proxy.conf"+:
++++++++mode:+"000755"
++++++++owner:+root
++++++++group:+root
++++++++content:+%7C
+++++++++++client_max_body_size+20M;|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|2781525|为了安全起见，修改了上面的答案(语法错误，请看YAML中的两个'owner:‘条目)，伙计们，请不要在任何东西上设置777权限。除非你喜欢被黑客入侵，并将Nginx配置文件的所有者设置为root。|unstyled|2781526|另请参阅below+answer，以使nginx在部署后获取此更改。|offset|length|2781527|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/28313384/184184^0|0|0|4|C|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|T|8|@]|9|@]|A|$]]|$1|G|3|H|5|F|7|U|8|@]|9|@$I|V|J|W|1|X]]|A|$]]|$1|K|3|-4|5|F|7|Y|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]]]

<pre><code>files:
 "/etc/nginx/conf.d/proxy.conf" :
 mode: "000755"
 owner: root
 group: root
 content: |
 client_max_body_size 20M;
</code></pre>

Modified the above answer for the sake of security (and the syntax was wrong, see, two 'owner:' entries in the YAML), guys, please don't set 777 permissions on ANYTHING. Unless you enjoy being hacked, and set the owner of Nginx config files to root.

Also see the <a href="https://stackoverflow.com/a/28313384/184184">below answer</a> to make nginx pickup this change after deployment.

blocks|key|2781587|text|编辑:使用Nick+Parson的accepted中的说明部署构建后，可能需要重新启动nginx服务器以获取更改。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2781588|为此，请ssh到实例并执行以下操作|2781589|sudo+service+nginx+reload|offset|length|style|CODE|2781590|要了解有关重新加载的更多信息，请参阅http://nginx.org/en/docs/beginners_guide.html。|2781591|在Elastic+Beanstalk的前一个版本中，我可以添加一个container_command来完成此任务，但现在我发现，就像@cdmckay一样，这会导致部署失败。如果您重新构建您的环境，它将获取client_max_body_size设置，只要该指令在您的配置文件中。|2781592|entityMap|0|LINK|mutability|MUTABLE|url|http://nginx.org/en/docs/beginners_guide.html^0|0|0|0|P|0|I|19|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|X|8|@$F|Y|G|Z|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|10|8|@]|9|@$F|11|G|12|1|13]]|A|$]]|$1|L|3|M|5|6|7|14|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|U]]]]

EDIT: After you've deployed a build with the instructions in the accepted answer by Nick Parsons, you may need to restart the nginx server to pick up the changes.

To do this, ssh to the instance and do

<code>sudo service nginx reload</code>

To learn more about reloading, see <a href="http://nginx.org/en/docs/beginners_guide.html" rel="noreferrer">http://nginx.org/en/docs/beginners_guide.html</a>.

In a previous version of Elastic Beanstalk, I was able to add a container_command to accomplish this, but now I am finding, like @cdmckay, that this causes a deployment failure. If you rebuild your environment it will pick up the client_max_body_size settings as well as long as that instruction is in your config file.

blocks|key|177598|text|被接受的答案对我不起作用，因为我有一个基于JVM的应用程序，而且它似乎对NGINX的配置有所不同。我会看到在部署过程中创建了一个proxy.conf文件，但随后在部署完成之前将其删除。亚马逊网络服务文档解释了如何使用configure+the+proxy|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|177599|创建只包含以下行的.ebextensions/nginx/conf.d/proxy.conf文件：client_max_body_size+40M;|style|CODE|177600|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/java-se-nginx.html^0|30|J|0|0|9|11|1D|P|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@$A|U|B|V|F|G]|$A|W|B|X|F|G]]|9|@]|C|$]]|$1|H|3|-4|5|6|7|Y|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

The accepted answer didn't work for me since I have a JVM-based app and it seems to do NGINX configuration differently. I would see a proxy.conf file being created during the deploy but then later deleted before the deploy was completed. AWS documentation explains how to <a href="https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/java-se-nginx.html" rel="noreferrer">configure the proxy</a>:

Create an <code>.ebextensions/nginx/conf.d/proxy.conf</code> file that contains just the line: <code>client_max_body_size 40M;</code>

blocks|key|2781614|text|或者，您可以将代理服务器更改为Apache。要执行此操作，请转到Configuration并编辑Software+Configuration。这里的第一个选项是“代理服务器”，选择“apache”。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2781615|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Alternatively you could change the proxy server to Apache.
To do this, go to the Configuration and Edit the Software Configuration. The first option here is “Proxy server”, select “apache”.

blocks|key|2994184|text|根据接受的答案，您可能需要重新加载nginx配置文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2994185|为了做到这一点，添加以下命令|2994186|+++container_commands:
++++++01_reload_nginx:
++++++++command:+"service+nginx+reload"|code-block|syntax|javascript|2994187|与ssh进入您的eb实例并使用命令手动操作相比，这是更好的做法。|2994188|这与公认的答案相结合，为我解决了同样的问题。(Rails、Puma、NGINX)|2994189|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

Following on from the accepted answer, you need may need to reload the nginx config file. 

In order to do this add the following command

<pre><code> container_commands:
 01_reload_nginx:
 command: "service nginx reload"
</code></pre>

This would be better practice than ssh'ing into your eb instance and manually doing it with a command.

This combined with the accepted answer solved the same issue for me. (Rails, Puma, NGINX)

blocks|key|177615|text|对于没有Docker的Golang，我遵循了aws文档中的以下说明：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|177616|177617|配置反向代理|blockquote|177618|177619|如果除了nginx.conf+http块中的指令之外还想包含指令，还可以在源包的.ebextensions/nginx/conf.d/目录中提供额外的配置文件。此目录中的所有文件都必须具有.conf扩展名。http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/go-environment.html#go-complex-apps|offset|length|style|CODE|177620|177621|我在项目的根目录下用.ebextensions/nginx/conf.d/创建了文件proxy.conf，里面只有一行代码：|177622|client_max_body_size+20M;|code-block|syntax|javascript|177623|如果仍然不起作用，请确保您的展开压缩包中包含.ebextensions文件夹和子文件夹。无需手动重启Nginx。|177624|entityMap|0|LINK|mutability|MUTABLE|url|http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/go-environment.html#go-complex-apps^0|0|0|0|0|14|R|2V|2H|0|0|0|A|R|16|A|0|0|M|D|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|15|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|16|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|17|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|18|8|@$I|19|J|1A|K|L]]|9|@$I|1B|J|1C|1|1D]]|A|$]]|$1|M|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|1F|8|@$I|1G|J|1H|K|L]|$I|1I|J|1J|K|L]]|9|@]|A|$]]|$1|P|3|Q|5|R|7|1K|8|@]|9|@]|A|$S|T]]|$1|U|3|V|5|6|7|1L|8|@$I|1M|J|1N|K|L]]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1O|8|@]|9|@]|A|$]]]|X|$Y|$5|Z|10|11|A|$12|13]]]]

For Golang without Docker I followed these instructions from aws doc:

<blockquote>
 Configuring the Reverse Proxy
 
 If you want to include directives in addition to those in the nginx.conf http block, you can also provide additional configuration files in the <code>.ebextensions/nginx/conf.d/</code> directory of your source bundle. All files in this directory must have the .conf extension.
 <a href="http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/go-environment.html#go-complex-apps" rel="nofollow noreferrer">http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/go-environment.html#go-complex-apps</a>
</blockquote>

I created the file <code>proxy.conf</code> in <code>.ebextensions/nginx/conf.d/</code> at the root of my project, with simply 1 line inside:

<pre><code>client_max_body_size 20M;
</code></pre>

If it still doesn't work, make sure <code>.ebextensions</code> folder and sub-folders are included in your deployment zip. No need to restart Nginx manually.

blocks|key|2994221|text|被接受的答案对我不起作用，所以我用自己的配置覆盖了nginx配置。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2994222|我在.ebextensions/nginx/目录下创建了一个名为nginx.conf的文件|offset|length|style|CODE|2994223|我使用SSHed进入我的Beanstalk应用程序的运行实例，并使用cat+/etc/nginx/nginx.conf复制nginx.conf文件的内容，然后从终端进行复制。|2994224|我将内容粘贴到之前在.ebextensions/nginx/中创建的nginx.conf文件中，并修改了http指令以包含client_max_body_size+50M;。我最终使用eb+deploy重新部署了我的应用程序，它起作用了。在部署过程中，您应该会收到以下消息：|2994225|2994226|信息:在'.ebextensions/+Nginx‘目录中检测到nginx配置。AWS+Elastic+Beanstalk将不再管理此环境的Nginx配置。|blockquote|2994227|2994228|2994229|以下是我的.ebextensions/nginx/nginx.conf文件的内容：|2994230|#+Elastic+Beanstalk+Nginx+Configuration+File

user++++++++++++++++++++nginx;
error_log+++++++++++++++/var/log/nginx/error.log+warn;
pid+++++++++++++++++++++/var/run/nginx.pid;
worker_processes++++++++auto;
worker_rlimit_nofile++++33193;

events+{
++++worker_connections++1024;
}

http+{
++++include+++++++/etc/nginx/mime.types;
++++default_type++application/octet-stream;

++++log_format++main++'$remote_addr+-+$remote_user+[$time_local]+"$request"+'
++++++++++++++++++++++'$status+$body_bytes_sent+"$http_referer"+'
++++++++++++++++++++++'"$http_user_agent"+"$http_x_forwarded_for"';

++++include+++++++conf.d/*.conf;

++++map+$http_upgrade+$connection_upgrade+{
++++++++default+++++"upgrade";
++++}

++++server+{
++++++++listen++++++++80+default_server;
++++++++access_log++++/var/log/nginx/access.log+main;

++++++++client_header_timeout+60;
++++++++client_body_timeout+++60;
++++++++keepalive_timeout+++++60;
++++++++gzip++++++++++++++++++off;
++++++++gzip_comp_level+++++++4;
++++++++gzip_types+text/plain+text/css+application/json+application/javascript+application/x-javascript+text/xml+application/xml+application/xml%2Brss+text/javascript;

++++++++#+Include+the+Elastic+Beanstalk+generated+locations
++++++++include+conf.d/elasticbeanstalk/*.conf;
++++}

++++client_max_body_size+50M;
}|code-block|syntax|javascript|2994231|我不需要重新启动nginx服务或环境。|2994232|注意：确保您的.ebextensions是在部署期间创建并上传到Beanstalk的.zip文件的一部分(如果您正在使用它，则在.gitignore或.ebignore中不会忽略它)。|BOLD|2994233|entityMap^0|0|2|K|W|A|0|Y|P|1P|A|0|A|K|Y|A|1P|P|2K|9|0|0|0|0|0|5|U|0|0|0|0|2|1S|A|23|9|0^^$0|@$1|2|3|4|5|6|7|15|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|16|8|@$D|17|E|18|F|G]|$D|19|E|1A|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|1B|8|@$D|1C|E|1D|F|G]|$D|1E|E|1F|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|1G|8|@$D|1H|E|1I|F|G]|$D|1J|E|1K|F|G]|$D|1L|E|1M|F|G]|$D|1N|E|1O|F|G]]|9|@]|A|$]]|$1|L|3|-4|5|6|7|1P|8|@]|9|@]|A|$]]|$1|M|3|N|5|O|7|1Q|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|1R|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|1S|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|1T|8|@$D|1U|E|1V|F|G]]|9|@]|A|$]]|$1|T|3|U|5|V|7|1W|8|@]|9|@]|A|$W|X]]|$1|Y|3|Z|5|6|7|1X|8|@]|9|@]|A|$]]|$1|10|3|11|5|6|7|1Y|8|@$D|1Z|E|20|F|12]|$D|21|E|22|F|G]|$D|23|E|24|F|G]]|9|@]|A|$]]|$1|13|3|-4|5|6|7|25|8|@]|9|@]|A|$]]]|14|$]]

The accepted answer did not work for me, so instead I overrode the nginx configuration with my own.

I created a file called <code>nginx.conf</code> under the directory <code>.ebextensions/nginx/</code>

I SSHed into a running instance of my Beanstalk app, and copied the contents of the <code>nginx.conf</code> file, using <code>cat /etc/nginx/nginx.conf</code> and copying from the terminal.

I pasted the contents into the <code>nginx.conf</code> file I previously created in <code>.ebextensions/nginx/</code>, and modified the http directive to include <code>client_max_body_size 50M;</code>. I finally redeployed my app using <code>eb deploy</code> and it worked. You should get the following message during deployment:

<blockquote>
 INFO: Nginx configuration detected in the '.ebextensions/nginx'
 directory. AWS Elastic Beanstalk will no longer manage the Nginx
 configuration for this environment.
</blockquote>

These are the contents of my <code>.ebextensions/nginx/nginx.conf</code> file:

<pre><code># Elastic Beanstalk Nginx Configuration File

user nginx;
error_log /var/log/nginx/error.log warn;
pid /var/run/nginx.pid;
worker_processes auto;
worker_rlimit_nofile 33193;

events {
 worker_connections 1024;
}

http {
 include /etc/nginx/mime.types;
 default_type application/octet-stream;

 log_format main '$remote_addr - $remote_user [$time_local] "$request" '
 '$status $body_bytes_sent "$http_referer" '
 '"$http_user_agent" "$http_x_forwarded_for"';

 include conf.d/*.conf;

 map $http_upgrade $connection_upgrade {
 default "upgrade";
 }

 server {
 listen 80 default_server;
 access_log /var/log/nginx/access.log main;

 client_header_timeout 60;
 client_body_timeout 60;
 keepalive_timeout 60;
 gzip off;
 gzip_comp_level 4;
 gzip_types text/plain text/css application/json application/javascript application/x-javascript text/xml application/xml application/xml+rss text/javascript;

 # Include the Elastic Beanstalk generated locations
 include conf.d/elasticbeanstalk/*.conf;
 }

 client_max_body_size 50M;
}
</code></pre>

I did not have to restart the nginx service nor the environment.

Note: Make sure your .ebextensions is part of the .zip file created and uploaded to Beanstalk during deployment (it's not ignored in <code>.gitignore</code> or <code>.ebignore</code> if you're using it).

blocks|key|175198|text|用于Java平台的|type|unstyled|depth|inlineStyleRanges|entityRanges|data|175199|要创建NGINX配置代理文件，只需添加|offset|length|style|BOLD|175200|.ebextension/nginx/conf.d/proxy.conf文件|CODE|175201|其中包含content+client_max_body_size+20M;。|175202|"proxy.conf“将被部署到"/etc/+NGINX+/conf.d/proxy.conf”中，并自动包含在NGINX配置中。|175203|entityMap^0|0|0|J|0|0|12|0|10|0|0|12|C|P|0|0|1U|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@$D|S|E|T|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|U|8|@$D|V|E|W|F|G]|$D|X|E|Y|F|J]]|9|@]|A|$]]|$1|K|3|L|5|6|7|Z|8|@$D|10|E|11|F|G]|$D|12|E|13|F|J]]|9|@]|A|$]]|$1|M|3|N|5|6|7|14|8|@$D|15|E|16|F|G]]|9|@]|A|$]]|$1|O|3|-4|5|6|7|17|8|@]|9|@]|A|$]]]|P|$]]

For Java Platform

To create the NGINX config proxy file you should just add

<code>.ebextension/nginx/conf.d/proxy.conf</code> file

with the content <code>client_max_body_size 20M;</code> in it. 

"proxy.conf" will be deployed to "/etc/nginx/conf.d/proxy.conf" and automatically included by the NGINX config.

blocks|key|2994270|text|我唯一能做的就是在.ebextensions中创建一个".config“文件，如下所示：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2994271|.ebextensions/
+++++++++++proxy.config|code-block|syntax|javascript|2994272|在.config文件中仅包含以下内容：|2994273|files:
++"/etc/nginx/conf.d/proxy.conf":
+++++content:+%7C
+++++++client_max_body_size+50M;|2994274|不需要子文件夹，不需要重新启动应用程序服务器，注意在.ebextensions中是一个".config“而不是".conf”文件，并使用适当的缩进来避免在亚马逊网络服务控制台中出现错误。其余的都是一样的，不管文件名是什么。|2994275|感谢：http://kroltech.com/2014/09/14/quick-tip-increase-upload-size-in-aws-elastic-beanstalk-node-js-env/|offset|length|2994276|entityMap|0|LINK|mutability|MUTABLE|url|http://kroltech.com/2014/09/14/quick-tip-increase-upload-size-in-aws-elastic-beanstalk-node-js-env/^0|0|0|0|0|0|3|2R|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|10|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|12|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|13|8|@]|9|@$O|14|P|15|1|16]]|A|$]]|$1|Q|3|-4|5|6|7|17|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X]]]]

The only thing that worked for me was to create a ".config" file inside .ebextensions like this:

<pre><code>.ebextensions/
 proxy.config
</code></pre>

with only this content in the .config file:

<pre><code>files:
 "/etc/nginx/conf.d/proxy.conf":
 content: |
 client_max_body_size 50M;
</code></pre>

no need for subfolders, no need to restart the application server, pay attention that is a ".config" not a ".conf" file inside .ebextensions and the use of proper indentation to avoid errors in the aws console the rest is the same doesn't matter the name of the file, 

thanks to :
<a href="http://kroltech.com/2014/09/14/quick-tip-increase-upload-size-in-aws-elastic-beanstalk-node-js-env/" rel="noreferrer">http://kroltech.com/2014/09/14/quick-tip-increase-upload-size-in-aws-elastic-beanstalk-node-js-env/</a>

blocks|key|2781710|text|我也在努力解决同样的问题，但没能解决它，最后它起作用了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2781711|这是我的congfig文件，|2781712|files:
++"/etc/nginx/conf.d/01_proxy.conf":
++++mode:+"000755"
++++owner:+root
++++group:+root
++++content:+%7C
++++++client_max_body_size+50M;
++++++client_body_buffer_size+16k;

container_commands:
++01_reload_nginx:
++++command:+"sudo+service+nginx+reload"|code-block|syntax|javascript|2781713|问题是，|2781714|在创建构建时，我使用了一个不包含.ebextensions文件夹的python脚本作为代码管道。|2781715|2781716|这是我的几点心得，|2781717|2781718|确保您的.ebextensions文件夹包含在您的构建版本的压缩文件夹中，该文件夹位于您的aws帐户的s3bucket中|ordered-list-item|2781719|确保它不在.gitignore文件中|2781720|如果您使用脚本生成构建版本，请确保它包含.ebextensions|2781721|2781722|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|12|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|13|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|14|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|15|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|16|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|17|8|@]|9|@]|A|$]]|$1|Q|3|R|5|S|7|18|8|@]|9|@]|A|$]]|$1|T|3|U|5|S|7|19|8|@]|9|@]|A|$]]|$1|V|3|W|5|S|7|1A|8|@]|9|@]|A|$]]|$1|X|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]]|Z|$]]

I was struggling with the same issue but wasn't able the resolve it, finally its working.

here is my congfig file,

<pre><code>files:
 "/etc/nginx/conf.d/01_proxy.conf":
 mode: "000755"
 owner: root
 group: root
 content: |
 client_max_body_size 50M;
 client_body_buffer_size 16k;

container_commands:
 01_reload_nginx:
 command: "sudo service nginx reload"
</code></pre>

The issue was, 

<blockquote>
 I was using a python script for code pipeline which does not include
 the .ebextensions folder while creating the build.
</blockquote>

Here are my few cents,

<ol>
<li>make sure that your .ebextensions folder is included in your build's zip folder which is located in s3bucket of your aws account</li>
<li>make sure it is not in the .gitignore file </li>
<li>if you are using a script to generate the build make sure it
includes .ebextensions</li>
</ol>

blocks|key|2781734|text|在花了3天的时间试图解决这个问题后，我立即与令人惊叹的AWS支持团队进行了电话交谈，他们给了我一些关于如何解决这个问题的线索。首先，我的项目是用JAVA编写的，我使用maven和spring+boot通过Elastic+Beanstalk+(EBS)运行它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2781735|2781736|正如AWS'+documentation上所解释的，您需要将自定义nginx设置存储在项目的根级别中。为此，我创建了一个client_max_body_size.conf文件，并将其放在以下路径中：myprojectname/src/main/resources/ebextensions/nginx/conf.d/client_max_body_size.conf此文件仅包含以下行：|ordered-list-item|offset|length|style|BOLD|2781737|2781738|client_max_body_size+10M；|2781739|将maven配置为在构建过程中将此文件添加到项目的根文件夹中。这有点棘手，我需要在我的POM.xml中添加以下配置(source)：|unordered-list-item|2781740|2781741|maven-resources-plugin+3.1.0+copy-resources验证copy-resources+${basedir}/target/.ebextensions+src/main/resources/ebextensions+true|2781742|2781743|您现在已经可以在本地构建项目，并运行以下SSH命令来验证它是否确实位于项目的根目录中：|2781744|2781745|jar+tf+main-1.0-SNAPSHOT.jar+%7C+grep+.ebextensions|2781746|Now这是个棘手的部分。当你上传到EBS时，你的文件应该只包含SNAPSHOT.jar文件和.ebextensions文件夹。例如，如果您现在将压缩jar文件和文件夹并手动上传，它将工作！|2781747|
|2781748|，因为我正在使用Jenkins进行部署，特别是AWS+EBS+Deployment+Plugin+-您需要更改部署中包含的文件/文件夹的设置。现在，由于某种原因，我无法包含.ebextensions文件夹，所以除了文件夹和.jar文件之外，我只排除了其他所有内容。|2781749|2781750|📷|atomic|2781751|​|2781752|这行得通！|2781753|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/java-se-nginx.html|1|https://maven.apache.org/plugins/maven-resources-plugin/examples/copy-resources.html|2|https://wiki.jenkins-ci.org/display/JENKINS/AWSEB%2BDeployment%2BPlugin|3|IMAGE|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/c0081132894f9d753c4ccb88f0f7fc5d.png|imageAlt^0|0|0|2R|2C|2|I|0|0|0|0|1M|6|1|0|0|0|0|0|0|0|0|0|N|P|2|0|0|0|1|3|0|0|0^^$0|@$1|2|3|4|5|6|7|1U|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|1V|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|1W|8|@$F|1X|G|1Y|H|I]]|9|@$F|1Z|G|20|1|21]]|A|$]]|$1|J|3|-4|5|6|7|22|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|23|8|@]|9|@]|A|$]]|$1|M|3|N|5|O|7|24|8|@]|9|@$F|25|G|26|1|27]]|A|$]]|$1|P|3|-4|5|6|7|28|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|29|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|2A|8|@]|9|@]|A|$]]|$1|T|3|U|5|E|7|2B|8|@]|9|@]|A|$]]|$1|V|3|-4|5|6|7|2C|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|2D|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|O|7|2E|8|@]|9|@]|A|$]]|$1|10|3|11|5|6|7|2F|8|@]|9|@]|A|$]]|$1|12|3|13|5|O|7|2G|8|@]|9|@$F|2H|G|2I|1|2J]]|A|$]]|$1|14|3|-4|5|6|7|2K|8|@]|9|@]|A|$]]|$1|15|3|16|5|17|7|2L|8|@]|9|@$F|2M|G|2N|1|2O]]|A|$]]|$1|18|3|19|5|6|7|2P|8|@]|9|@]|A|$]]|$1|1A|3|1B|5|6|7|2Q|8|@]|9|@]|A|$]]|$1|1C|3|-4|5|6|7|2R|8|@]|9|@]|A|$]]]|1D|$1E|$5|1F|1G|1H|A|$1I|1J]]|1K|$5|1F|1G|1H|A|$1I|1L]]|1M|$5|1F|1G|1H|A|$1I|1N]]|1O|$5|1P|1G|1Q|A|$1R|1S|1T|-4]]]]

After 3 long days of trying to figure this one out, I jumped on a call with the amazing AWS support team and they gave me some clues about how to solve it.
First, my project is in JAVA and I use maven and spring boot to run it through Elastic Beanstalk (EBS).

<ol>
<li>As explained on <a href="https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/java-se-nginx.html" rel="nofollow noreferrer">AWS' documentation</a>, you need to have the custom nginx settings stored in the root level of your project.
To do that I have created a client_max_body_size.conf file and placed it in the following path:
myprojectname/src/main/resources/ebextensions/nginx/conf.d/client_max_body_size.conf
This file contains only the following line:

<pre><code>client_max_body_size 10M;
</code></pre></li>
<li>Configure maven to add this file in the root folder of my project during the build. 
This was a bit tricky, I needed to add the following configuration (<a href="https://maven.apache.org/plugins/maven-resources-plugin/examples/copy-resources.html" rel="nofollow noreferrer">source</a>) in my POM.xml:

<pre><code>&lt;plugin&gt;
&lt;artifactId&gt;maven-resources-plugin&lt;/artifactId&gt;
&lt;version&gt;3.1.0&lt;/version&gt;
&lt;executions&gt;
 &lt;execution&gt;
 &lt;id&gt;copy-resources&lt;/id&gt;
 &lt;!-- here the phase you need --&gt;
 &lt;phase&gt;validate&lt;/phase&gt;
 &lt;goals&gt;
 &lt;goal&gt;copy-resources&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;configuration&gt;
 &lt;outputDirectory&gt;${basedir}/target/.ebextensions&lt;/outputDirectory&gt;
 &lt;resources&gt;
 &lt;resource&gt;
 &lt;directory&gt;src/main/resources/ebextensions&lt;/directory&gt;
 &lt;filtering&gt;true&lt;/filtering&gt;
 &lt;/resource&gt;
 &lt;/resources&gt;
 &lt;/configuration&gt;
 &lt;/execution&gt;
&lt;/executions&gt;
</code></pre>

</li>
<li>You can now already build your project locally and run the following SSH command to validate it's actually located in the root of your project:

<pre><code>jar tf main-1.0-SNAPSHOT.jar | grep .ebextensions
</code></pre></li>
<li>Now it's the tricky part. When you upload it to EBS, your file should contain only the SNAPSHOT.jar file and the .ebextensions folder. For example, if now you will zip the jar file and the folder and upload it manually, it will work!</li>
<li>Since I am using Jenkins for my deployment, and specifically the <a href="https://wiki.jenkins-ci.org/display/JENKINS/AWSEB+Deployment+Plugin" rel="nofollow noreferrer">AWS EBS Deployment Plugin</a> - you need to change the settings of the files/folder you include in the deployment. 
Now for some reason I wasn't able to include the .ebextensions folder so I just excluded everything else except the folder and the .jar file.
<a href="https://i.stack.imgur.com/y7EyY.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/y7EyY.png" alt="enter image description here"></a></li>
</ol>

This works!

blocks|key|2781755|text|这是AWS+provided+solution，它可以工作(根据需要调整大小)|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2781756|files:
++"/opt/elasticbeanstalk/hooks/appdeploy/enact/12_add_nginx_configuration.sh":
++++mode:+"000755"
++++owner:+root
++++group:+root
++++content:+%7C
++++++#!/usr/bin/env+bash
++++++/bin/echo+"client_max_body_size+50M;"+>+/etc/nginx/conf.d/proxy.conf
++++++/sbin/service+nginx+reload|code-block|syntax|javascript|2781757|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/awsdocs/elastic-beanstalk-samples/blob/master/configuration-files/aws-provided/instance-configuration/change-nginx-max-body-size.config^0|2|L|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]]|C|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|C|$G|H]]|$1|I|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]]]

This is the <a href="https://github.com/awsdocs/elastic-beanstalk-samples/blob/master/configuration-files/aws-provided/instance-configuration/change-nginx-max-body-size.config" rel="noreferrer">AWS provided solution</a>, and it works (adjust the size to your needs)

<pre><code>files:
 "/opt/elasticbeanstalk/hooks/appdeploy/enact/12_add_nginx_configuration.sh":
 mode: "000755"
 owner: root
 group: root
 content: |
 #!/usr/bin/env bash
 /bin/echo "client_max_body_size 50M;" &gt; /etc/nginx/conf.d/proxy.conf
 /sbin/service nginx reload
</code></pre>

blocks|key|176065|text|如果您运行的是EC2，并且自己安装了nginx，那么最好的解决方案是在|type|unstyled|depth|inlineStyleRanges|entityRanges|data|176066|/etc/nginx/conf.d|code-block|syntax|javascript|176067|文件夹：|176068|sudo+nano+/etc/nginx/conf.d/proxy.conf|176069|然后在那里添加以下行：|176070|client_max_body_size+20M;|176071|然后保存并重新启动nginx：|176072|sudo+systemctl+restart+nginx|176073|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|Y|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|10|8|@]|9|@]|A|$]]|$1|Q|3|R|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

If you are running EC2 and installed nginx yourself, your best solution is to create a new file in 

<pre><code>/etc/nginx/conf.d
</code></pre>

folder:

<pre><code>sudo nano /etc/nginx/conf.d/proxy.conf
</code></pre>

and then add the following line there:

<pre><code>client_max_body_size 20M;
</code></pre>

then save and restart nginx:

<pre><code>sudo systemctl restart nginx
</code></pre>

blocks|key|175278|text|我尝试了添加实现级别配置的所有.ebextensions方法，但在最新的Amazon+Linux+AMI中它对我没有帮助。我做了很多研究，在浏览了日志后，我发现部署任务运行器每次都会检查一个名为.platform的文件夹，我想添加一个就像.ebextensions一样。下面是我在我的项目根文件夹中所做的设置。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|175279|将下面的文件夹设置添加到项目文件夹的根目录下。|175280|文件夹结构+(.platform/nginx/conf.d/proxy.conf)|BOLD|175281|.platform/
+++++++++nginx/
++++++++++++++conf.d/
++++++++++++++++++++proxy.conf
+++++++++00_myconf.config|code-block|syntax|javascript|175282|文件1的内容-+proxy.conf+(在.platform/nginx/conf.d/文件夹内)|175283|client_max_body_size+50M;|175284|文件2的内容-+00_myconf.config+(在.platform/文件夹内)|175285|container_commands:
++01_reload_nginx:
++++command:+"service+nginx+reload"|175286|完全注意扩展。第一个文件是.conf，第二个文件是.config。|175287|现在，将您的项目重新部署到Amazon+Elastic+Beanstalk，您将看到它的魔力。此配置将添加到您作为弹性伸缩一部分创建的所有EC2实例中。|175288|下面是详细的文件夹结构。|175289|​|175290|📷|atomic|175291|175292|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/57d49cf0b4a4cc661d18437dd5d39c8b.jpeg|imageAlt^0|F|D|2P|9|0|0|0|5|0|0|8|A|L|N|0|0|8|G|R|A|0|0|D|5|P|7|0|0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|1I|8|@$9|1J|A|1K|B|C]|$9|1L|A|1M|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1N|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|1O|8|@$9|1P|A|1Q|B|J]]|D|@]|E|$]]|$1|K|3|L|5|M|7|1R|8|@]|D|@]|E|$N|O]]|$1|P|3|Q|5|6|7|1S|8|@$9|1T|A|1U|B|J]|$9|1V|A|1W|B|C]]|D|@]|E|$]]|$1|R|3|S|5|M|7|1X|8|@]|D|@]|E|$N|O]]|$1|T|3|U|5|6|7|1Y|8|@$9|1Z|A|20|B|J]|$9|21|A|22|B|C]]|D|@]|E|$]]|$1|V|3|W|5|M|7|23|8|@]|D|@]|E|$N|O]]|$1|X|3|Y|5|6|7|24|8|@$9|25|A|26|B|J]|$9|27|A|28|B|J]]|D|@]|E|$]]|$1|Z|3|10|5|6|7|29|8|@]|D|@]|E|$]]|$1|11|3|12|5|6|7|2A|8|@]|D|@]|E|$]]|$1|13|3|14|5|6|7|2B|8|@]|D|@]|E|$]]|$1|15|3|16|5|17|7|2C|8|@]|D|@$9|2D|A|2E|1|2F]]|E|$]]|$1|18|3|14|5|6|7|2G|8|@]|D|@]|E|$]]|$1|19|3|-4|5|6|7|2H|8|@]|D|@]|E|$]]]|1A|$1B|$5|1C|1D|1E|E|$1F|1G|1H|-4]]]]

I have tried all <code>.ebextensions</code> method of adding implementation level configuration and it didn't helped me in the latest Amazon Linux AMI. I have did a lot research and after going through the logs i can find the deployment task runner is checking for a folder called <code>.platform</code> everytime and i thought of add one just like the .ebextensions. Below is the settings i have done in my root folder of my project.

Add the below folder setup in the root level of your project folder.

Folder structure (.platform/nginx/conf.d/proxy.conf)

<pre><code>.platform/
 nginx/
 conf.d/
 proxy.conf
 00_myconf.config
</code></pre>

Content of File 1 - proxy.conf (Inside <code>.platform/nginx/conf.d/</code> folder)

<pre><code>client_max_body_size 50M;
</code></pre>

Content of File 2 - 00_myconf.config (Inside <code>.platform/</code> folder)

<pre><code>container_commands:
 01_reload_nginx:
 command: "service nginx reload"
</code></pre>

Care full with the extensions. First file is .conf and second file is .config.

Now redeploy your project to Amazon Elastic Beanstalk and you will see the magic. This configuration will be added to all your EC2 instances, created as part of auto scaling.

Detailed folder structure below.

<a href="https://i.stack.imgur.com/aNnIW.jpg" rel="noreferrer"><img src="https://i.stack.imgur.com/aNnIW.jpg" alt="enter image description here"></a>

blocks|key|2994463|text|除了client_max_body_size之外，我还必须添加client_body_buffer_size.以下是适用于2+MB附件的.config文件：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2994464|2994465|文件："/etc/nginx/conf.d/proxy.conf“：|blockquote|2994466|2994467|模式："000755“|2994468|所有者:+root|2994469|组:根|2994470|内容：|2994471|proxy_buffering+on；|2994472|proxy_buffer_size+128k；|2994473|proxy_buffers+8+256k；|2994474|client_body_buffer_size+2M；|2994475|proxy_busy_buffers_size+256k；|2994476|fastcgi_buffers+1616k；|2994477|fastcgi_buffer_size+32k；|2994478|client_max_body_size+3M;|2994479|entityMap^0|V|N|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1A|8|@$9|1B|A|1C|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|1D|8|@]|D|@]|E|$]]|$1|G|3|H|5|I|7|1E|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|1F|8|@]|D|@]|E|$]]|$1|K|3|L|5|6|7|1G|8|@]|D|@]|E|$]]|$1|M|3|N|5|6|7|1H|8|@]|D|@]|E|$]]|$1|O|3|P|5|6|7|1I|8|@]|D|@]|E|$]]|$1|Q|3|R|5|6|7|1J|8|@]|D|@]|E|$]]|$1|S|3|T|5|6|7|1K|8|@]|D|@]|E|$]]|$1|U|3|V|5|6|7|1L|8|@]|D|@]|E|$]]|$1|W|3|X|5|6|7|1M|8|@]|D|@]|E|$]]|$1|Y|3|Z|5|6|7|1N|8|@]|D|@]|E|$]]|$1|10|3|11|5|6|7|1O|8|@]|D|@]|E|$]]|$1|12|3|13|5|6|7|1P|8|@]|D|@]|E|$]]|$1|14|3|15|5|6|7|1Q|8|@]|D|@]|E|$]]|$1|16|3|17|5|6|7|1R|8|@]|D|@]|E|$]]|$1|18|3|-4|5|6|7|1S|8|@]|D|@]|E|$]]]|19|$]]

In addition to client_max_body_size, I had to add client_body_buffer_size. Here is the dot config file that worked, for a 2 MB attachment:
<blockquote>
files: &quot;/etc/nginx/conf.d/proxy.conf&quot; : 
mode: &quot;000755&quot; 
owner: root 
group: root 
content: | 
proxy_buffering on; 
proxy_buffer_size 128k; 
proxy_buffers 8 256k; 
client_body_buffer_size 2M; 
proxy_busy_buffers_size 256k; 
fastcgi_buffers 16 16k; 
fastcgi_buffer_size 32k; 
client_max_body_size 3M;
</blockquote>

blocks|key|176104|text|直接在.ebextensions中创建文件是I+found对我起作用的唯一方法。创建一个名为01_files.config的新文件，并粘贴以下内容：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|176105|files:
"/etc/nginx/conf.d/proxy.conf"+:
++++mode:+"000755"
++++owner:+root
++++group:+root
++++content:+%7C
+++++++client_max_body_size+20M;|code-block|syntax|javascript|176106|这将在部署时为您创建一个配置文件，将client_max_body_size设置为20MB+(更改#以满足您的需要)。|176107|entityMap|0|LINK|mutability|MUTABLE|url|https://www.zigpoll.com/blog/413-error-aws-eb-nginx^0|M|7|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]]|C|$]]|$1|D|3|E|5|F|7|W|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|X|8|@]|9|@]|C|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|C|$]]]|L|$M|$5|N|O|P|C|$Q|R]]]]

Creating a file in the .ebextensions directly is the only method <a href="https://www.zigpoll.com/blog/413-error-aws-eb-nginx" rel="nofollow noreferrer">I found</a> that has worked for me. Create a new file called 01_files.config and paste in the following:
<pre><code>files:
&quot;/etc/nginx/conf.d/proxy.conf&quot; :
 mode: &quot;000755&quot;
 owner: root
 group: root
 content: |
 client_max_body_size 20M;
</code></pre>
This will create a config file for you on deploy that sets the client_max_body_size to 20MB (change the # to suit your needs).

blocks|key|177791|text|使用Amazon+Linux+2时(与平台无关)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|177792|当您使用使用Amazon+Linux+AMI的较旧的Elastic+Beanstalk环境时，accepted+answer是正确的。较新的Elastic+Beanstalk环境使用Amazon+Linux+2+AMI。|offset|length|177793|在使用Amazon+Linux2时，您需要在.platform/目录而不是.ebextensions/中指定自定义Nginx配置。|style|CODE|177794|这意味着您需要使用content+client_max_body_size+50M;创建文件.platform/nginx/conf.d/proxy.conf。|177795|another+answer中也提到了.platform/目录，但仍然需要重新加载Ngix配置，不再需要重新加载Amazon+Linux2。|177796|您可以在Extending+Elastic+Beanstalk+Linux+platforms文档中找到有关这方面的更多选项。|177797|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/18951706/2111438|1|https://stackoverflow.com/a/61943622/2111438|2|https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/platforms-linux-extend.html^0|0|1B|F|0|0|M|A|11|E|0|H|P|1A|X|0|J|A|0|E|1|0|4|17|2|0^^$0|@$1|2|3|4|5|6|7|11|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|12|8|@]|9|@$D|13|E|14|1|15]]|A|$]]|$1|F|3|G|5|6|7|16|8|@$D|17|E|18|H|I]|$D|19|E|1A|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|1B|8|@$D|1C|E|1D|H|I]|$D|1E|E|1F|H|I]]|9|@]|A|$]]|$1|L|3|M|5|6|7|1G|8|@$D|1H|E|1I|H|I]]|9|@$D|1J|E|1K|1|1L]]|A|$]]|$1|N|3|O|5|6|7|1M|8|@]|9|@$D|1N|E|1O|1|1P]]|A|$]]|$1|P|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]]|Q|$R|$5|S|T|U|A|$V|W]]|X|$5|S|T|U|A|$V|Y]]|Z|$5|S|T|U|A|$V|10]]]]

<h1>When using Amazon Linux 2 (regardless of platform)</h1>
The <a href="https://stackoverflow.com/a/18951706/2111438">accepted answer</a> is correct when you're using an older Elastic Beanstalk environment using Amazon Linux AMI. Newer Elastic Beanstalk environments use the Amazon Linux 2 AMI.
When using Amazon Linux 2 you need to specify the custom Nginx config in the <code>.platform/</code> directory instead of the <code>.ebextensions/</code>.
This means that you'll need to create the file <code>.platform/nginx/conf.d/proxy.conf</code> with the content <code>client_max_body_size 50M;</code> instead.
The <code>.platform/</code> directory was also mentioned in <a href="https://stackoverflow.com/a/61943622/2111438">another answer</a>, but that still required reloading the Ngix config, with Amazon Linux 2 reloading is no longer needed.
You can find more options about this in the <a href="https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/platforms-linux-extend.html" rel="noreferrer">Extending Elastic Beanstalk Linux platforms</a> documentation.

blocks|key|2994551|text|对于那些在这里遇到困难的人，请使用：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2994552|我遵循了Jijo+Cleetus+answer，但没有起作用，但绝对指出了正确的方向。|2994553|但我担心为什么，因为如果我看到nginx.conf文件，它确实包含include+conf.d/*.conf，所以它应该包括the答案提到的代理文件。|CODE|2994554|此外，在80上侦听并标记为default_server的默认服务器也具有include+conf.d/elasticbeanstalk/*.conf|2994555|但是this+answer确实解决了这个问题，重要的是，.conf文件目录必须是.platform/nginx/conf.d/elasticbeanstalk而不是.platform/nginx/conf.d/。|2994556|所以：|2994557|.platform/nginx/conf.d/elasticbeanstalk/01-request-body.conf+.platform/nginx/conf.d/elasticbeanstalk/02-timeouts.conf|2994558|下面是一些例子|2994559|我还通过登录到ec2实例并运行nginx+-T来确认这一点，这将打印运行配置，以验证是否包含我的自定义配置。|2994560|我还在那里看到，默认的应用程序代理配置名为00_application.conf，nginx包含按字母顺序排列的文件，因此使用前缀数字来命名。|2994561|向通过CodePipeline部署的用户添加了注意事项：请确保在buildspec.yaml+->+artifacts部分中包含.platform/**/*|2994562|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/61943622/13754639|1|2|https://stackoverflow.com/a/65077638/13754639^0|H|1|0|4|C|0|0|F|A|X|L|1Q|3|1|0|D|E|10|12|0|S|5|14|13|2A|N|2|B|2|0|0|0|1O|1P|1K|0|0|F|8|0|L|J|0|0|S|W|E|1E|9|1S|E|0^^$0|@$1|2|3|4|5|6|7|1B|8|@$9|1C|A|1D|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1E|8|@]|D|@$9|1F|A|1G|1|1H]]|E|$]]|$1|H|3|I|5|6|7|1I|8|@$9|1J|A|1K|B|J]|$9|1L|A|1M|B|J]]|D|@$9|1N|A|1O|1|1P]]|E|$]]|$1|K|3|L|5|6|7|1Q|8|@$9|1R|A|1S|B|J]|$9|1T|A|1U|B|J]]|D|@]|E|$]]|$1|M|3|N|5|6|7|1V|8|@$9|1W|A|1X|B|J]|$9|1Y|A|1Z|B|J]|$9|20|A|21|B|J]]|D|@$9|22|A|23|1|24]]|E|$]]|$1|O|3|P|5|6|7|25|8|@]|D|@]|E|$]]|$1|Q|3|R|5|6|7|26|8|@$9|27|A|28|B|J]|$9|29|A|2A|B|J]]|D|@]|E|$]]|$1|S|3|T|5|6|7|2B|8|@]|D|@]|E|$]]|$1|U|3|V|5|6|7|2C|8|@$9|2D|A|2E|B|J]]|D|@]|E|$]]|$1|W|3|X|5|6|7|2F|8|@$9|2G|A|2H|B|J]]|D|@]|E|$]]|$1|Y|3|Z|5|6|7|2I|8|@$9|2J|A|2K|B|C]|$9|2L|A|2M|B|J]|$9|2N|A|2O|B|J]|$9|2P|A|2Q|B|J]]|D|@]|E|$]]|$1|10|3|-4|5|6|7|2R|8|@]|D|@]|E|$]]]|11|$12|$5|13|14|15|E|$16|17]]|18|$5|13|14|15|E|$16|17]]|19|$5|13|14|15|E|$16|1A]]]]

For those who are stumbling on here:
I followed <a href="https://stackoverflow.com/a/61943622/13754639">Jijo Cleetus</a> answer but did not work, but definitely pointed to the right direction.
But I am wordering why because if I see <code>nginx.conf</code> file, it does contain <code>include conf.d/*.conf</code> so it should include the proxy file as <a href="https://stackoverflow.com/a/61943622/13754639">the</a> answer mentioned.
Also the default server listening on 80 and marked as <code>default_server</code>, has <code>include conf.d/elasticbeanstalk/*.conf</code>
But <a href="https://stackoverflow.com/a/65077638/13754639">this answer</a> did solve the issue, in gist, the <code>.conf</code> files directory have to be <code>.platform/nginx/conf.d/elasticbeanstalk</code> instead of <code>.platform/nginx/conf.d/</code>.
So:
<code>.platform/nginx/conf.d/elasticbeanstalk/01-request-body.conf</code>
<code>.platform/nginx/conf.d/elasticbeanstalk/02-timeouts.conf</code>
are some examples
I also confirmed it by logging into the ec2 instance and running <code>nginx -T</code> which prints the running config to verify if my custom configs were included.
Also there I saw, the default application proxy config is named <code>00_application.conf</code> and nginx includes files in alphabetical order, so named it by prefixing numbers.
Added notes to those who are deploying via CodePipeline:
Make sure to include <code>.platform/**/*</code> in <code>buildspec.yaml</code> -&gt; <code>artifacts</code> section

blocks|key|174065|text|晚到派对上，但对于.NET核心，以下解决方案有效：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|174066|在/..platform/nginx/conf.d/proxy.conf中创建一个包含以下内容的文件：|174067|client_max_body_size+100M;|code-block|syntax|javascript|174068|确保在Visual+Studio的属性中，将此文件的“复制到输出目录”设置为"Always“，并且构建操作为”content“。|174069|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|O|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

Late to the party but for .NET Core the following solution works:
Make a file in /.platform/nginx/conf.d/proxy.conf with the content:
<pre><code>client_max_body_size 100M;
</code></pre>
Make sure in properties on Visual Studio that Copy to output directory is set to &quot;Always&quot; for this file and that the build action is &quot;content.&quot;

blocks|key|2994618|text|在这里尝试所有的解决方案都有很大的困难。我收到错误消息:+eb-engine.log中的未知指令"client_max_body_size“|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2994619|这个页面帮助我解决了这个问题：https://forums.aws.amazon.com/thread.jspa?threadID=334637|offset|length|2994620|Visual+Studio使用导致问题的某种编码创建了该文件，我可以将该文件保存/转换为ANSI编码，并按预期工作。|2994621|希望这篇文章能帮助那些被同样的问题困扰的人。|2994622|entityMap|0|LINK|mutability|MUTABLE|url|https://forums.aws.amazon.com/thread.jspa?threadID=334637^0|0|F|1L|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@$D|T|E|U|1|V]]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

Had a lot of trouble with this even trying all of the solutions here. I got the error message: unknown directive &quot;client_max_body_size&quot; in the eb-engine.log
This page help me solve the issue: <a href="https://forums.aws.amazon.com/thread.jspa?threadID=334637" rel="nofollow noreferrer">https://forums.aws.amazon.com/thread.jspa?threadID=334637</a>
Visual Studio had create the file in some encoding that caused the problem and I could save/convert the file to ANSI encoding and it worked as expected.
Hope this can help someone stuck with the same problem.

blocks|key|175414|text|针对Amazon+Linux+2的超级简单解决方案：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|175415|在与.ebextensions和.elasticbeanstalk相同的级别上，在名为.platform/nginx/conf.d/client_max_body_size.conf|175416|Add的目录下创建一个文件(显示了完整路径)：.platform/nginx/conf.d/client_max_body_size.conf|unordered-list-item|175417|
|175418|Add这一行20M;|175419|175420|Deploy!!|175421|
+.ebextensions+client_max_body_size|175422|这是基于AWS+NGINX+"Reverse+proxy+configuration"+Documentation的。|offset|length|175423|(这适用于在64位Amazon+Linux+2/3.2.0上运行的Django+3.1.4+%2B+Python+3.7+)|175424|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/platforms-linux-extend.html^0|0|0|0|0|0|0|0|0|4|1H|0|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|14|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|15|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|16|8|@]|9|@]|A|$]]|$1|I|3|J|5|F|7|17|8|@]|9|@]|A|$]]|$1|K|3|H|5|6|7|18|8|@]|9|@]|A|$]]|$1|L|3|M|5|F|7|19|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|1A|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1B|8|@]|9|@$R|1C|S|1D|1|1E]]|A|$]]|$1|T|3|U|5|6|7|1F|8|@]|9|@]|A|$]]|$1|V|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]]|W|$X|$5|Y|Z|10|A|$11|12]]]]

Super Simple Solution for Amazon Linux 2:
<ol>
<li>On the same level as .ebextensions and .elasticbeanstalk, create a
directory called .platform</li>
<li>Create a file (full path shown) under this directory called: .platform/nginx/conf.d/client_max_body_size.conf</li>
<li>Add this one line to the client_max_body_size.conf file: client_max_body_size 20M;</li>
<li>Deploy!!</li>
</ol>
This is based on <a href="https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/platforms-linux-extend.html" rel="noreferrer">AWS NGINX &quot;Reverse proxy configuration&quot; Documentation</a>.
(This worked w/ Django 3.1.4 + Python 3.7 running on 64bit Amazon Linux 2/3.2.0)

blocks|key|2782011|text|上述选项中的任何一个都可能或可能不起作用，|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2782012|如果您的proxy.config文件的行尾不正确，那么在尝试将您的代码部署到实例时，...but将会出错。|2782013|我们创建了.platform/nginx/conf.d/proxy.config文件，但是因为我们是在windows平台上开发和构建代码，所以行尾被设置为Windows+(CRLF)。|2782014|但是我们的AWS实例都是Linux，这意味着Unix+(LF)的终结。|2782015|所以当Linux试图读取文件时，failed...it甚至没有在事件或日志中给我们一个像样的错误，它只是说失败。|2782016|如果其他方法都不起作用，可能需要检查的最后一件事:)|2782017|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

Any of the above options may or may not work,
...but if you're line endings of the proxy.config file are not correct then AWS will just error when trying to deploy your code to the instance.
We created the .platform/nginx/conf.d/proxy.config file, but because we are developing and building the code on a windows platform, the line endings were set to Windows (CRLF).
But our AWS instances were all Linux, which expect the Unix (LF) ending.
So when Linux tried to read the file it just failed...it didn't even give us a decent error in the events or logs, it just said failed.
Maybe a last thing to check if nothing else works :)

blocks|key|177870|text|在EBS中为Nginx创建自动配置|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|177871|由于EBS是自动伸缩的，我们不能手动增加大小和请求超时，因此我们必须在源代码中添加conf文件，该文件会自动包含在EBS的nginx配置中|177872|https://akshaykrisonz.medium.com/fix-413-request-entity-too-large-nginx-error-on-aws-elastic-beanstalk-via-ebs-configuration-7533ad28ac06|177873|entityMap|0|LINK|mutability|MUTABLE|url^0|0|4|0|0|0|3T|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|T|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|U|8|@]|D|@$9|V|A|W|1|X]]|E|$]]|$1|J|3|-4|5|6|7|Y|8|@]|D|@]|E|$]]]|K|$L|$5|M|N|O|E|$P|I]]]]

Create Auto configuration for Nginx in EBS
Since the EBS is auto scaling we can’t increase the Size and request time out manually so we have to add conf file in you source code which automatically include in the nginx configuration in EBS
<a href="https://akshaykrisonz.medium.com/fix-413-request-entity-too-large-nginx-error-on-aws-elastic-beanstalk-via-ebs-configuration-7533ad28ac06" rel="nofollow noreferrer">https://akshaykrisonz.medium.com/fix-413-request-entity-too-large-nginx-error-on-aws-elastic-beanstalk-via-ebs-configuration-7533ad28ac06</a>

blocks|key|2782085|text|对于AWS+Beanstalk上的Spring+Boot+/+Java+/+Fat-Jar部署：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2782086|使用.platform的previous+answer在AWS+Linux2中是必需的，但与.ebextensions不同的是，您不能在fat+jar中包含.platform目录-它必须在Java+jar之外。|2782087|这篇有用的文章描述了如何设置Maven来创建用于部署的AWS+fat+jar。|2782088|https://www.coderdreams.com/deploying-spring-boot-app-to-aws-beanstalk-with-nginx-customization/|2782089|注意:不需要像前面的答案那样创建脚本来重新启动nginx服务器。|2782090|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/61943622/8711782|1^0|H|S|0|C|F|0|0|0|0|2O|1|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Z|8|@]|D|@$9|10|A|11|1|12]]|E|$]]|$1|H|3|I|5|6|7|13|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|14|8|@]|D|@$9|15|A|16|1|17]]|E|$]]|$1|L|3|M|5|6|7|18|8|@]|D|@]|E|$]]|$1|N|3|-4|5|6|7|19|8|@]|D|@]|E|$]]]|O|$P|$5|Q|R|S|E|$T|U]]|V|$5|Q|R|S|E|$T|K]]]]

For Spring Boot / Java / Fat-Jar deployments on AWS Beanstalk:
The <a href="https://stackoverflow.com/a/61943622/8711782">previous answer</a> using .platform is required in AWS Linux 2, but, unlike .ebextensions, you can't include the .platform directory inside the fat jar - it must be outside the Java jar.
This useful post describes how to set up Maven to create an AWS fat jar for deployment.
<a href="https://www.coderdreams.com/deploying-spring-boot-app-to-aws-beanstalk-with-nginx-customization/" rel="nofollow noreferrer">https://www.coderdreams.com/deploying-spring-boot-app-to-aws-beanstalk-with-nginx-customization/</a>
Note: there's no need to create a script to restart the nginx server as in the previous answer.

I'm running into "413 Request Entity Too Large" errors when posting files larger than 10MB to our API running on AWS Elastic Beanstalk.

I've done quite a bit of research and believe that I need to up the client_max_body_size for Nginx, however I cannot seem to find any documentation on how to do this using Elastic Beanstalk. My guess is that it needs to be modified using an ebetension file.

Anyone have thoughts on how I can up the limit? 10MB is pretty weak, there has to be a way to up this manually.

Increasing client_max_body_size in Nginx conf on AWS Elastic Beanstalk

Visual Studio

弹性伸缩

Spring Boot

服务器

Windows

Django

Python

Linux

Java

Unix

当将大于10MB的文件发布到运行在AWS Elastic Beanstalk上的应用程序接口时，我遇到了"413 Request Entity Too Large"错误。我已经做了相当多的研究，并相信我需要为Nginx建立client_max_body_size，但是我似乎找不到任何关于如何使用Elastic Bean...

问在AWS弹性豆茎上提高Nginx conf中的client_max_body_size
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在AWS弹性豆茎上提高Nginx conf中的client_max_body_sizeEN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在AWS弹性豆茎上提高Nginx conf中的client_max_body_size
EN