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
* AWS' SDK concerns for cached credentials should not be handled by the logger as they're handled by the aws sdk
* [Doc] - added a guide for configuring AwsKinesisLogger backend.
* [Doc] - Updated README based on reviews
shared_cache_dict="aws_credentials" -- dict for caching STS and IAM credentials
177
+
}
178
+
```
179
+
180
+
Make sure to also configure the NGINX variables:
181
+
182
+
*`kinesis_aws_account` - the AWS Account where the kinesis stream is configured
183
+
*`kinesis_iam_role` - the role to be assumed in order to send the logs to kinesis
184
+
185
+
>INFO: If you send the logs into the same account where NGINX runs you don't need to configure any STS Credentials, but you can use IAM Credentials.
186
+
187
+
For more information about `AWSSTSCredentials` configuration see [the documentation](https://github.com/adobe-apiplatform/api-gateway-aws#sts-credentials).
188
+
189
+
If you can't use IAM Credentials nor STS Credentials, then you can still send logs to Kinesis by configuring AWS with static `access_key` and `secret`.
190
+
These are not as secure as IAM/STS but are working for non-AWS deployments:
0 commit comments