-
See https://github.com/snowplow/snowplow/issues/1263
-
When the provider is run in an EKS pod, with the IAM assume role setup, that works with the AWS provider too, the provider cannot use the assumed role, the following error is dropped:
`* failed to lo…
-
Once I start recording using jibri, the system automatically gives moderator role to random participant ! (Sometimes)
Even I have disabled auto owner!
And tried to enable guest and join with jwt
(…
-
In a brand new org, you'll receive these errors:
```
Error: Unable to verify whether custom org role organizations/0000000000/roles/foobar_gcveNetworkAdmin already exists and must be undeleted: Er…
-
### Description
This ticket is in regards to the AWS announcement https://aws.amazon.com/blogs/security/announcing-an-update-to-iam-role-trust-policy-behavior/
The issue basically is that the ne…
-
- IAM role for Lambda to access S3
- Fraud Detector
- CloudWatch
- Allow Lambda to access S3 buckets for transaction data and results
- Fraud Detector
Add all necessary roles
-
**Describe the bug**
I encountered an error when running terraform command to install RADLab UI following the doc https://googlecloudplatform.github.io/rad-lab/docs/rad-lab-ui/ui_installation/infrast…
-
GCP Secret Manager Integration: Unable to authenticate the cluster secret store using GCP Workload Identity
**Error message:** Warning InvalidProviderConfig 11m (x71 over 14h) cluster-secret-st…
-
Our AWS Org settings require all new IAM roles to have a specific Permission Boundary applied. Any role create command where the role does not have this permission boundary will fail.
I have follow…
-
### Describe the feature
I am trying to modify the defaultPolicy in the IAM.Role construct. The default policy is a great feature - I don't have to worry too much about base permissions when instan…