You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: docs/articles/features/Custom Destinations/README.md
+16-16
Original file line number
Diff line number
Diff line change
@@ -96,29 +96,29 @@ Login to API Gateway, expand the menu options icon available in the top right in
96
96
97
97
Provide a Unique Name for the Custom destination. Supported characters are [a-zA-Z0-9-_].
98
98
99
-
99
+
100
100
101
101
### Condition based publishing
102
102
103
103
You can configure conditions based on which API Gateway filters events to publish to a configured destination. That is, only the events that satisfy your conditions are published to the given destination. For example, you can configure a condition to publish the error events of an application, say app1, to a destination; and another condition to publish the error events of another application, app2, to a second destination and so on.
To configure a condition, you can use variables available in the variable framework, and specify a matching value based on which the condition must be validated. You can specify multiple conditions and configure whether the data to be published must satisfy all or any of the given conditions. The use cases in this section explain the process of configuring conditions.
108
108
109
109
#### Conditions:
110
110
111
111
Conditions are completely optional. One can configure multiple conditions and everything will be validated based on the Condition type. In this case, if the application name matches with **'Splunk HEC Application',** only then API Gateway will send the configured events to Splunk.
112
112
113
-
113
+
114
114
115
115
After configuring the condition variable and value click Add.
116
116
117
117
#### Type - External endpoint:
118
118
119
119
Select the Custom destination type as External endpoint and provide the necessary details like URL, Method, SSL, and Timeout.
Select the data that you want to publish to the configured destination.
136
136
137
-
137
+
138
138
139
139
After all the successful configuration click Add to add Custom destination.
140
140
141
141
### Step 3: Create the API and add Custom Destination
142
142
143
143
Login to API Gateway and create a *Petstore* API from the swagger definition URL http://petstore.swagger.io/v2/swagger.json alternatively you can use the existing API which is already available in API Gateway. Edit the API, go to *Policies → Traffic Monitoring →* Add *Log Invocation → Select Splunk HEC under Destination*.
144
144
145
-
145
+
146
146
147
147
After all the configuration click Save and Activate the API.
148
148
@@ -152,7 +152,7 @@ Invoke the API using a REST client like Postman to generate Transactional Event
152
152
153
153
Open Splunk and search for **sourcetype="httpevent",** the splunk search will look like this,
From the search response you can see the Audit log for Activate and Deactivate, and Transactional events published to Splunk.
158
158
@@ -180,7 +180,7 @@ public class APIGatewayEvents implements RequestHandler<Object, String> {
180
180
181
181
To invoke a Lambda function, we need to create a AWS account configuration in the API Gateway Administration section with the Access key ID, Secret access key and Region. This can be created by navigating to Administration → External accounts → AWS configuration. Configure the AWS account details here and use it as an alias in the Custom Destination. API Gateway supports configuration of multiple AWS accounts.
182
182
183
-
183
+
184
184
185
185
Click Add to add the AWS account in API Gateway.
186
186
@@ -192,7 +192,7 @@ Name, Conditions, Request Processing, and Events sections remains same for AWS L
192
192
193
193
Select the Custom destination type as AWS and provide the necessary details like Function Name, Invocation Type, AWS Alias, and Client Configuration.
Login to API Gateway and create a *Petstore* API from the swagger definition URL http://petstore.swagger.io/v2/swagger.json alternatively you can use the existing API which is already available in API Gateway. Edit the API, go to *Policies → Traffic Monitoring →* Add *Log Invocation → Select AWS CD under Destination*.
218
218
219
-
219
+
220
220
221
221
After all the configuration click Save and Activate the API.
222
222
@@ -228,15 +228,15 @@ Open AWS Lambda to check the events. Login to AWS console, then Services → La
228
228
229
229
In the function overview tab Click Monitor → View logs in CloudWatch.
230
230
231
-
231
+
232
232
233
233
This will open a new Cloud Watch tab. In the Log streams select any one of the stream. It will list all the log statement along with the data published from API Gateway.
@@ -250,4 +250,4 @@ This will open a new Cloud Watch tab. In the Log streams select any one of the
250
250
# Learn more
251
251
252
252
- For details on usage of *Invoke webMethods IS* policy in versions 10.2 and above, refer [Invoke webMethods IS policy in API Gateway 10.2](https://iwiki.eur.ad.sag/display/RNDWMGDM/Invoke+webMethods+IS+policy+in+API+Gateway+10.2)
253
-
- For details on AMQP [AMQP 1.0 support in API Gateway](https://iwiki.eur.ad.sag/display/RNDWMGDM/AMQP+1.0+support+in+API+Gateway)
253
+
- For details on AMQP [AMQP 1.0 support in API Gateway](https://iwiki.eur.ad.sag/display/RNDWMGDM/AMQP+1.0+support+in+API+Gateway)
0 commit comments