Invoking Lambda from CodePipeline Pipeline: Difference between revisions
Jump to navigation
Jump to search
(Created page with "=Internal= * CodePipeline Operations") |
|||
| Line 2: | Line 2: | ||
* [[AWS CodePipeline Operations#Invoking_Lambda_from_CodePipeline_Pipeline|CodePipeline Operations]] | * [[AWS CodePipeline Operations#Invoking_Lambda_from_CodePipeline_Pipeline|CodePipeline Operations]] | ||
* [[AWS_CodePipeline_Concepts#Invoke|CodePipeline Concepts]] | |||
=TO DO= | |||
<font color=darkgray> | |||
* Invoke Lambda as a Pipeline Action | |||
* Create a lambda through console following NOKB. | |||
* At the point of where I can specify the executable, try bash: | |||
** https://docs.aws.amazon.com/en_us/lambda/latest/dg/runtimes-custom.html | |||
** https://aws.amazon.com/blogs/compute/running-executables-in-aws-lambda/ | |||
** https://stackoverflow.com/a/53849964/7817789 | |||
* Add that lambda as a thalarion Invoke action at the build phase. | |||
* Rationalize and NOKB the “InputArtifact” as an S3 folder. | |||
</font> | |||
Latest revision as of 21:55, 18 March 2019
Internal
TO DO
- Invoke Lambda as a Pipeline Action
- Create a lambda through console following NOKB.
- At the point of where I can specify the executable, try bash:
- Add that lambda as a thalarion Invoke action at the build phase.
- Rationalize and NOKB the “InputArtifact” as an S3 folder.