aws / aws/aws-app-mesh-examples

[BUG] Invalid request provided: AWS::ElasticLoadBalancingV2::ListenerRule

Open
#420 1 comment 0 reactions 0 assignees View on GitHub
bug
Dominant language
Shell
Stars
868
Forks
384
PR merge metrics
No merged PRs in 30d

Description

_**Important note on security disclosures**: If you think you’ve found a potential security issue, please do not post it in the Issues. Instead, please follow the instructions [here](https://aws.amazon.com/security/vulnerability-reporting/) or [email AWS security directly](mailto:aws-security@amazon.com)._

**Describe the bug**
Followed the instructions in https://github.com/aws/aws-app-mesh-examples/tree/main/walkthroughs/howto-alb. Failed to create the `howto-alb-app` cloudformation stack because of error:
```
Resource handler returned message: "Invalid request provided: AWS::ElasticLoadBalancingV2::ListenerRule Validation exception" (RequestToken: 2e145274-3f83-c38f-cfdc-0645483c40fe, HandlerErrorCode: InvalidRequest)
```

There example here: https://github.com/aws/aws-app-mesh-examples/tree/main/examples/apps/colorapp also failed with the same error.

**Platform**
ECS

**To Reproduce**
1. Export the environment variables as requests.
2. run `./deploy.sh`

**Expected behavior**
The example application is expected to come up and ready to server traffic.

**Config files, and API responses**
If applicable config files and responses from our API.

**Additional context**
Add any other context about the problem here.

Contributor guide

Open the contributing guide

Research direction

Start with walkthroughs/howto-alb and examples/apps/colorapp, then run the referenced ./deploy.sh reproduction using the requested environment variables. Inspect the CloudFormation resources involved in the howto-alb-app stack and the AWS::ElasticLoadBalancingV2::ListenerRule failure. Done means the example stack creates successfully and the application serves traffic.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, shell
Domain
cloud, devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.