Skip to content
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

SPIKE: Identify the need for AWS Metadata server request #429

Open
jerico opened this issue Aug 19, 2022 · 0 comments
Open

SPIKE: Identify the need for AWS Metadata server request #429

jerico opened this issue Aug 19, 2022 · 0 comments

Comments

@jerico
Copy link
Contributor

jerico commented Aug 19, 2022

Having this code relies on AWS Metadata server being always available. There are instances where an ECS task cannot reach the metadata server which makes the task marked as unhealthy.

$provider = CredentialProvider::defaultProvider();
$credentials = call_user_func( $provider )->wait();

Check if this is critical or can be obtained elsewhere (environment variable) without relying on AWS Metadata server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant