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.

Sign up for GitHub

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

Jump to bottom

Functionbeat more granular options for permission when deploying a function and support VPC #9425

Closed
vchan2002 opened this issue Dec 6, 2018 · 1 comment · Fixed by #11779
Closed

Functionbeat more granular options for permission when deploying a function and support VPC #9425

vchan2002 opened this issue Dec 6, 2018 · 1 comment · Fixed by #11779
Assignees
@kvch
Labels
enhancement Functionbeat

Comments

@vchan2002
Copy link

vchan2002 commented Dec 6, 2018 •
edited
Loading

When deploying functionbeat, there needs to be the following flags.

a. subnets for deployment within a VPC
b. specify security groups
c. The IAM role that the cloudformation generates for the lambda will need additional rights that a lambda inside a VPC needs rights to do such things within the lambda accordingly.

I have an elasticsearch cluster that I built that's 100% within a VPC and will stay that way. Right now, I can go ahead and manually put in changes after the lambda is deployed, but i'd imagine this is a requirement.
@ph
Copy link
Contributor

ph commented Dec 12, 2018

Certainly, I am planning to expose the VPC/IAM/Security group at the function level so we can generate then correctly with the cloudformation template.

@ph ph assigned kvch Feb 7, 2019
@ph ph changed the title functionbeat deployment need additional options Functionbeat more granular options for permission when deploying a function Feb 26, 2019
@ph ph changed the title Functionbeat more granular options for permission when deploying a function Functionbeat more granular options for permission when deploying a function and support VPC Mar 15, 2019
@kvch kvch mentioned this issue Apr 12, 2019
Merged
kvch added a commit that referenced this issue Apr 23, 2019
@kvch
New options to configure roles and VPC (#11779)
c5ca01b 
From now on it is possible to configure permissions in `functionbeat.yml` for the deployed lambda function. Two new options are added: `role` and `virtual_private_cloud`.

```yaml
# Execution role of the function.
role: arn:aws:iam::123456789012:role/MyFunction
```
```yaml
# Connect to private resources in an Amazon VPC.
virtual_private_cloud:
  security_group_ids:
    - mySecurityGroup
    - anotherSecurityGroup
  subnet_ids:
    - myUniqueID
```

Note: I don't really like the name `virtual_private_cloud` as it's too long. But naming the option `vpc` seems wrong. Do you have any other suggestions?

Closes #9425
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kvch kvch

Labels
enhancement Functionbeat
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

New options to configure roles and VPC kvch/beats
3 participants
@ph @kvch @vchan2002