I am not sure about AWS credentials, but, in general, you can use task.opts
config value to pass any java level settings, which will be passed to each
container jvm.
On Tue, Dec 8, 2015 at 9:57 AM, Gordon Tai wrote:
> Hi,
>
> Is there any convenient way to pass custom Java system properties to S
You should also prefix the names of the API keys with "sensitive.". This will
mask the values when the config is logged and in the AM UI.
On 12/09/2015 01:19 AM, Yi Pan wrote:
Hi, Gordon,
Try to use --config X.Y.Z=value from the command line to run run-job.sh
On Tue, Dec 8, 2015 at 5:57 PM, G
Hi, Gordon,
Try to use --config X.Y.Z=value from the command line to run run-job.sh
On Tue, Dec 8, 2015 at 5:57 PM, Gordon Tai wrote:
> Hi Rad,
>
> Our Samza jobs run on on-premiere clusters, on top of YARN and Kafka. So
> IAM roles won't be an option either.
>
> BR,
>
> On 9 December 2015 at 0
Hi Rad,
Our Samza jobs run on on-premiere clusters, on top of YARN and Kafka. So
IAM roles won't be an option either.
BR,
On 9 December 2015 at 04:09, Rad Gruchalski wrote:
> Gordon,
>
> If your tasks run on EC2, you should use IAM roles.
> https://www.youtube.com/watch?v=XuRM4Id6uDY
>
>
>
>
>
Gordon,
If your tasks run on EC2, you should use IAM roles.
https://www.youtube.com/watch?v=XuRM4Id6uDY
Kind regards,
Radek Gruchalski
ra...@gruchalski.com (mailto:ra...@gruchalski.com)
(mailto:ra...@gruchalski.com)
de.linkedin.com/in/radgruchalski/ (http://de.linkedin.com/in/radgruc
