Health checks fail when using the new publish to elastic beanstalk interface

[alexsaare]

Describe the bug
Health checks fail when using the new publish to elastic beanstalk interface

To Reproduce

1. Right click project in Visual Studio
2. Click "Publish to AWS..."
3. Select existing application environment
4. Click "Publish"

Expected behaviour
Application should be deployed the same as legacy interface

Computer (please complete the following information):

• Windows Version: Windows 11 Pro build 22621.963
• Visual Studio Version: 17.3.5
• AWS Toolkit for Visual Studio Version: 1.38.0.0

Additional context
Deploying .NET 6 application to Amazon Linux 2/2.4.2. "Publish to AWS Elastic Beanstalk (Legacy)" works as expected. Health check simply checks for 200 from specific end point,. Using ELB type Application Loadbalancer. Environment has 5 instances of t3a.small and is part of a VPC. Uses rolling deploy based on health with batch size of 50%. Application version is successfully pushed to instances in first batch but instances are not re-registered with loadbalancer gets stuck on the step saying "Registering instance(s) with the load balancer and waiting for them to be healthy." Under "causes" in the console no error codes are shown.

[alexsaare]

Further info: our environment does not use a proxy server

Further investigation:

The artifacts produced by the legacy deploy process are quite different to the new version.

• New version creates a "runtimes" folder
• New version generates an exe for the target project where as the legacy version creates a file named the same as the target project with with no extension
• The legacy version creates a Procfile file the new version does not
• New version creates a web.config file

[floralph]

Thank you for bringing this issue to our attention. To be sure I understand correctly, you deployed to a Beanstalk environment using the "Publish to AWS Elastic Beanstalk (Legacy)" option in the AWS Toolkit. Subsequently, you attempted to deploy the same project to the same Beanstalk environment using the "Publish to AWS" option. Do I have that correct?

[alexsaare]

Hi! Yes that is correct.

[floralph]

Do you see this behavior consistently when deploying with Publish to AWS? Do the legacy deployments work or fail as well?

If you haven't already, let's take a look at your log files. From Visual Studio, if you click on Extensions in the main menu then AWS Toolkit then View Toolkit Logs. Do you see any warnings/errors related to the deployment in those logs? If so, please post the details in this issue.

The toolkit uses the AWS dotnet deploy tool to perform these actions. What results do you get when trying to deploy this project using the deploy tool directly? https://aws.github.io/aws-dotnet-deploy/docs/commands/deploy/

[alexsaare]

Hi,

I just wanted to let you know it's been a busy start to the year and I will get those logs for you asap - The logs I have are full of other noise so I wanted to get a "clean" version for you.

The behaviour is consistent and the legacy version does not fail.

I think the main difference here will be the commands used to create the deploy artefacts as the packages are quite different. Hopefully the logs will shed some light.

Also, FYI, this affects more than one project/application.

[alexsaare]

Some company info redacted

Here's the output of the logs from the new publish

2023-01-06 09:40:56,363 [113] INFO Amazon.AWSToolkit.Credentials.Core.ProfileCredentialProviderFactory - Reloaded AWS Credential Profiles
Profiles found: 1
2023-01-06 09:41:03,539 [1] INFO Amazon.AwsToolkit.VsSdk.Common.VSWebProjectInfo - EnvDTEProject.FullName lookup yielded 'C:\Dev\XXXXX\XXXXX\XXXXX.services.sales\XXXXX.Services.Sales\XXXXX.Services.Sales.csproj'
2023-01-06 09:41:03,666 [1] INFO Amazon.AWSToolkit.S3FileFetcher - Null/empty hosted files location override
2023-01-06 09:41:03,669 [1] INFO Amazon.AWSToolkit.S3FileFetcher - Null/empty hosted files location override
2023-01-06 09:41:03,670 [1] INFO Amazon.AWSToolkit.S3FileFetcher - Probing for hosted file at url 'https://d3rrggjwfhwld2.cloudfront.net/CloudFormationTemplates/TemplatesManifest.xml'
2023-01-06 09:41:04,462 [134] DEBUG Amazon.AWSToolkit.Telemetry.Internal.TelemetryPublisher - Publishing 3 event(s)
2023-01-06 09:41:20,698 [177] INFO Amazon.AWSToolkit.VisualStudio.AWSToolkitPackage - Publishing 'XXXXX.Services.Sales' to Amazon Web Services
2023-01-06 09:41:39,951 [150] INFO Amazon.AWSToolkit.ElasticBeanstalk.Commands.BaseBeanstalkDeployCommand - Publish to AWS Elastic Beanstalk environment 'XXXXX-sales-uat-4' completed successfully
2023-01-06 09:41:41,957 [178] INFO Amazon.AWSToolkit.CommonUI.BaseAWSControl - Beginning loading data for EnvStatuse-ujy6hsdujj
2023-01-06 09:41:43,933 [178] INFO Amazon.AWSToolkit.CommonUI.BaseAWSControl - Data loaded data for EnvStatuse-ujy6hsdujj
2023-01-06 09:46:05,667 [15] DEBUG Amazon.AWSToolkit.Telemetry.Internal.TelemetryPublisher - Publishing 4 event(s)
2023-01-06 09:54:30,205 [116] DEBUG Amazon.AWSToolkit.Publish.ViewModels.PublishToAwsDocumentViewModel - Starting a deployment session
2023-01-06 09:54:35,262 [1] DEBUG Amazon.AWSToolkit.Publish.ViewModels.PublishToAwsDocumentViewModel - Deployment session started
2023-01-06 09:54:35,737 [180] DEBUG Amazon.AWSToolkit.Publish.ViewModels.PublishToAwsDocumentViewModel - Publish targets found for XXXXX.Services.Sales: 4
2023-01-06 09:54:35,815 [147] DEBUG Amazon.AWSToolkit.Publish.ViewModels.PublishToAwsDocumentViewModel - Republish targets found for XXXXX.Services.Sales: 13
2023-01-06 09:54:46,591 [145] DEBUG Amazon.AWSToolkit.Telemetry.Internal.TelemetryPublisher - Publishing 5 event(s)
2023-01-06 10:06:07,500 [166] DEBUG Amazon.AWSToolkit.Telemetry.Internal.TelemetryPublisher - Publishing 1 event(s)
2023-01-06 10:11:28,360 [151] DEBUG Amazon.AWSToolkit.Telemetry.Internal.TelemetryPublisher - Publishing 1 event(s)

And the output in the deploy tab

Creating Dotnet Publish Zip file...
MSBuild version 17.3.1+2badb37d1 for .NET
Determining projects to restore...
Restored C:\Dev\XXXXX\XXXXX\XXXXX.services.sales\XXXXX.Services.Sales.Json\XXXXX.Services.Sales.Json.csproj (in 395 ms).
Restored C:\Dev\XXXXX\XXXXX\XXXXX.services.sales\XXXXX.Services.Sales.Loggly\XXXXX.Services.Sales.Loggly.csproj (in 395 ms).
Restored C:\Dev\XXXXX\XXXXX\XXXXX.services.sales\XXXXX.Services.Sales.Data\XXXXX.Services.Sales.Data.csproj (in 395 ms).
Restored C:\Dev\XXXXX\XXXXX\XXXXX.services.sales\XXXXX.Services.Sales.Runtime.Caching\XXXXX.Services.Sales.Runtime.Caching.csproj (in 395 ms).
Restored C:\Dev\XXXXX\XXXXX\XXXXX.services.sales\XXXXX.Services.Sales.Core\XXXXX.Services.Sales.Core.csproj (in 395 ms).
Restored C:\Dev\XXXXX\XXXXX\XXXXX.services.sales\XXXXX.Services.Sales.MongoDb\XXXXX.Services.Sales.MongoDb.csproj (in 429 ms).
Restored C:\Dev\XXXXX\XXXXX\XXXXX.services.sales\XXXXX.Services.Sales\XXXXX.Services.Sales.csproj (in 474 ms).
XXXXX.Services.Sales.Core -> C:\Dev\XXXXX\XXXXX\XXXXX.services.sales\XXXXX.Services.Sales.Core\bin\Release\netstandard2.0\XXXXX.Services.Sales.Core.dll
XXXXX.Services.Sales.Loggly -> C:\Dev\XXXXX\XXXXX\XXXXX.services.sales\XXXXX.Services.Sales.Loggly\bin\Release\netstandard2.0\XXXXX.Services.Sales.Loggly.dll
XXXXX.Services.Sales.MongoDb -> C:\Dev\XXXXX\XXXXX\XXXXX.services.sales\XXXXX.Services.Sales.MongoDb\bin\Release\netstandard2.0\XXXXX.Services.Sales.MongoDb.dll
XXXXX.Services.Sales.Data -> C:\Dev\XXXXX\XXXXX\XXXXX.services.sales\XXXXX.Services.Sales.Data\bin\Release\netstandard2.0\XXXXX.Services.Sales.Data.dll
XXXXX.Services.Sales.Json -> C:\Dev\XXXXX\XXXXX\XXXXX.services.sales\XXXXX.Services.Sales.Json\bin\Release\netstandard2.0\XXXXX.Services.Sales.Json.dll
XXXXX.Services.Sales.Runtime.Caching -> C:\Dev\XXXXX\XXXXX\XXXXX.services.sales\XXXXX.Services.Sales.Runtime.Caching\bin\Release\netstandard2.0\XXXXX.Services.Sales.Runtime.Caching.dll
XXXXX.Services.Sales -> C:\Dev\XXXXX\XXXXX\XXXXX.services.sales\XXXXX.Services.Sales\bin\Release\net6.0\XXXXX.Services.Sales.dll
XXXXX.Services.Sales -> C:\Users\alexs\AppData\Local\Temp\121e38dd-6038-4c04-a45f-4764d9fc09ee\

Uploading to S3. (Bucket: elasticbeanstalk-eu-west-1-XXXXX Key: XXXXX.ServicesSales/AWSDeploymentArchive_XXXXX.ServicesSales_v-XXXXX.zip Size: 6151000 bytes)
... Progress: 10%
... Progress: 20%
... Progress: 31%
... Progress: 32%
... Progress: 34%
... Progress: 38%
... Progress: 46%
... Progress: 53%
... Progress: 57%
... Progress: 64%
... Progress: 69%
... Progress: 79%
... Progress: 88%
... Progress: 96%
Creating new application version: v-XXXXX

Getting latest environment event date before update
Updating environment XXXXX-sales-uat-4 to new application version v-XXXXX
Waiting for environment update to complete
06/01/2023 09:55:04 INFO Environment update is starting.
06/01/2023 09:55:11 INFO Updating environment XXXXX-sales-uat-4's configuration settings.
06/01/2023 09:55:46 INFO Deploying new version to instance(s).
06/01/2023 09:55:47 INFO Batch 1: Starting application deployment on instance(s) [i-XXXXX,i-XXXXX].
06/01/2023 09:56:09 INFO Batch 1: Starting application deployment command execution.
06/01/2023 09:56:09 INFO Environment health has transitioned from Ok to Info. Application update in progress (running for 12 seconds).
06/01/2023 09:56:11 INFO Instance deployment found a runtime-dependent .NET Core application in your source bundle.
06/01/2023 09:56:13 INFO Instance deployment completed successfully.
06/01/2023 09:56:14 INFO Batch 1: Completed application deployment command execution.
06/01/2023 09:56:14 INFO Command execution completed on 2 of 5 instances in environment.
06/01/2023 09:56:14 INFO Batch 1: Registering instance(s) with the load balancer and waiting for them to be healthy.
06/01/2023 09:57:09 WARN Environment health has transitioned from Info to Degraded. ELB processes are not healthy on 2 out of 5 instances. Application update in progress on 2 instances. 0 out of 5 instances completed (running for 62 seconds). ELB health is failing or not available for 2 out of 5 instances.
06/01/2023 10:10:16 ERROR Instance id(s) 'i-XXXXX,i-XXXXX' did not pass health check after command execution. Aborting the operation.
06/01/2023 10:10:16 ERROR Failed to deploy application.
06/01/2023 10:10:16 ERROR During an aborted deployment, some instances may have deployed the new application version. To ensure all instances are running the same version, re-deploy the appropriate application version.
06/01/2023 10:11:04 INFO The environment was reverted to the previous configuration setting.
XXXXX-sales-uat-4 could not be published as ASP.NET Core App to Existing AWS Elastic Beanstalk Environment: Failed to update the Elastic Beanstalk environment
XXXXX.Services.Sales failed to publish to AWS.

[alexsaare]

Logs from legacy deploy

2023-01-06 10:19:01,432 [1] INFO Amazon.AwsToolkit.VsSdk.Common.VSWebProjectInfo - EnvDTEProject.FullName lookup yielded 'C:\Dev\XXXXX\XXXXX\XXXXX.services.sales\XXXXX.Services.Sales\XXXXX.Services.Sales.csproj'
2023-01-06 10:19:01,483 [1] INFO Amazon.AWSToolkit.S3FileFetcher - Null/empty hosted files location override
2023-01-06 10:19:01,483 [1] INFO Amazon.AWSToolkit.S3FileFetcher - Loading hosted file 'CloudFormationTemplates/TemplatesManifest.xml' from local path 'C:\Users\alexs\AppData\Local/AWSToolkit/downloadedfiles/CloudFormationTemplates/TemplatesManifest.xml'
2023-01-06 10:20:00,798 [216] INFO Amazon.AWSToolkit.VisualStudio.AWSToolkitPackage - Publishing 'XXXXX.Services.Sales' to Amazon Web Services
2023-01-06 10:20:15,230 [226] INFO Amazon.AWSToolkit.ElasticBeanstalk.Commands.BaseBeanstalkDeployCommand - Publish to AWS Elastic Beanstalk environment 'XXXXX-sales-uat-4' completed successfully
2023-01-06 10:21:29,734 [126] DEBUG Amazon.AWSToolkit.Telemetry.Internal.TelemetryPublisher - Publishing 3 event(s)

[alexsaare]

There's not really much useful info in the logs from what I can see. The output doesn't appear to include the command used to the invoke the deploy tool.

I'll try the command line directly asap. Do both legacy and new versions use the same command line?

I'd highlight again that the deploy artefacts in the packages produced are VERY different. I can raise a support ticket in AWS if it helps? I'd be willing to share the artefacts there but not on here

[ashovlin]

Hi @alexsaare - I've created aws/aws-dotnet-deploy#749 over on the AWS Deploy Tool for .NET CLI repository. The CLI handles the packaging for Beanstalk and powers the experience in Visual Studio, so any change we'll have to make will likely originate in that repository.

We'll review the packaging differences and how we're handling the health checks. If you are able to route a ticket through support to us, the correct location internally is "AWS SDK for .NET" within the "SDKs and Tools" team.

[alexsaare]

Thanks @ashovlin. I created a support case 11835795821 and attached both versions of the deploy package. I had to re-zip the new version using 7Zip to get it under 5MB so I could attach it to the case.

[ashovlin]

Thanks, just heard from the support engineer internally who is routing the case to our queue.

[alexsaare]

Just thought I'd add that in the output console the legacy deploy includes the following

dotnet publish "C:\Dev\XXXXX\XXXXX\XXXXX.services.sales\XXXXX.Services.Sales" --output
"C:\Dev\XXXXX\XXXXX\XXXXX.services.sales\XXXXX.Services.Sales\bin\Release\net6.0\publish" --configuration "Release" --framework "net6.0" --runtime linux-x64 --self-contained false

(Company redacted)

[normj]

@alexsaare I'm struggling to reproduce the issue. Would you mind running the following PowerShell command for each the environment that was created with the legacy wizard and the new wizard? You will need to update the region, profile, beanstalk application name and beanstalk environment name that you have. It will print out all of the Beanstalk option settings so we can compare what is different about the 2 different environemnts.

# If you already have the module installed this step can be removed.
Install-Module -Name AWS.Tools.ElasticBeanstalk -Force 

$settings = (Get-EBConfigurationSetting -Region "us-west-2" -ProfileName "default" -ApplicationName "<beanstalk-app-name>" -EnvironmentName "<beanstalk-env-name>").OptionSettings 

$settings | Where-Object {$_.Value -ne $null} |  Select-Object {$_.Namespace, $_.OptionName, $_.Value}

[alexsaare]

Hi @normj, thanks for taking the time to look into this.

Apologies if I wasn't clear or I've misunderstood something here.

No environment has been created using the new wizard.

I only have existing environments which were created via the aws console. Deploying to these environments works via the legacy wizard however, when using the new wizard, it fails. Looking at the assets created by the 2 different wizards they are very different (see support case created).

I can give you the output of the powershell requested for a environment that works with the legacy wizard but I don't have any environment that was created or works with the new wizard (that's the problem!)

Does that help clarify the issue? Do you still need the powershell output?

[normj]

@alexsaare that does help and I was misunderstanding the situation. If you wouldn't mind running the PS script on the existing environment that would be appreciated.

[alexsaare]

thanks @normj

Output below - company/account info redacted - if you need anything I've redacted I can add it to the support case, just let me know

$.Namespace, $.OptionName, $_.Value

{aws:autoscaling:asg, Availability Zones, Any}
{aws:autoscaling:asg, Cooldown, 360}
{aws:autoscaling:asg, EnableCapacityRebalancing, false}
{aws:autoscaling:asg, MaxSize, 5}
{aws:autoscaling:asg, MinSize, 5}
{aws:autoscaling:launchconfiguration, DisableIMDSv1, false}
{aws:autoscaling:launchconfiguration, EC2KeyName, test}
{aws:autoscaling:launchconfiguration, IamInstanceProfile, XXXX}
{aws:autoscaling:launchconfiguration, ImageId, ami-XXXX}
{aws:autoscaling:launchconfiguration, InstanceType, t3a.small}
{aws:autoscaling:launchconfiguration, MonitoringInterval, 5 minute}
{aws:autoscaling:launchconfiguration, SSHSourceRestriction, tcp,22,22,0.0.0.0/0}
{aws:autoscaling:launchconfiguration, SecurityGroups, sg-XXXX,sg-XXXX,sg-XXXX}
{aws:autoscaling:trigger, BreachDuration, 5}
{aws:autoscaling:trigger, EvaluationPeriods, 1}
{aws:autoscaling:trigger, LowerBreachScaleIncrement, -1}
{aws:autoscaling:trigger, LowerThreshold, 2000000}
{aws:autoscaling:trigger, MeasureName, NetworkOut}
{aws:autoscaling:trigger, Period, 5}
{aws:autoscaling:trigger, Statistic, Average}
{aws:autoscaling:trigger, Unit, Bytes}
{aws:autoscaling:trigger, UpperBreachScaleIncrement, 1}
{aws:autoscaling:trigger, UpperThreshold, 6000000}
{aws:autoscaling:updatepolicy:rollingupdate, MaxBatchSize, 1}
{aws:autoscaling:updatepolicy:rollingupdate, MinInstancesInService, 1}
{aws:autoscaling:updatepolicy:rollingupdate, RollingUpdateEnabled, true}
{aws:autoscaling:updatepolicy:rollingupdate, RollingUpdateType, Health}
{aws:autoscaling:updatepolicy:rollingupdate, Timeout, PT30M}
{aws:cloudformation:template:parameter, AppSource, https://elasticbeanstalk-platform-assets-eu-west-1.s3.eu-west-1.amazonaws.com/stalks/eb_dotnetcore_amazon_linux_2_1.0.1642.0_20230127021049/sampleapp/EBSampleApp-DotNetCore.zip}
{aws:cloudformation:template:parameter, EnvironmentVariables, ASPNETCORE_ENVIRONMENT=uat}
{aws:cloudformation:template:parameter, HooksPkgUrl, https://elasticbeanstalk-platform-assets-eu-west-1.s3.eu-west-1.amazonaws.com/stalks/eb_dotnetcore_amazon_linux_2_1.0.1642.0_20230127021049/lib/hooks.tar.gz}
{aws:cloudformation:template:parameter, InstancePort, 80}
{aws:cloudformation:template:parameter, InstanceTypeFamily, t3a}
{aws:ec2:instances, EnableSpot, false}
{aws:ec2:instances, InstanceTypes, t3a.small}
{aws:ec2:instances, SpotFleetOnDemandAboveBasePercentage, 70}
{aws:ec2:instances, SpotFleetOnDemandBase, 0}
{aws:ec2:instances, SupportedArchitectures, x86_64}
{aws:ec2:vpc, AssociatePublicIpAddress, false}
{aws:ec2:vpc, ELBScheme, public}
{aws:ec2:vpc, ELBSubnets, subnet-XXXX,subnet-XXXX,subnet-XXXX}
{aws:ec2:vpc, Subnets, subnet-XXXX,subnet-XXXX,subnet-XXXX}
{aws:ec2:vpc, VPCId, vpc-XXXX}
{aws:elasticbeanstalk:application:environment, ASPNETCORE_ENVIRONMENT, uat}
{aws:elasticbeanstalk:cloudwatch:logs, DeleteOnTerminate, false}
{aws:elasticbeanstalk:cloudwatch:logs, RetentionInDays, 7}
{aws:elasticbeanstalk:cloudwatch:logs, StreamLogs, false}
{aws:elasticbeanstalk:cloudwatch:logs:health, DeleteOnTerminate, false}
{aws:elasticbeanstalk:cloudwatch:logs:health, HealthStreamingEnabled, false}
{aws:elasticbeanstalk:cloudwatch:logs:health, RetentionInDays, 7}
{aws:elasticbeanstalk:command, BatchSize, 50}
{aws:elasticbeanstalk:command, BatchSizeType, Percentage}
{aws:elasticbeanstalk:command, DeploymentPolicy, Rolling}
{aws:elasticbeanstalk:command, IgnoreHealthCheck, false}
{aws:elasticbeanstalk:command, Timeout, 600}
{aws:elasticbeanstalk:control, DefaultSSHPort, 22}
{aws:elasticbeanstalk:control, LaunchTimeout, 0}
{aws:elasticbeanstalk:control, LaunchType, Migration}
{aws:elasticbeanstalk:control, RollbackLaunchOnFailure, false}
{aws:elasticbeanstalk:environment, EnvironmentType, LoadBalanced}
{aws:elasticbeanstalk:environment, LoadBalancerIsShared, false}
{aws:elasticbeanstalk:environment, LoadBalancerType, application}
{aws:elasticbeanstalk:environment, ServiceRole, arn:aws:iam::XXXX:role/aws-elasticbeanstalk-service-role}
{aws:elasticbeanstalk:environment:process:default, DeregistrationDelay, 20}
{aws:elasticbeanstalk:environment:process:default, HealthCheckInterval, 15}
{aws:elasticbeanstalk:environment:process:default, HealthCheckPath, /aws-health-check}
{aws:elasticbeanstalk:environment:process:default, HealthCheckTimeout, 5}
{aws:elasticbeanstalk:environment:process:default, HealthyThresholdCount, 3}
{aws:elasticbeanstalk:environment:process:default, MatcherHTTPCode, 200}
{aws:elasticbeanstalk:environment:process:default, Port, 80}
{aws:elasticbeanstalk:environment:process:default, Protocol, HTTP}
{aws:elasticbeanstalk:environment:process:default, StickinessEnabled, false}
{aws:elasticbeanstalk:environment:process:default, StickinessLBCookieDuration, 86400}
{aws:elasticbeanstalk:environment:process:default, StickinessType, lb_cookie}
{aws:elasticbeanstalk:environment:process:default, UnhealthyThresholdCount, 5}
{aws:elasticbeanstalk:environment:proxy, ProxyServer, none}
{aws:elasticbeanstalk:healthreporting:system, ConfigDocument, {"Version":1,"CloudWatchMetrics":{"Instance":{"RootFilesystemUtil":null,"CPUIrq":null,"LoadAverage5...
{aws:elasticbeanstalk:healthreporting:system, EnhancedHealthAuthEnabled, false}
{aws:elasticbeanstalk:healthreporting:system, HealthCheckSuccessThreshold, Ok}
{aws:elasticbeanstalk:healthreporting:system, SystemType, enhanced}
{aws:elasticbeanstalk:hostmanager, LogPublicationControl, false}
{aws:elasticbeanstalk:managedactions, ManagedActionsEnabled, true}
{aws:elasticbeanstalk:managedactions, PreferredStartTime, SUN:07:00}
{aws:elasticbeanstalk:managedactions, ServiceRoleForManagedUpdates, arn:aws:iam::XXXX:role/aws-elasticbeanstalk-service-role}
{aws:elasticbeanstalk:managedactions:platformupdate, InstanceRefreshEnabled, false}
{aws:elasticbeanstalk:managedactions:platformupdate, UpdateLevel, minor}
{aws:elasticbeanstalk:monitoring, Automatically Terminate Unhealthy Instances, true}
{aws:elasticbeanstalk:sns:topics, Notification Endpoint, [email protected]}
{aws:elasticbeanstalk:sns:topics, Notification Protocol, email}
{aws:elasticbeanstalk:sns:topics, Notification Topic ARN, arn:aws:sns:eu-west-1:XXXX:ElasticBeanstalkNotifications-Environment-XXXX-sales-uat-3}
{aws:elasticbeanstalk:xray, XRayEnabled, false}
{aws:elbv2:listener:443, DefaultProcess, default}
{aws:elbv2:listener:443, ListenerEnabled, true}
{aws:elbv2:listener:443, Protocol, HTTPS}
{aws:elbv2:listener:443, SSLCertificateArns, arn:aws:acm:eu-west-1:XXXX:certificate/XXXX}
{aws:elbv2:listener:443, SSLPolicy, ELBSecurityPolicy-TLS-1-2-Ext-2018-06}
{aws:elbv2:listener:default, DefaultProcess, default}
{aws:elbv2:listener:default, ListenerEnabled, false}
{aws:elbv2:listener:default, Protocol, HTTP}
{aws:elbv2:loadbalancer, AccessLogsS3Bucket, logs.ireland.XXXX}
{aws:elbv2:loadbalancer, AccessLogsS3Enabled, true}
{aws:elbv2:loadbalancer, AccessLogsS3Prefix, XXXX-sales-uat}
{aws:elbv2:loadbalancer, SecurityGroups, sg-XXXX}
{aws:rds:dbinstance, HasCoupledDatabase, false}

[normj]

Thanks this helps. I created an environment from the console with rolling deployments with 5 instances and I was able to deploy from both the legacy wizard and the new wizard. I see some differences in our environments based your settings above. In particular I have enhanced health enabled and your does not. So it gives me more things to try.

[rahulpnath]

Ran into this issue - I was using the Reverse Proxy set to 'none' to use Kestrel. In this case, I had to make sure that it was running on the correct port - I set ASPNETCORE_URLS to explicitly run it on port 5000 and that fixed it.

In case that helps.