Skip to content

Feature/add signing resources#633

Merged
TOEL2 merged 6 commits intomainfrom
feature/add-signing-resources
Apr 10, 2026
Merged

Feature/add signing resources#633
TOEL2 merged 6 commits intomainfrom
feature/add-signing-resources

Conversation

@TOEL2
Copy link
Copy Markdown
Contributor

@TOEL2 TOEL2 commented Apr 9, 2026

Description

Adds the required code signing resources, tf outputs and creates and attached the relevant policies to be used in the ci/cd workflows in a further pr

Context

This pr must come first before we actually make changes to our workflows that will use these resources to escape a chicken and egg scenario

Type of changes

  • Refactoring (non-breaking change)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would change existing functionality)
  • Bug fix (non-breaking change which fixes an issue)

Checklist

  • I am familiar with the contributing guidelines
  • I have followed the code style of the project
  • I have added tests to cover my changes
  • I have updated the documentation accordingly
  • This PR is a result of pair or mob programming

Sensitive Information Declaration

To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.

  • I confirm that neither PII/PID nor sensitive data are included in this PR and the codebase changes.

@TOEL2 TOEL2 requested a review from a team as a code owner April 9, 2026 11:37
@TOEL2 TOEL2 marked this pull request as draft April 9, 2026 11:39
@TOEL2 TOEL2 marked this pull request as ready for review April 9, 2026 11:41
@TOEL2 TOEL2 closed this Apr 9, 2026
@TOEL2 TOEL2 reopened this Apr 9, 2026
@eddalmond1 eddalmond1 requested a review from Copilot April 9, 2026 12:16
eddalmond1
eddalmond1 previously approved these changes Apr 9, 2026
Copy link
Copy Markdown
Collaborator

@eddalmond1 eddalmond1 left a comment

Choose a reason for hiding this comment

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

All looks good - have hit Copilot review as I've never deployed code signing, so it might flag something specific i don't know about!

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR introduces AWS Lambda code-signing prerequisites (AWS Signer signing profile + Lambda code signing config), exposes the signing profile name via Terraform outputs, and grants GitHub Actions IAM permissions to manage code-signing resources as a precursor to upcoming CI/CD workflow changes.

Changes:

  • Add an AWS Signer signing profile and a Lambda code signing config in the shared Lambda module.
  • Expose the signing profile name as Terraform outputs for consumption by GitHub Actions workflows.
  • Add and attach a new GitHub Actions IAM policy for managing Lambda code signing configs and Signer jobs.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 3 comments.

Show a summary per file
File Description
infrastructure/stacks/iams-developer-roles/locals.tf Adds locals for signing profile name/ARN used by IAM policy resources.
infrastructure/stacks/iams-developer-roles/github_actions_policies.tf Adds a new code_signing_management IAM policy and attaches it to the GitHub Actions role.
infrastructure/stacks/api-layer/lambda.tf Adds a Terraform output for the signing profile name from the Lambda module.
infrastructure/modules/lambda/signing.tf Creates the AWS Signer signing profile and Lambda code signing config resources.
infrastructure/modules/lambda/outputs.tf Exposes the signing profile name from the Lambda module.

Comment thread infrastructure/modules/lambda/signing.tf
Comment thread infrastructure/stacks/iams-developer-roles/locals.tf
Comment on lines +833 to +837
"lambda:ListTags",
"lambda:DeleteFunctionCodeSigningConfig",
"lambda:PutFunctionCodeSigningConfig"
],
Resource = "*"
Copy link

Copilot AI Apr 9, 2026

Choose a reason for hiding this comment

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

This statement allows lambda:PutFunctionCodeSigningConfig / lambda:DeleteFunctionCodeSigningConfig against Resource = "*", which lets GitHub Actions attach/detach code-signing configs on any Lambda in the account. These actions support function ARN scoping; consider splitting them into a separate statement with the same function ARNs already used in aws_iam_policy.lambda_management in this file, keeping Resource="*" only for actions that truly require it (e.g., listing/creating configs).

Copilot uses AI. Check for mistakes.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

This makes sense

eddalmond1
eddalmond1 previously approved these changes Apr 10, 2026
Copy link
Copy Markdown
Collaborator

@eddalmond1 eddalmond1 left a comment

Choose a reason for hiding this comment

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

you still need to remove?

Copy link
Copy Markdown
Collaborator

@eddalmond1 eddalmond1 left a comment

Choose a reason for hiding this comment

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

no, I'm wrong

@TOEL2 TOEL2 merged commit c8dea83 into main Apr 10, 2026
26 checks passed
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.

3 participants