# CDK Lambda Power Tuner
This is simply a CDK wrapper for the SAM/SAR application - [aws-lambda-power-tuning](https://github.com/alexcasalboni/aws-lambda-power-tuning)
> Note this is an alpha module, it needs thoroughly tested before being production recommended
All of the lambda logic is cloned on build from that source repo with only the stepfunction definition being defined in this project.
This enables you to now do this:

## Deploying the state machine
Import it into any CDK stack and then cdk deploy
## Running The Tuner
This is the same as [here](https://github.com/alexcasalboni/aws-lambda-power-tuning#how-to-execute-the-state-machine-web-console)
## Differences from [aws-lambda-power-tuning](https://github.com/alexcasalboni/aws-lambda-power-tuning)
Since this uses AWS CDK to build and deploy the step function, we need to play by the rules of CDK.
The method of integrating Lambda functions as a step into your workflow via ARN has been deprecated by the team. They have chosen to support integrating via function name. For reference see [issue](https://github.com/aws/aws-cdk/issues/7709)
This means that the payloads coming back from the Lambda functions contain an extra abstraction layer of data not present in the SAR application.
To make this work without rewriting the Lambda functions so that I can always pull the latest code on every build I had to introduce adapters between the step function Lambda tasks to strip out this abstraction layer. This is their only purpose

Metadata
Release files for cdk-lambda-powertuner 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| cdk-lambda-powertuner-0.2.0.tar.gz | 478.6 kB | Without provenance | Details for cdk-lambda-powertuner-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cdk_lambda_powertuner-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for cdk_lambda_powertuner-0.2.0-py3-none-any.whl |
Total release size: 956.9 kB
Release files / cdk-lambda-powertuner-0.2.0.tar.gz
| Download URL | cdk-lambda-powertuner-0.2.0.tar.gz |
|---|---|
| Size | 478.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
60f9fdae429616286b0d05cd5e9a9311dd9e7e79ddd7d43981717c38b6080af9
|
|
BLAKE2b-256 checksum How to use checksums |
158dacdda63a926e5ac27830a2f66b71b29582887f06dd773e1282e298e33eb2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.22.0 setuptools/36.2.7 requests-toolbelt/0.9.1 tqdm/4.46.0 CPython/3.6.10
|
Release files / cdk_lambda_powertuner-0.2.0-py3-none-any.whl
| Download URL | cdk_lambda_powertuner-0.2.0-py3-none-any.whl |
|---|---|
| Size | 478.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
01d67ff875227e71aa4afd3b427c9d4588c2f78f9a437aeddff7fffc82947c59
|
|
BLAKE2b-256 checksum How to use checksums |
905a7265f494bc66535757662769015738741108754668f21db2d3fb3440df5b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.22.0 setuptools/36.2.7 requests-toolbelt/0.9.1 tqdm/4.46.0 CPython/3.6.10
|
Security for cdk-lambda-powertuner 0.2.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.