Geek Answers Handbook

Deploy web.config for amazon beanstalk

When I deploy the .net web application to Amazon Beanstalk, my local web.config is completely ignored, and it just gets replaced with this:

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
    <appSettings>
        <add key="PARAM3" value="" />
        <add key="PARAM4" value="" />
        <add key="PARAM1" value="" />
        <add key="PARAM2" value="" />
        <add key="PARAM5" value="" />
        <add key="AWS_SECRET_KEY" value="" />
        <add key="AWSSecretKey" value="" />
        <add key="AWS_ACCESS_KEY_ID" value="" />
        <add key="AWSAccessKey" value="" />
    </appSettings>
</configuration>

I thought that beanstalk was unable to parse part of my web.config, so I simplified web.config to a minimum:

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
  <appSettings>
    <add key="mykey" value="myvalue"/>
  </appSettings>
  <system.web>
    <compilation debug="true" targetFramework="4.5"/>
    <httpRuntime targetFramework="4.5"/>
  </system.web>
</configuration>

And I get the same result. my appSettings and all other sections of my web.config do not appear in the deployed web.config. I looked everywhere and I can not find documentation on this. I do not have any conversions in my local application (i.e. there is no web.release.config file). Is it possible to somehow disable this "feature" Beanstalk?

I do not ask for any action, I just want my original web.config to be deployed.

+4
1

Elastic Beanstalk, git.

0

More articles:


All Articles