Sked CLI
Configures AWS Scheduled Scaling for Amazon EC2 Auto Scaling based on Tags.
You can Tag your EC2 instances and define in a config file the scaling profiles. The rest is magic…
Installation
$ pip install sked
Usage
sked create [-c=<config_file>] sked delete [-c=<config_file>] sked -h | --help sked --version
Examples
sked create -c my_schedule.yml sked delete -c my_schedule.yml
If you omit the -c parameter, the cli by default tries to use a file called sked.yml.
Configuration file sample
# sked.yml
profiles:
small:
desired_capacity: 5
min_size: 1
max_size: 10
recurrence: 0 7 * * * # every day at 07:00
overnight:
desired_capacity: 0
min_size: 0
recurrence: 15 19 * * MON-FRI # 19:15 from Monday to Friday
auto_scaling_groups:
- filter:
tag:
key: Name
value: SomeTag
schedule:
- profile: small
times:
- start_time: 2018-03-01T00:00:00Z
- start_time: 2018-04-01T00:00:00Z
- filter:
tags:
- tag: {key: Name, value: MyInstanceA}
- tag: {key: Name, value: 'My Instance B'}
schedule:
- profile: small
times:
- start_time: 2018-03-01T00:00:00Z
- start_time: 2018-04-01T00:00:00Z
Additional Note
Sked doesn’t store the state of the applied scheduled action. Everything is based upon the Yaml configuration file.
If you want to use the delete command make sure you didn’t change the Yaml configuration file in the meantime.
For instance, the following workflow will produce an error:
run sked create
change the sked.yml file
run sked delete
Metadata
Release files for sked 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| sked-1.0.0-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for sked-1.0.0-py2.py3-none-any.whl |
Release files / sked-1.0.0-py2.py3-none-any.whl
| Download URL | sked-1.0.0-py2.py3-none-any.whl |
|---|---|
| Size | 7.9 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
2cd639fbfda8220c76ae89879924c7cdadfacf3749ce253cc29dc2a4d7ffebc1
|
|
BLAKE2b-256 checksum How to use checksums |
c41a122b46396b55c24ccf6a7c44f79dc95c8ddf9dec2a04355b1c98b078abf8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for sked 1.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.