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

Built in code signing as part of module to support prepared zips #658

Closed
Fran-Rg opened this issue Jan 27, 2025 · 4 comments
Closed

Built in code signing as part of module to support prepared zips #658

Fran-Rg opened this issue Jan 27, 2025 · 4 comments
Labels

Comments

@Fran-Rg
Copy link
Contributor

Fran-Rg commented Jan 27, 2025

Is your request related to a new offering from AWS?

Is your request related to a problem? Please describe.

To support code signing with this module it's required to pre-zip and upload the file to s3. This causes an issue when we rely on the packaging happening within the module as the zip is produced within the module and can't be signed.

Describe the solution you'd like.

Add a aws_signer_signing_job resource with expected variables:

  • [required] enable code signing
  • [required] signing profile_name
  • [optional] destination s3 prefix otherwise use the same as var.s3_prefix
  • [optional] destination s3 bucket otherwise use the same bucket as var.s3_bucket

Describe alternatives you've considered.

I tried to use the output module.this.s3_object.bucket to sign it and inject it to the s3_existing_package but that creates a looping dependency.

Additional context

Checkov rates code signing as a high finding: https://docs.prismacloud.io/en/enterprise-edition/policy-reference/aws-policies/aws-general-policies/bc-aws-272

@antonbabenko
Copy link
Member

You are right, there is an example of how to do it, but we currently don't have a submodule that can handle it. We may create it in the future.

@Fran-Rg
Copy link
Contributor Author

Fran-Rg commented Jan 29, 2025

@antonbabenko I've raised a PR to support code signing: #660

Copy link

github-actions bot commented Mar 1, 2025

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

@github-actions github-actions bot added the stale label Mar 1, 2025
Copy link

This issue was automatically closed because of stale in 10 days

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants