-
Notifications
You must be signed in to change notification settings - Fork 162
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
Security patterns update #171
Security patterns update #171
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/do-e2e-test guardduty deploy |
@aliaksei-ivanou please check the e2e failure:
|
/do-e2e-test guardduty deploy |
Done |
/do-e2e-test guardduty deploy |
1 similar comment
/do-e2e-test guardduty deploy |
GuardDuty blueprint stack did not deploy due to missing secrets. Rerunning with the secret setup. |
/do-e2e-test guardduty deploy |
Getting this issue during synth time:
Is listdetectors the only permission neeed @aliaksei-ivanou ? |
|
@aliaksei-ivanou UpdateDetector is needed at deploy, not synth time, correct? |
I believe so. |
/do-e2e-test guardduty deploy |
/do-e2e-test guardduty destroy |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Issue #, if available:
Description of changes:
guardduty
pattern.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.