Thanks - exchanging token with apiKeyId solved the issue. Sendgrid works. I have been referring iglu schemas, but focused on Optimizely so there is a token field, unfortunately…
There is also issue with Optimizely config - in docs you do not mention about enabled statement. As far as I understand in Avro all the fields are mandatory. Can we have this fixed in documentation as well?
SQS queue name key in WIKI is sqsQueue whereas IGLU stands sqsQueueName. Of course iglu key name works.
Unfortunately, once I configure S3 bucket, SQS queue and start the process I get flood of errors regarding credentials ((Service: AmazonSQS; Status Code: 403; Error Code: SignatureDoesNotMatch...). The credentials are correct and have all the required privileges (sqs:*). I have tried two regions (eu-west-1 and eu-central-1) and 3 versions of Java (Oracle 8, OJDK 8 and OJDK 7 - this one does not work).
Did you follow Setup Guide precisely and have all same policies and s3:* permissions? I’m asking because we followed this guide and it worked fine. There’s also a more broad guide on AWS docs if you need more details. I think last time I saw SignatureDoesNotMatch was related to not matching regions. Also, what are using Java for? Are you compiling Sauna from the sources? (It was compiled using Oracle JDK 8 and uses some specific for JDK8 stdlib classes).
I have events configured (can see ObjectPut events in queue). I am using my own user, so i have s3:* and sqs:*. Credentials are ok, as I can use my key/secret with aws cli to list bucket and pull the queue (and list queues). The region is OK - now I use Ireland (so eu-west-1).
I tried both: bintray binary and compiled sauna. Neither works. I started playing with Java versions as I had no idea what can be wrong. Java is in fact required to run Scala code as far as I understand (and downgrading version confirms that).
Update: I have tried with Power User privileges and still the same authentication error. Any thoughts?