-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump AWS SDK version to version "~>3". #38
Comments
Actually, after making this change locally and testing all of the logstash plugins that use logstash-mixin-aws as a dependency, it appears that upgrading to aws-sdk version "~> 3" is not a breaking change for any of these plugins (that is, all of their tests passed with the upgraded sdk). Therefore it seems safe to simply do a minor version bump in logstash-mixin-aws. Thoughts? |
As mentioned in #39 bumping this dependency version has the side effect of adding ~200 more dependencies and we will defer using v3 of the aws-sdk to our upcoming aws integration plugin (see https://www.elastic.co/blog/logstash-lines-introduce-integration-plugins) where we will be in a better place to only pick the required dependencies. |
@colinsurprenant v3 also brings support for web identity provider, which is a crucial security feature when running on AWS EKS. |
Is there an ETA on the AWS integrations plugin? |
We are actively moving forward with integration plugins but we don't have an ETA. |
Hello @colinsurprenant, A colleague did the aws-sdk upgrade and added the support for AssumeRoleWebIdentityCredentials in a fork: master...coveooss:CLOUDINFRA-2050---logstash-in-EKS Do you want us to submit a pull request? Thanks! |
@JPLachance Sure! Go ahead! Thanks. |
It looks like bumping the AWS SDK version to at least 2.11.345 would introduce support for IAM roles for service accounts (IRSA). That should be an even smaller change to make, but add heaps of value for AWS EKS users. Would you consider this as an interim solution? |
This has been opened for over a year now 😅 is there any chance we can get upgraded aws-sdk gem soonish? As @itssimon pointed out, latest v2 should already support temporary creds. issued via Logstash integration plugins seem great, but it's been over a year and there's only three of them available (seem like that the same ones made available in the original announcement). What's the best course of action that one could take here @colinsurprenant ? |
I tried to get this working with v2 of the ruby SDK and had no success. I don't even see a reference to |
any updates? |
v2 of the SDK doesn't doesn't support web identity credentials through the |
Any updates on this issue to support IRSA? |
I´ve tested with aws sdk v3, by patching mixin locally... The pessimistic version locking in this plugin block´s ervery plugin developer from using the new SDK. So please update or change the dependency to >= 2. |
We´ve a manually patched version in our test envirnonment. Everything works as expected with aws-sdk 3. regards |
@roaksoax : thank you |
Any news on this? |
@andsel @colinsurprenant Should this project be considered abandoned and all other projects should be migrated directly to use the sdk? |
FYI:
|
you can't remove logstash-mixin-aws this way:
Here is currently the Dockerfile:
|
Seems like if you don't remove logstash-mixin-aws it will still install the new preview integration-aws:
|
Please do a
to see the installed sdk version. |
Hey @cdenneen and @christianherweg0807 thanks for your interest in this upgrade, please note that's some effort in upgrading to AWS v3 is also happening at https://github.com/logstash-plugins/logstash-integration-aws/pulls |
sure for this it is a prerelease. This is a real big production issue for us. regards |
@christianherweg0807 we're getting close to getting the aws integration out, so it'd be nice to push a 0.1.0 release to rubygems. Can you hand over the ownership in rubygems.org to |
Sure. I’m today afk. But tomorrow, I’ll handover.
Regards
Christian
Von meinem iPhone gesendet
… Am 06.07.2022 um 11:24 schrieb João Duarte ***@***.***>:
@christianherweg0807 we're getting close to getting the aws integration out, so it'd be nice to push a 0.1.0 release to rubygems. Can you hand over the ownership in rubygems.org to ***@***.*** ?
We can also use a different name if you prefer to keep "logstash-integration-aws" (first come first served :) )
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.
|
@jsvd : Plz confirm the access, so I could remove myself regards |
Confirmed, many thanks! |
With the logstash-integration-aws released which includes aws-sdk-v3 (logstash-plugins/logstash-integration-aws#9), we can close this issue. Logstash 8.4.0 will be released soon, an include the integration plugin by default. |
We have a plugin:
https://github.com/awslabs/logstash-output-amazon_es
which we want to bump the aws-sdk version to "~>3". To avoid any dependency conflicts with other logstash plugins, we would also like to bump the version of aws-sdk used by logstash-mixin-aws. My thinking is that this should be a major version bump, and that each of the logstash plugins that are using "logstash-mixin-aws" as a runtime dependency should upgrade their dependency to "logstash-mixin-aws" with a version bump as well.
I am in the process of developing and testing this change, but wanted to create the issue to track any discussion about this.
The text was updated successfully, but these errors were encountered: