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

CAMEL-9210 accessKey and secretKey are optional #1415

Closed
wants to merge 3 commits into from

Conversation

onderson
Copy link
Contributor

these options are optional now, if not provided, AWS SDK handles them

…tional

accessKey and secretKey options for CloudWatch is now optional
and AWS Java SDK handles those keys unless they are not provided in URI.
…is now optional

csfix -> accessKey and secretKey options for CloudWatch is now optional
and AWS Java SDK handles those keys unless they are not provided in URI.
accessKey and secretKey options are optional now
@davsclaus
Copy link
Contributor

Thanks for the PR it has been merged. Do you mind closing this?

@onderson onderson closed this Jan 21, 2017
@onderson
Copy link
Contributor Author

happy to hear that. thanks

@onderson onderson deleted the CAMEL-9210 branch January 21, 2017 18:43
@ThomasDemande
Copy link

This seems to break working (dynamic) endpoints that provided accessKey and secretKey as endpoint params, giving this error message:

org.apache.camel.ResolveEndpointFailedException: Failed to resolve endpoint: aws-s3://bucket?accessKey=ABDCEFG&fileName=xxx.csv&secretKey=RAWSECRETKEY) due to: AmazonS3Client must be specified

Is this the intended behavior?

@davsclaus
Copy link
Contributor

Hi @ThomasDemande yeah it looks like it may be optional. So you are welcome to log a JIRA and provide a PR with a fix to remove that constrain in the S3Component

@dwsjax
Copy link

dwsjax commented Jul 21, 2017

Please restore my booter I was hacked

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