You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Complete the following or your issue will be deleted (delete me after)
Please complete these steps and check these boxes (by putting an x inside
the brackets) before filing your issue:
I have read and understood this plugin's README
If filing a bug report, I have included my version of node and s3-plugin-webpack
If filing a bug report, I have included which OS (including specific OS
version) I am using.
If filing a bug report, I have included a minimal test case that reproduces
my issue.
I understand this is an open-source project staffed by someone with a job and
that any help I receive is done on free time. I know I am not entitled to anything and will be polite and courteous.
I understand my issue may be closed if it becomes obvious I didn't
actually perform all of these steps or the issue is not with the library itself
Thank you for adhering to this process! This ensures that I can pay attention to issues that are relevant and answer questions faster.
Issue Details
If filing a bug report, please include a list of steps that describe how to
reproduce the bug you are experiencing. Include your config being passed to the S3Plugin.
Issue:
When uploading to s3 the process is slow when credentials are pulled through the IAM Role meta-data that is associated with the ec2 instance.
Steps to reproduce:
Run webpack with the s3-webpack-plugin and attempt to upload to s3 with out providing credentials in either the config file or as an environment variable.
Expected result: uploading of all assets should take the same time when using IAM role or hard coding credentials
Actual results: uploading with the IAM role takes about 4 times as long as hardcoding the Credentials.
The text was updated successfully, but these errors were encountered:
@gracefullee I'm unable to update to 1.0.2 as it has a dependency of webpack4. I've worked around this issue by getting the AWS credentials from the meta data endpoint and placing them in environment variables. the root cause seems to be the AWS STS endpoint
Complete the following or your issue will be deleted (delete me after)
Please complete these steps and check these boxes (by putting an
x
insidethe brackets) before filing your issue:
version) I am using.
my issue.
that any help I receive is done on free time. I know I am not entitled to anything and will be polite and courteous.
actually perform all of these steps or the issue is not with the library itself
Thank you for adhering to this process! This ensures that I can pay attention to issues that are relevant and answer questions faster.
Issue Details
If filing a bug report, please include a list of steps that describe how to
reproduce the bug you are experiencing. Include your config being passed to the
S3Plugin
.Versions used:
os: ubuntu 16.04
node: 8.11.4
npm: 6.4.0
webpack: 3.12.0
s3-webpack-plugin: 1.0.0-rc.0
Issue:
When uploading to s3 the process is slow when credentials are pulled through the IAM Role meta-data that is associated with the ec2 instance.
Steps to reproduce:
Run webpack with the s3-webpack-plugin and attempt to upload to s3 with out providing credentials in either the config file or as an environment variable.
Expected result: uploading of all assets should take the same time when using IAM role or hard coding credentials
Actual results: uploading with the IAM role takes about 4 times as long as hardcoding the Credentials.
The text was updated successfully, but these errors were encountered: