Skip to content

Conversation

@arielbeckjit
Copy link
Contributor

@arielbeckjit arielbeckjit commented Jun 4, 2025

✨ PR Description

Purpose and impact: This PR introduces a Terraform module for automating AWS integration with JIT security platform, supporting both single account and organization-wide deployments.

Main changes:

  • Implements dual integration types (single account and organization-wide) using CloudFormation stacks
  • Provides multi-region monitoring and US/EU API support
  • Includes comprehensive error handling, input validation, and state token management

@gitstream-cm

This comment has been minimized.

@gitstream-cm
Copy link

gitstream-cm bot commented Jun 4, 2025

🥷 Code experts: no user matched threshold 10

See details

To learn more about /:\ gitStream - Visit our Docs

@arielbeckjit arielbeckjit reopened this Jun 4, 2025
… features, integration types, prerequisites, examples, and error handling.
gitstream-cm[bot]

This comment was marked as resolved.

…eration

- Replaced shell script resource with REST API provider for creating state tokens.
- Updated parameters in CloudFormation stack resources to retrieve tokens from the new REST API resource.
- Configured REST API provider with global headers for authentication.
- Updated Terraform version requirements to include the new REST API provider.
gitstream-cm[bot]

This comment was marked as resolved.

- Introduced example Terraform configurations for integrating AWS organizations and single accounts with Jit.
- Created `organization_integration.tf` and `variables.tf` for organization integration, including necessary variables and module configurations.
- Created `account_integration.tf` and `variables.tf` for single account integration, detailing the required variables and module settings.
- Both examples include configurations for Jit API integration and AWS provider settings.
gitstream-cm[bot]

This comment was marked as resolved.

- Changed resource type from `aws_cloudformation_stack_set` to `aws_cloudformation_stack` for organization integration.
- Removed auto deployment configuration and permission model settings that were previously associated with the StackSet.
- Updated example Terraform configurations to include new capabilities for CloudFormation.
- Added new `terraform.tfvars` files for organization and single account examples, including JIT API credentials and organizational settings.
gitstream-cm[bot]

This comment was marked as resolved.

- Changed `resource_name_prefix` in `organization_integration.tf` to use a variable instead of a hardcoded value.
- Added new variables for `regions_to_monitor`, `aws_region`, and `resource_name_prefix` in `variables.tf` for both organization and single account examples.
- Updated `terraform.tfvars` files to include the new variables and their default values for better configurability.
gitstream-cm[bot]

This comment was marked as resolved.

- Updated README.md to clarify the organization integration process, specifying that it creates a CloudFormation stack with internal StackSets.
- Revised module names in examples for better clarity, changing `jit_aws_integration` to `jit_aws_account_integration`.
- Added detailed explanations for required CloudFormation capabilities for both single account and organization integrations.
- Improved validation notes for parameters and added comprehensive examples for both integration types, ensuring users have clear guidance on usage.
gitstream-cm[bot]

This comment was marked as resolved.

@jitsecurity jitsecurity deleted a comment from coderabbitai bot Jun 8, 2025
@arielbeckjit arielbeckjit merged commit fe3ebb6 into main Jun 8, 2025
11 of 12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants