-
Notifications
You must be signed in to change notification settings - Fork 2
First commits #1
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
Conversation
If a user's console access was created too recently then we cannot yet determine inactivity, so we should not disable it.
If a user's access key was created too recently then we cannot yet determine inactivity, so we should not disable it.
I also removed the run_lambda_locally section as it will not be used with this project.
Otherwise we cannot perform arithmetic such as now - login_profile_create, since the latter is timezone-aware.
This package is already available to Lambda functions.
…nsole access In such a case the "PasswordLastUsed" key does not exist for the user.
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.
Looks great! I noted a few thangs in validate_event_data that I think you overlooked.
Co-authored-by: dav3r <david.redmin@trio.dhs.gov>
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.
Please enable the dependabot ignore directives and fix the upstream repository reference in
disable-inactive-iam-users-lambda/.github/dependabot.yml
Lines 22 to 24 in 15fc27e
| # # Managed by cisagov/disable-inactive-iam-users-lambda | |
| # - dependency-name: actions/upload-artifact | |
| # - dependency-name: github/codeql-action |
That reference changing suggests you have not updated your locally installed skeleton extension. Please update with gh extension upgrade --all to ensure you're working with the latest copy.
Also correct repo reference in comment. Co-authored-by: Nick <50747025+mcdonnnj@users.noreply.github.com>
Please see commit 469a51f. |
|
Hi Team, for README.md file section 'How to update Python dependencies' sentence 'More information about the Pipfile format can be found here.' The link from 'here' returns a 404 not found error. |
I created cisagov/skeleton-aws-lambda-python#32 to fix this upstream. |
…Python This is the latest Python runtime we can currently support, given our AWS Terraform provider constraints. Co-authored-by: Dave Redmin <david.redmin@gwe.cisa.dhs.gov>
|
@mcdonnnj - This work is due tomorrow, and you are out of the office, so I am going to assume that you are satisfied with the changes I made in response to your review. |
🗣 Description
This pull request implements the Python code for an AWS Lambda function that will disable users' inactive console and programmatic access.
See also:
💭 Motivation and context
We have a POAM about disabling inactive users in IAM. Partially resolves cisagov/cool-system-internal#143.
🧪 Testing
I applied this module to our COOL Users account without incident.
✅ Pre-approval checklist
✅ Pre-merge checklist
✅ Post-merge checklist