1 Answer
- Newest
- Most votes
- Most comments
0
The problem stemmed from adding a second website project to the visual studio solution. The second website did not have any permissions or used SSM. I noticed the wrong appsetting.json in the S2 bucket, by removing the second web project and redeploying everything is back to working. It would be great if the Visual Studio publish Lambda function realized it did not know how to handle the situation and offered a warning instead of populating the bucket with broken configuraitons.
answered 3 years ago
Relevant content
- asked 3 months ago
- asked 9 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago