-
## Error in v3
**Aws::Sigv4::Errors::MissingCredentialsError** in **SyncSolutionToSearchIndexJob@default**
missing credentials, provide credentials with one of the following options:
- :access_key_…
-
We are loading the vault-ruby gem with Chef. Either Chef directly or some other dependency is also loading aws-sigv4, but version 1.1.3. I believe it is Chef itself loading it, as it is happening on…
-
**Is your feature request related to a problem? Please describe.**
I would like to connect my OpenSearch Dashboards (2.11.1, hosted in AWS ECS using my own container image based on the main dashboa…
-
### What is the feature you are proposing?
Hello,
It would be awesome if we can somehow support SigV4 requests for lambdaliths running Hono, that way we don't have to use API Gateway (and incur …
-
### Description:
I did a migration of files to S3. I tried setup before that and I hitted an error, written below.
My setup:
- Ceph 18.2.2 with RGW and S3 API
- Nginx proxy before RGW endpoint…
-
I would like to use Sigv4 proxy, but not using IRSA, which is already working, but relying on new Pod Identity.
Seems it needs an upgrade for the SDK to let it work natively
-
### What is the problem?
If a role is passed to `EdgeFunction` created in a stack located outside of `us-east-1` it will result in a cyclic dependency error.
### Reproduction Steps
try to deploy th…
-
Currently the SDK is not able to do SigV4 signing of streaming request bodies for async clients.
-
I just realized this crate has a new release `v0.11` but when I tried to compile my existing code based on `v0.10.4`, it failed with
```rust
error[E0432]: unresolved imports `scratchstack_aws_signat…
-
### Is your feature request related to a problem?
Official AWS SDK has a size of 37 MB and AsyncAWS only 1,4 MB
### What solution would you like?
Allow to use also the SigV4 logic from AsyncAWS…