Skip to content

Conversation

@davidhessler
Copy link
Contributor

Description

Adds CLI Flag and propegates that through to the AWS Security Incident Response Stack

Type of change (Choose 1)

  • Bug Fix
  • New Feature: Non-new Integration Target
  • New Feature: New Integration Target
  • Documentation update
  • Security fix

Reason for this change

Brief description of why these changes need to be made.

Related Issue (if applicable)

Link to any related issues

Contributor Task List

  • I have reviewed the Contributing Guideline and Code of Conduct
  • I have performed a self-review of my code
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing tests pass locally with my changes
  • The code coverage difference report check has passed
  • Security considerations have been addressed

New Integration Target Questions

If you are introducing a new integration target, additional scrutiny is applied to ensure a high bar is maintained.
For details on this review visit Pull Request Review Rubric.

How does the components of this integration communicate with each

Provide a brief description or attach an architecture diagram to this PR.

How does the integration authenticated and authorize connections between the integration and the target

Provide a brief description or attach a sequence diagram to this PR.

What kind of compute is used by this integration

  • Lambda
  • ECS Fargate or EKS (Auto Mode or Fargate Workers Only)
  • Other

Other: Provide a brief description or attach an architecture diagram to this PR.

How is state / caching maintained in the integration

No changes to state management were made

How much do you expect this integration to cost

No changes to costs were made

By submitting this pull request, I confirm that my contribution is made under the terms of the MIT No Attribution license

@davidhessler davidhessler requested a review from nshalabh January 23, 2026 18:06
Copy link
Contributor Author

@davidhessler davidhessler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comments by @nshalabh

runtime=aws_lambda.Runtime.PYTHON_3_13,
timeout=Duration.minutes(5),
role=service_now_secret_rotation_handler_role,
runtime=PYTHON_LAMBDA_RUNTIME,
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

issue(blocking): The role is never passed to the lambda function

@nshalabh nshalabh changed the base branch from main to v3/service-now-integration January 23, 2026 21:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant