Skip to content
This repository was archived by the owner on May 5, 2025. It is now read-only.

Commit d7eede8

Browse files
authored
add cloudwatch screenshot to lambda guide (#217)
1 parent dd3a442 commit d7eede8

File tree

3 files changed

+13
-3
lines changed

3 files changed

+13
-3
lines changed
-117 KB
Loading
108 KB
Loading

docs/guides/creatingatarget.md

Lines changed: 13 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,15 @@ FIELDS:
5959

6060
In addition to be able to interact with AWS you need to have your AWS API keys available. You may specify them in an object manifest but for better security you will want to use a Kubernetes secret.
6161

62-
Create the following object by saving the YAML manifest in a file and using the `kubectl apply` command.
62+
Create a Kubernetes secret called `awscreds` from the command line like so:
63+
64+
```console
65+
kubectl create secret generic awscreds \
66+
--from-literal=access_key_id=<ACCESS_KEY_ID> \
67+
--from-literal=secret_access_key=<SECRET_ACCESS_KEY>
68+
```
69+
70+
Then, create the following object by saving the YAML manifest in a file and using the `kubectl apply` command.
6371

6472
```yaml
6573
apiVersion: targets.triggermesh.io/v1alpha1
@@ -89,7 +97,7 @@ kind: PingSource
8997
metadata:
9098
name: ping-lambda
9199
spec:
92-
data: '{"hello": "triggermesh"}'
100+
data: '{"name": "triggermesh"}'
93101
schedule: '*/1 * * * *'
94102
sink:
95103
ref:
@@ -114,7 +122,9 @@ NAME URL READY REASON AGE
114122
lambda-guide True 3m12s
115123
```
116124

117-
Finally head over to the AWS Lambda console and see the logs of your Lambda. It will show the `{"hello": "triggermesh"}` string in the standard output.
125+
Finally, go to the AWS Lambda console and see the logs of your Lambda function invocation in a CloudWatch log stream like in the screenshot below:
126+
127+
![](../assets/images/logstream-lambda.png)
118128

119129
## More about Targets
120130

0 commit comments

Comments
 (0)