Closed dblock closed 1 year ago
Closed via #220
The rootcause is still unclear but the reason of error has been found. See log: dataprepper-2.0.2-install.txt
When install without any security settings, aws-sdk-s3 as a transient dependency to aws-sdk is being installed as 1.134.0. https://github.com/opensearch-project/logstash-output-opensearch/blob/main/logstash-output-opensearch.gemspec#L48
When switching to any of the security settings, it will then fall back to 1.131.0, as shown in the log above.
Since aws-sdk-s3 never being signed, when running with -P HighSecurity
, it will fail the run due to high security requires all packages to be signed, no matter having signature or not.
[opensearch@fa202d0638a5 logstash-output-opensearch]$ gem install logstash-output-opensearch-2.0.2-java.gem -P HighSecurity
Fetching aws-sdk-s3-1.131.0.gem
ERROR: While executing gem ... (Gem::Security::Exception)
unsigned gems are not allowed by the High Security policy
No Sig Files in the aws-sdk-s3 gem
[opensearch@fa202d0638a5 logstash-output-opensearch]$ ll testsdk/
total 676
-rw-rw-r-- 1 opensearch opensearch 344064 Aug 24 23:09 aws-sdk-s3-1.134.0.gem
-r--r--r-- 1 opensearch opensearch 300 Aug 24 18:10 checksums.yaml.gz
-r--r--r-- 1 opensearch opensearch 339253 Aug 24 18:10 data.tar.gz
-r--r--r-- 1 opensearch opensearch 1358 Aug 24 18:10 metadata.gz
The solution is to follow this order:
It is possible to directly install with MediumSecurity to start with tho.
Thanks.
Describe the bug
https://github.com/opensearch-project/logstash-output-opensearch/actions/runs/5954433808/job/16150938024