- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
Hi, Have a look at this question and its answer: https://stackoverflow.com/questions/74177675/aws-cloudformation-events-api-connection
It looks quite similar to your problem. The proposed solution is:
I solved this by adding full API permissions to the role creating the stack but of course I scoped the permissions by the resource to avoid security issues, something like:
effects: "Allow"
actions: [
"events:*",
"secretsmanager:*"
]
resources: [
"arn:aws:secretsmanager:<your region>:<your-account-id>:secret:events!connection/<yoursecretnameprefix>-*"
]
Hi, I had a similar issue and found the root cause by following Shiva's recommendation and looking into the Cloud Trail logs.
I'm posting this as an answer as I believe it may help anyone having issues with the too general 'GeneralServiceException', no matter which resource one is trying to deploy by using CloudFormation.
Go to CloudTrail -> "Event History" and go to "Preferences" -> "Select visible columns" -> enable "Error code". Then filter the list to find the relevant event. If you enter the event and look at the JSON view, you should be able to find a field called "errorMessage", which holds more detailed information as to what have gone wrong.
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 3 Jahren
This answer helped me to partially solve my situation. I was having another issue with providing correct resource name on the policy and to track down correct error I needed to check actual errors in Cloud Trail.
Cloud Trail will help you get to the actual root cause instead of just guessing what the issue might be with GeneralServiceException. On Cloud Trail Event History - I had luck with filtering by User Name and choosing appropriate time frame the error occurred. Also, make sure to enable "Error code" as visible column on the results so you can easily see which event failed.
Hi, thanks for your feedback with additional info. Glad that you solved your problem. If you're now happy with your situation. You can close this question by accepting the answer completed by your own details.