Skip to content

DR: Use it or lose it policy - IAM User Accounts #65

Closed

Description

@sudhara

Overview

We need to document what our Use it or lose it requirements are, so that we can create further issues to get compliance across all our AWS accounts.

Action Items

  • Research current best practices
  • See notes
  • Write up a Recommendation
  • Get approval on recommendation
  • Write Decision record
  • Get approval
  • Add Decision Record to wiki in the appropriate places
    • List under "Link to all the decision records" (resource 1.01)
    • List under "Records" (resource 1.02)
  • Create an issue to write code and implement policy

Resources/Instructions

Template for decision record

This is a record in the [Decision Records on Solutions Adopted](https://github.com/hackforla/website/wiki/Decision-Records-on-Solutions-Adopted).

#### Issue 
#### Problem Statement
#### Potential Solution
#### Feasibility Determination

notes

There are some accounts where the person logs in infrequently but must maintain their account, no matter what. Make sure recommendation accommodates those accounts.

Activity

  1. ExperimentsInHonesty commented on Jan 27, 2025

    @ExperimentsInHonesty
    Member

    Please

    • assign size
    • add label ready for prioritization
    • remove label ready for CoP lead
  2. changed the title [-]Use it or lose it policy enablement Decision record[/-] [+]DR: Use it or lose it hosting account policy[/+] on Jan 27, 2025
  3. 5 remaining items

  4. moved this from New Issue Review to Prioritized Backlog in CoP: DevOps: Project Boardon Feb 12, 2025
  5. changed the title [-]DR: Use it or lose it policy[/-] [+]DR: Use it or lose it policy - IAM User Accounts[/+] on Feb 13, 2025
  6. brittanyms commented on Feb 14, 2025

    @brittanyms
    Member

    Hi All,

    Here are my notes and discussion thoughts regarding this issue.

    Criteria:

    1. Inactivity Threshold
    • what time period do we want to use to classify an account as inactive? (120 days ~ 6 months)
    • what about if there are h4la members that step away for a while then come back?
    1. Project Accounts
    • are IAM accounts currently assigned on a project level as well?
    • if so, projects that are no longer active should be deactivated
  7. self-assigned this
    on Feb 27, 2025
  8. moved this from Prioritized Backlog to In progress (actively working) in CoP: DevOps: Project Boardon Feb 27, 2025
  9. ale210 commented on Mar 8, 2025

    @ale210
    Member

    @brittanyms this looks great - can you move this to questions/review status to that we'll see it when we do board review?

  10. moved this from In progress (actively working) to Questions/Review in CoP: DevOps: Project Boardon Mar 12, 2025
  11. ale210 commented on Mar 13, 2025

    @ale210
    Member

    Decision record approved:

    After 6 months of inactivity, IAM users will be removed

  12. moved this from Questions/Review to Done in CoP: DevOps: Project Boardon Mar 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

Relationships

None yet

Development

No branches or pull requests

Issue actions