-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
After update Version 3.187.0 = DynamoDB Error retrieving credentials from the instance profile metadata #2281
Comments
@massimodellarovere I think I know what caused this, and am working on a fix right now. Please stand by |
@massimodellarovere, just merged the fix. Please get the latest then try again and let me know if it's fixed |
@SamRemis This is still an issue with production and affects more services than just DynamoDB, when will this be merged? |
@SamRemis Any idea on the ETA for this one being merged in and released as a tagged version? It's wiped a fair few systems out. |
@jonnycbw @mgilberties I have already merged it, so depending on how you download the release, it should have already been fixed. I will release a tagged version to make sure it propagates faster In case I'm wrong, I could use a larger error message to know for sure what the issue is |
@SamRemis - Nice one. We were installing using composer and it doesn't appear to be pulling the latest changes without the tag. We have manually set our systems to use 3.186.1 for now. This is the error we were getting across numerous instances:
|
@mgilberties Thanks :) that's really helpful! I wonder if this issue is releated only to presigned requests. I will be looking into it more once the issue is definitely clear. I did just release tag 3.187.1, so hopefully everyone should have this fixed now. |
Actually I spoke too soon, it looks like it's taking a bit to update on composer; I'll see what I can do to speed that up. |
There it goes, should be available now for 3.187.1 |
@mgilberties please confirm this is fixed if you get the chance so I can close this issue out |
@SamRemis - I can confirm that we now have v3.187.1 getting picked up and everything is functioning as expected. Thanks for your quick actions and response 🙌 |
Good morning! I hit this issue this morning after rebuilding a Docker image for MediaWiki --
Posting this here in case it helps anyone else. Had me worried there! Super appreciate @massimodellarovere for reporting the issue and the quick fix, @SamRemis. As soon as I saw the release notes I was pretty sure I could revert to an older version, but it's great this has been patched. |
Great :) this should be working for everyone now, but I'll set this issue to closing soon just to give it a few days if anyone runs into it. |
I'm having the same issue with the latestupdate of the package.
|
@RosiersRobin you're sure you're using 3.187.3? The error appears to have been fixed. Can you CURL or ping from your machine? The error you're getting also looks different than the one's above |
@SamRemis Yes, I'm using version 3.187.3 The IP it's willing to go to is that 169.254.169.254 and when I ping it, it won't work, I get |
@RosiersRobin can you ping anything at all? And this is a new behavior? To me it looks like an issue with internet settings on your instance, but it was working before and you haven't changed anything? |
@SamRemis It worked before, now I haven't changed a thing it it doesn't work anymore. When I ping from any other place, same issue occures. When I ping from an remote service like https://www.site24x7.com/ping-test.html it appears to be down too. So I doubt it would have to do with my network. I have some AWS instances running, when I ping from a server to that IP, then It's tuck at the "sending data" ; |
@RosiersRobin I'm not 100% sure but it seems to me that the IP 169.254.169.254 direction is not reachable via Ping but only via HTTP request for retrieve Metadata. In my instance the ping return timeout no response but if i use CURL is OK |
I hit this issue this morning, running There must have been a bug where |
I've just encountered this problem and have been trying to find out exactly why this particular problem affected our code. @SamRemis are you able to provide some context for the reverted change to help debug the issue? Thanks |
@electric it's a bit late where I'm at, but hopefully I'll find time tomorrow to confirm. If I recall correctly, it was exactly what the comment above yours says, a missing colon from the url scheme (https// instead of https://). Can you set "debug" => true on your client constructor and confirm where the request is being sent? |
If that's what it is, please try the "composer update" command recommended above. Please let me know if that doesn't work and I'll make sure to get it taken care of ASAP |
Thanks Sam - to confirm, a composer update did indeed fix the issue. |
|
I current use this environment
aws/aws-sdk-php 3.186.4 AWS SDK for PHP - Use Amazon Web Services in your PH...
aws/aws-sdk-php-laravel 3.6.0 A simple Laravel 5/6/7/8 service provider for includ
laravel/framework v8.53.0 The Laravel Framework.
laravel/nova 3.27.0 A wonderful administration interface for Laravel.
If I execute composer update for upgrade SDK version 3.187.0 receive this. The problem is DynamoDB thatt i use for driver Cache and Session in Laravel. If change Driver from DYNAMODB to FIle.. no reveive error, but if i use dynamodb exception in all pages my application..
If downgrade return all OK
The text was updated successfully, but these errors were encountered: