fix: add SSM AMI parameter permissions and environment-based naming

[npalm]

This pull request introduces environment-specific configuration improvements and updates IAM policy resources to support new SSM parameters. The main changes focus on making resource naming more flexible and ensuring the Lambda scale-up policy has access to the necessary SSM parameters.

Configuration improvements:

• Updated the al2023_arm64_name local in examples/multi-runner/main.tf to include the environment variable, making AMI name paths environment-specific for better isolation and flexibility.

IAM policy updates:

• Added ${ssm_ami_id_parameter_arn} to the resource list in modules/runners/policies/lambda-scale-up.json, allowing Lambda scale-up operations to access the new SSM parameter for AMI IDs. This solve errors related handling batches

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

[Copilot]

Pull request overview

This PR enhances environment isolation and fixes Lambda scale-up permissions by making AMI parameter paths environment-specific and granting necessary SSM access. These changes prevent errors when the Lambda function handles batches by ensuring it can read the required AMI ID parameters.

Changes:

• Added environment variable to AMI parameter paths for better resource isolation across environments
• Extended Lambda scale-up IAM policy to include SSM AMI ID parameter access

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
modules/runners/policies/lambda-scale-up.json	Grants Lambda scale-up function access to SSM AMI ID parameter
examples/multi-runner/main.tf	Makes AMI parameter path environment-specific for proper isolation

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.