Purchased the Apple Watch

Apple has done a nice job with the packaging as usual.  Nice paper, nice protectors, nice unboxing experience.  I recall some earlier unboxing projects we had while I was at Sun Microsystems for one of the lower end workstations.

The watch just worked.  Took it out for a jog while calibrating the fitness application.  Nice.

Now, working to take an earlier hello world application to the watch to verify the toolchain to the hardware.

Location Updates Posted to Kinesis Stream

Well, the service pattern is becoming familiar.  Still pretty much every new line of code requires digging into the documentation; how do I print a date?  compare dates?  use a switch?  set color? convert this ObjectiveC to Swift?  Fun though.

Anyway, now I can run the app and transmit a buffered location update event stream.  A little bit more work and I will be off to AWS Lamba to actually do something with the data.

Federated Login Enhancements

With a little more reading and experimenting I think I've refactored the pattern into a slightly more general solution that covers startup, login and logout states properly (github updated).  Code seems robust enough -- need to test a bit under various network error states.

Next up is to wire in another social provider or two (google+ and twitter).  And then to experiment with identity merge -- how to recognize multiple authenticated userIds and then join them into a single entity.

As of this point, I'm fairly certain the auto-refreshing temporary AWS credentials are loaded and working -- seems ready to use with a sensor stream to Kinesis for example.

As a footnote, my first dabbling in Swift is encouraging.  Yes, some sort of a cross of C, Java, ObjectiveC, Javascript, heck, even Gosu.  I only know enough to be dangerous, so time to read the language spec to see what I'm missing.

Federated Login Working

Well, as expected, it is quite trivial to establish the mapped identity provider callback.  Once a login to the provider completes, our service calls out to establish a login mapping to initialize the Cognito to STS mapping (GetID is the AWS api call).  Then later, as needed, a refreshing token is fetched on the fly by the Cognito credentialsProvider.  Nice.

The git repo for this experiment is here.

AWS Cognito wired in, federating to Amazon login

This is turning out to be a nice exercise.  Been forced to dig deeper into Objective-C to Swift 'porting'.  Anyway, application now federates to Amazon as the initial identity provider.  And I do have Cognito unauthenticated access working in the app.  In this case fetching and displaying an image stored in S3.

Oh, and I also reactivated Developer license so I also now have the app running on real hardware.

Next up, figure out how to take an authentication event callback and wire it into the CognitoCredentialsProvider.  This page seems to indicate how.  It feels like a lot of this is done under the hood in the CredentialsProvider.  But I need to see if the source is available to understand what is really going on here.  I haven't yet found a concrete Swift example of having an authenticated session being what is handled by Cognito.  Only pieces...

AWS SDK Loaded, Hello World

I've started a page to detail the steps for getting an Apple Watch sensor flow going through some AWS flow engines.  This is shaping up to be an interesting little project.  The reference page is here.

A bit of walkthrough of the AWS documents and it all looks pretty clear (although I've been using AWS in various forms since the fall of 2007 so the AWS grammar seems familiar).

Initial strategy will be on integrating Cognito with the standard identify providers.  This should get a decent hello world, some temporary credentials, a nice limited IAM role and an object store in place.

Apple Watch

Well, it is time to dig into the details of Apple's latest product.  Dev machines are upgraded, Xcode is refreshed, Swift looks great, Hello Worlds are completed.

So far so good.  Looking forward to live sensor streams offloaded to lambda processors.