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

AWS IAM security improvements #24

Open
16 tasks
justinPemberton opened this issue Oct 27, 2022 · 5 comments
Open
16 tasks

AWS IAM security improvements #24

justinPemberton opened this issue Oct 27, 2022 · 5 comments

Comments

@justinPemberton justinPemberton changed the title AWS IMA security AWS IMA security hot fix Oct 27, 2022
@justinPemberton justinPemberton changed the title AWS IMA security hot fix AWS IMA security( hot fix) Oct 27, 2022
@justinPemberton justinPemberton changed the title AWS IMA security( hot fix) AWS IMA security(hot fix) Oct 27, 2022
@JasonEb JasonEb changed the title AWS IMA security(hot fix) AWS IAM security improvements Oct 30, 2022
@JasonEb
Copy link

JasonEb commented Nov 17, 2022

@justinPemberton can you break out Assignee's Instructions to a different issue

@ExperimentsInHonesty
Copy link
Member

Template for child issues

### Overview
We need to figure out Industry Guidance and document what should be in the [name of thing] policy, so that we can create actionable HfLA best practices.

### Action Items
- [ ] Identify and document in a comment who is the authoritative source for guidance (might be multiple places), e.g., AWS, etc.
- [ ] Write up the recommendation in the form of a Decision Record as a draft comment.  Use template on (resource 1.01) and reference the source
- [ ] Add to DevOps team agenda (resource 1.02) for review and approval
- [ ] Add to wiki and link to (resource 1.01 and 1.03)

### Resources/Instructions
#### Used during issue
- 1.01 Decision Records Implemented
- 1.02 https://github.com/hackforla/ops/issues/100
- 1.03 Decision Records 

#### created by issue
2.01 Decision Record for [name of thing]

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Oct 1, 2024

@sudhara all the issues linked to this epic need to have the template as the body of the issue.

@ExperimentsInHonesty
Copy link
Member

@sudhara Please provide update

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures or links* (if necessary): "Add any pictures or links that will help illustrate what you are working on."
  • remember to add links to the top of the issue if they are going to be needed again.

@sudhara
Copy link
Member

sudhara commented Oct 7, 2024

Created issues for team to work on instead of Decision Records. 3 more issues to be created. Will finish it next week.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: In progress (actively working)
Development

No branches or pull requests

4 participants