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

Scaling down provisioned concurrency is not working #59

Open
Kunalkatdare opened this issue Jun 25, 2024 · 2 comments
Open

Scaling down provisioned concurrency is not working #59

Kunalkatdare opened this issue Jun 25, 2024 · 2 comments

Comments

@Kunalkatdare
Copy link

Kunalkatdare commented Jun 25, 2024

@claydanford / @flxgn here's my config:

provisionedConcurrency: 1
config:
  enabled: true
  alias: provisioned
  usage: 0.80
  scheduledActions:
    - name: BusinessHours
      schedule: "cron(30 12 ? * 2-6 *)" # Start of business day (UTC)
      action:
        minimum: 1

when I see the lambda provisioned concurrency its is set to 2. Even during periods with no traffic. I've noticed that it doesn't scale down.
How can the minimum be set to 1 as per the config?

Screenshot 2024-06-25 at 1 02 18 PM Screenshot 2024-06-25 at 1 03 12 PM
@Kunalkatdare
Copy link
Author

Any update on this?

@claydanford
Copy link
Contributor

Hi, @Kunalkatdare, I would manually mess with the datapoints on the alarm and see if you can make it come down, maybe less datapoints in the same time. If you have success we can see about getting it in the plugin.

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

No branches or pull requests

2 participants