Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue when adding Lambda destinations in the console #7654

Closed
milestojakovic opened this issue Apr 28, 2020 · 2 comments
Closed

Issue when adding Lambda destinations in the console #7654

milestojakovic opened this issue Apr 28, 2020 · 2 comments
Assignees
Labels
@aws-cdk/aws-lambda Related to AWS Lambda bug This issue is a bug. needs-triage This issue or PR still needs to be triaged.

Comments

@milestojakovic
Copy link

When adding a destination in the console, if a destination already exists for the Async onFailure OR onSuccess and you try to add another destination of the same type and for the same execution status, it silently overwrites the previous one.

After adding the first destination of any execution status (Failure or Success) , the button "+ Add destination" of the same type and status acts like an "update" instead of "add".

This applies to all destination types: SNS topic, SQS queue or Lambda function.


This is 🐛 Bug Report

@milestojakovic milestojakovic added bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. labels Apr 28, 2020
@SomayaB SomayaB added the @aws-cdk/aws-lambda Related to AWS Lambda label Apr 29, 2020
@nija-at
Copy link
Contributor

nija-at commented Apr 29, 2020

Hello -

This repo is tracking issues related to the CDK. We don't own the AWS console experience; you will need to open an issue with AWS support for this.

@nija-at nija-at closed this as completed Apr 29, 2020
@milestojakovic
Copy link
Author

Hi,

Thanks for the update. I opened the ticket with AWS support. They said that this is beyond of the scope which they are able to handle and they are asking me to upgrade to paid support plan. I don't need to paid support plan, and I have workaround for this. This is a bug in AWS console. Is there any chance to forward this issue to developers who own the AWS console experience, so they can test and fix it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
@aws-cdk/aws-lambda Related to AWS Lambda bug This issue is a bug. needs-triage This issue or PR still needs to be triaged.
Projects
None yet
Development

No branches or pull requests

3 participants