Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

InvalidParameterValueException: SubnetIds and SecurityIds must coexist or be both empty list.

Open
#72 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
aws, github-actions
Domain
cloud, devops

Research direction

Start by reviewing the GitHub Action v0.1.9 inputs named subnets and securitygroups and how the provided comma-separated values are passed to AWS Lambda. Reproduce the configuration from the issue, then inspect the resulting request or error. Done means valid subnet and security group lists are accepted together, or the documentation clearly shows the supported syntax.

Written by the indexing model from the issue text.

Description

In description of lambda I'm describing parameter like this

- name: default deploy
  uses: appleboy/lambda-action@v0.1.9
  with:
    aws_access_key_id: ${{ secrets.AWS_ACCESS_KEY_ID }}
    aws_secret_access_key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
    function_name: func-1
    source: functions/func-1/main
    memory_size: 128
    timeout: 300
    handler: main
    role: "arn:aws:iam::foo:role/func-1-role"
    runtime: go1.x
    subnets: "subnet-123456,subnet-123465,subnet-423156"
    securitygroups: "sg-asdqwf324234"
    environment: ENVIRONMENT=foo

And I keep receiving error
InvalidParameterValueException InvalidParameterValueException: SubnetIds and SecurityIds must coexist or be both empty list.
I've tried to find example how to describe the subnets and SG but unfortunately didn't find any.

How to properly provide list of subnets and SG's here?

Dominant language
D2
Stars
435
Forks
57
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from appleboy/lambda-action

All issues in appleboy/lambda-action

Similar issues

More Cloud issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.