Timeline for AWS Temporary Permission Granting Tool for Account/Service "Firefights"
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 30, 2020 at 19:31 | answer | added | Hakob | timeline score: 0 | |
| Jun 29, 2020 at 0:18 | history | edited | Preston Martin♦ | CC BY-SA 4.0 |
added 255 characters in body
|
| Jun 28, 2020 at 23:46 | history | edited | Preston Martin♦ | CC BY-SA 4.0 |
Removed confusing text
|
| Jun 28, 2020 at 18:15 | history | edited | Preston Martin♦ | CC BY-SA 4.0 |
Error on the abbreviation, added clarity
|
| Jun 28, 2020 at 15:13 | answer | added | Harish KM | timeline score: 1 | |
| Jun 25, 2020 at 4:20 | comment | added | Preston Martin♦ | A or B can be assumed, it doesn't matter. I would like to stick to limiting it to within the AWS ecosystem. | |
| Jun 23, 2020 at 21:54 | comment | added | Woodland | Just to clarify, these developers and sysadmins already have either (a) an IAM User in the same AWS account, but with limited access, or (b) an IAM User in a different AWS account, correct? Also, do you have any existing products with an employee directory? G Suite or Active Directory, for example? This may help identify a third-party tool to integrate with. | |
| Jun 23, 2020 at 20:02 | history | asked | Preston Martin♦ | CC BY-SA 4.0 |