AWS wrangling, round 3: simplest possible, manually-configured static website

Our DevOps instructor Dan asked us to host a static HelloWorld page in S3.  After last week’s over-scoped tutorial, I started digging around in the properties of an S3 bucket, and discovered it was staring me in the face (if only I’d stared back).

Somehow I’d foolishly gotten into the groove of AWS tutorials and assumed if I found official content, that must be the most well-constructed approach based on the minimal needs of most of their audience, so I didn’t question the complexity and poorly-constructed lessons until long after I was committed to see it through.  [Thankfully I was able to figure out at least one successful path through those vagaries, or else I’d probably still be stubborn-through-seething and trying to debug the black box that are IAM policy attachments.]

Starting Small: S3 bucket and nothing else

Create Bucket

Modify the bucket-level Permissions

  • Select the new bucket and click Properties
  • Expand the Permissions section, click Add more permissions
  • In the Grantee selector, choose Everyone
  • check the List checkbox
  • click Save

Enable static website hosting

  • In the Bucket Properties, expand the Static Website Hosting section
  • Select enable website hosting
  • In the Index Document textbox, enter your favoured homepage name (e.g. index.html)
  •  click Save

Upload your web content

  • In the Actions button (on the top-left of the page), select Upload
  • Click Add files, select a simple HTML file, and click Start Upload
    • If you don’t have a suitable HTML file, copy the following to a text editor on your computer and save it (e.g. as helloworld.html)
      <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
      <html>
      <head>
       <title>Hello, World!</title>
       <style>
       body {
       color: #ffffff;
       background-color: #0188cc;
       font-family: Arial, sans-serif; 
       font-size:14px;
       }
       </style>
      </head>
      <body>
       

      Hello, World!

      You have successfully uploaded a static web page to AWS S3

      </body> </html>

Modify the content-level Permissions

  • Select the newly-uploaded file, then click Properties
  • expand the Permissions section and click Add more permissions
  • In the Grantee selector, choose Everyone
  • check the Open/Download checkbox and click Save

Now to confirm that your web page is available to web users, find the Link in the Properties for the file and click it – here’s my test file:

Screenshot 2017-01-15 10.26.39.png

If you’ve done everything correctly, you should see something like this:

Screenshot 2017-01-15 10.31.01.png

If one or more of the Permissions aren’t correct, you’ll see this (or at least, that’s what I’m getting in Chrome):

Screenshot 2017-01-15 10.29.47.png

 

Advertisements

How Do I Know What Success Looks Like?

I was asked recently what I do to ensure my team knows what success looks like.  I generally start with a clear definition of done, then factor usage and satisfaction into my evaluation of success-via-customers.

Evaluation Schema

Having a clear idea of what “done” looks like means having crisp answers to questions like:

  • Who am I building for?
    • Building for “everyone” usually means it doesn’t work well for anyone
  • What problem is it fixing for them?
    • I normally evaluate problems-to-solve based on the new actions or decisions the user can take *with* the solution that they can’t take *without* it
  • Does this deliver more business value than other work we’re considering?
    • Delivering value we can believe in is great, and obviously we ought to have a sense that this has higher value than the competing items on our backlog

What About The Rest?

My backlog of “ideas” is a place where I often leave things to bake.  Until I have a clear picture in my mind who will benefit from this (and just as importantly, who will not), and until I can articulate how this makes the user’s life measurably better, I won’t pull an idea into the near-term roadmap let alone start breaking it down for iteration prioritization.

In my experience there are lots of great ideas people have that they’ll bring to whoever they believe is the authority for “getting shit into the product”.  Engineers, sales, customers – all have ideas they think should get done.  One time my Principal Engineer spent an hour talking me through a hyper-normalized data model enhancement for my product.  Another time, I heard loudly from many customers that they wanted us to support their use of MongoDB with a specific development platform.

I thanked them for their feedback, and I earnestly spent time thinking about the implications – how do I know there’s a clear value prop for this work?

  • Is there one specific user role/usage model that this obviously supports?
  • Would it make users’ lives demonstrably better in accomplishing their business goals & workflows with the product as they currently use it?
  • Would the engineering effort support/complement other changes that we were planning to make?
  • Was this a dealbreaker for any user/customer, and not merely an annoyance or a “that’s something we *should* do”?
  • Is this something that addresses a gap/need right now – not just “good engineering that should become useful in the future”?  (There’s lots of cool things that would be fun to work on – one time I sat through a day-long engineering wish list session – but we’re lucky if we can carve out a minor portion of the team’s capacity away from the things that will help right now.)

If I don’t get at least a flash of sweat and “heat” that this is worth pursuing (I didn’t with the examples mentioned), then these things go on the backlog and they wait.  Usually the important items will come back up, again and again.  (Sometimes the unimportant things too.)  When they resurface, I test them against product strategy, currently-prioritized (and sized) roadmap and our prioritization scoring model, and I look for evidence that shows me this new idea beats something we’re already planning on doing.

If I have a strong impression that I can say “yes” to some or all of these, then it also usually comes along with a number of assumptions I’m willing to test, and effort I’m willing to put in to articulate the results this needs to deliver [usually in a phased approach].

Delivery

At that point we switch into execution and refinement mode – while we’ve already had some roughing-out discussions with engineering and design, this is where backlog grooming hammers out the questions and unknowns that bring us to a state where (a) the delivery team is confident what they’re meant to create and (b) estimates fall within a narrow range of guesses [i.e. we’re not hearing “could take a day, could take a week” – that’s a code smell].

Along the way I’m always emphasizing what result the user wants to see – because shit happens, surprises arise, priorities shift, the delivery team needs a solid defender of the result we’re going to deliver for the customer.  That doesn’t mean don’t flex on the details, or don’t change priorities as market conditions change, but it does mean providing a consistent voice that shines through the clutter and confusion of all the details, questions and opinions that inevitably arise as the feature/enhancement/story gets closer to delivery.

It also means making sure that your “voice of the customer” is actually informed by the customer, so as you’re developing definition of Done, mockups, prototypes and alpha/beta versions, I’ve made a point of taking the opportunity where it exists to pull in a customer or three for a usability test, or a customer proxy (TSE, consultant, success advocate) to give me their feedback, reaction and thinking in response to whatever deliverables we have available.

The most important part of putting in this effort to listen, though, is learning and adapting to the feedback.  It doesn’t mean rip-sawing in response to any contrary input, but it does mean absorbing it and making sure you’re not being pig-headed about the up-front ideas you generated that are more than likely wrong in small or big ways.  One of my colleagues has articulated this as Presumptive Design, whereby your up-front presumptions are going to be wrong, and the best thing you can do is to put those ideas in front of customers, users, proxies as fast and frequently as possible to find out how wrong you are.

Evaluating Success

Up front and along the way, I develop a sense of what success will look like when it’s out there, and that usually takes the form of quantity and quality – useage of the feature, and satisfaction with the feature.  Getting instrumentation of the feature in place is a brilliant but low-fidelity way of understanding whether it was deemed useful – if numbers and ratios are high in the first week and then steadily drop off the longer folks use it, that’s a signal to investigate more deeply.  The user satisfaction side – post-hoc surveys, customer calls – to get a sense of NPS-like confidence and “recommendability” are higher-fidelity means of validating how it’s actually impacting real humans.

This time, success: Flask-on-AWS tutorial (with advanced use of virtualenv)

Last time I tried this, I ended up semi-deliberately choosing to use Python 3 for a tutorial (I didn’t realize quickly enough) was built around Python 2.

After cleaning up my experiment I remembered that the default python on my MacBook was still python 2.7.10, which gave me the idea I might be able to re-run that tutorial with all-Python 2 dependencies.  Or so it seemed.

Strangely, the first step both went better and no better than last time:

Mac4Mike:flask-aws-tutorial mike$ virtualenv flask-aws
Using base prefix '/usr/local/Cellar/python3/3.5.2_3/Frameworks/Python.framework/Versions/3.5'
New python executable in /Users/mike/code/flask-aws-tutorial/flask-aws/bin/python3.5
Also creating executable in /Users/mike/code/flask-aws-tutorial/flask-aws/bin/python
Installing setuptools, pip, wheel...done.

Yes it didn’t throw any errors, but no it didn’t use the base Python 2 that I’d hoped.  Somehow the fact that I’ve installed Python 3 on my system is still getting picked up by virtualenv, so I needed to dig further into how virtualenv can be used to truly insulate from Python 3.

Found a decent article here that gave me hope, and even though they punted to using the virtualenvwrapper scripts, it still clued me in to the virtualenv parameter “-p”, so this seemed to work like a charm:

Mac4Mike:flask-aws-tutorial mike$ virtualenv flask-aws -p /usr/bin/python
Running virtualenv with interpreter /usr/bin/python
New python executable in /Users/mike/code/flask-aws-tutorial/flask-aws/bin/python
Installing setuptools, pip, wheel...done.

This time?  The requirements install worked like a charm:

Successfully installed Flask-0.10.1 Flask-SQLAlchemy-2.0 Flask-WTF-0.10.3 Jinja2-2.7.3 MarkupSafe-0.23 PyMySQL-0.6.3 SQLAlchemy-0.9.8 WTForms-2.0.1 Werkzeug-0.9.6 argparse-1.2.1 boto-2.28.0 itsdangerous-0.24 newrelic-2.74.0.54

Then (since I still had all the config in place), I ran pip install awsebcli and skipped all the way to the bottom of the tutorial and tried eb deploy:

INFO: Deploying new version to instance(s).                         
ERROR: Your requirements.txt is invalid. Snapshot your logs for details.
ERROR: [Instance: i-01b45c4d01c070555] Command failed on instance. Return code: 1 Output: (TRUNCATED)...)
  File "/usr/lib64/python2.7/subprocess.py", line 541, in check_call
    raise CalledProcessError(retcode, cmd)
CalledProcessError: Command '/opt/python/run/venv/bin/pip install -r /opt/python/ondeck/app/requirements.txt' returned non-zero exit status 1. 
Hook /opt/elasticbeanstalk/hooks/appdeploy/pre/03deploy.py failed. For more detail, check /var/log/eb-activity.log using console or EB CLI.
INFO: Command execution completed on all instances. Summary: [Successful: 0, Failed: 1].
ERROR: Unsuccessful command execution on instance id(s) 'i-01b45c4d01c070555'. Aborting the operation.
ERROR: Failed to deploy application.

This kept barfing over and over until I remembered that the target environment was still configured for Python 3.4.  Fortunately or not, you can’t change major versions of the platform – so back to eb init I go (with the -i parameter to re-initialize).

This time around?  The command eb deploy worked like a charm.

Lesson: be *very* explicit about your Python versions when messing with someone else’s code.  [Duh.]

Manifesto

Get to know Mike. The Tech Ambassador, the Empathizer, the hairy Dog Fur-bearer, the comics-inspired Dude and the Hatter.

Something I’m tired of doing to myself, every time I want to write my thoughts out to the world around me, is deciding halfway through a rant or a confessional, that the people I’m aiming at probably wouldn’t give the full rat’s ass to make it through the ninth paragraph.

So starting in 2015 I’m mustering the nerve to just write what I need to get out of my multi-layered (fractured?) brain. Is there anyone out there reading what I write (other than the Google index spider and the parasitic content-scrapers [hi there bastards!])? Fucked if I know. And as far as this pressurized-anxiety release valve is concerned, don’t really matter. Nope, it don’t.

Got something to say to me? Take your best shot (and not your laziest one). I’ll give as good (but not as bad) as I get.

2012 Manifesto

Here is my manifesto for 2012: to move in a more creative career direction, I will think more visually by working more visually.

I will become my own style of visual designer, user experience engineer, crackpot scientist of ideas. This will happen by spending more of my working day more visually – drawing, whiteboarding, illustrating the noise in my head. I will create sketches, wireframes, storyboards, flow charts, ideographs, gonzo business apps, unintelligible charts and results that scare the shit out of me.

How can I automatically crosspost/publish Google Reader "shares" to Google+, Facebook or Twitter?

Google Reader is such a great, simple way as a desktop user to keep up with dozens or hundreds of RSS feeds – but even moreso, to be able to selectively share and comment on the blog articles in those feeds with your friends and with various “external” social services (Facebook, Twitter, Delicious, Stumbleupon, and lots of even-more-ancient-sounding services).

What *isn’t* Google Reader great at?
  • sharing your favourite articles (with commentary) via a purely mobile experience
  • sharing those same faves with your burgeoning Google+ circles
Mobile: the Google Reader team have added a tiny number of widgets for sharing to the mobile web experience. Other third-party iPhone apps have done a better job of integrating to the foreign services’ APIs, but it’s not like they voraciously keep up or try to stay ahead of the next wave. [Reeder’s been good to me but hardly stellar – the FB integration works, but I guess I’d rather it just added this as a background operation for all sharing rather than me having to take the time and extra steps to bother sharing outside of the native Google Reader/Buzz feed.]
G+: And what the heck is with Google leaving no clues as to the status of Google Buzz, and whether/when they’ll move operations (like automatic posting of your Google Reader “sharing” activity to the Buzz feed) over to a native G+ implementation? After a year on Buzz, I accumulated no further “organic” growth of friends & followers than the folks that I originally scraped together on day one. I’m seeing a little better “natural uptick” of followers on G+, but still nothing like I see on Twitter – though to be fair, I think if I got new bot followers every time I posted to the Public feed on G+, I’d probably lose my mind.
So what’s up with Google Reader? Has it effectively been zombied, or starved of any reasonable squad of hungry developers and Product Owners? Or is this still a feature with a future? Hell, if I have to find yet *another* place to host my RSS feeds I’m probably gonna lose my mind. And that’s likely the reason why Google has starved the Reader team of any serious developer resources: there’s no competition left. Google is the last place to offer free, voluminous RSS scraping and it shows in their complacency. Up to the rest of us to kludge together some pretty Rube Goldbergian workflows to make it worth reading/sharing on Reader in the first place.
So what does *your* Goldberg machine look like?
So far, the furthest I’ve gotten is to ensure that Sharing & Notes are still working from the mobile Reader and the Reeder iPhone app. Nothing in the Reader “Send To” list even seems to hint at a G+ interaction – and I haven’t gotten creative enough yet to figure out how to make a ‘custom link’ post to one place, that will eventually (and richly – i.e. without cryptically condensing and stripping good content off the original shares) end up on FB, G+ & Twitter without me having to take a half-dozen manual steps at each post. Last I looked, Friendfeed does a cryptic job; does Seesmic have anything to offer here? Any new services from Silicon Valley that I should be looking into?

How can I publish GoodReads reviews on Google+, Facebook or Twitter?

Hey all my geeky friends: I’m trying to figure out the most automated way (least number of extra steps) to enable all the reviews I write on GoodReads to show up on my Google+ and/or Facebook streams. I realize that with the amount of effort I’ve put into these reviews over the last year or two, I might as well be getting more value out of the postings than from the dozen or so ‘friends’ I’ve accumulated on GoodReads itself.

Has anyone come up with a good scheme for pulling or pushing GoodReads reviews to their social walls? I’m currently experimenting with ways to pull or push reviews using this blog as a staging ground – see if I can find a way to pull or push from Blogger to G+ or Facebook.


Right now, I do all my reviewing from the GoodReads iPhone app, and based on my previous experiments, it looks like all of the automation is still just “semi-automated”, and only really available from a desktop browser. That is, GoodReads will certainly cache the locations and credentials necessary to cross-post from GR to the ‘foreign’ services; however, it still requires me to (a) fire up my laptop, (b) browse to GR, (c) find the review I just published via GR on iPhone, (d) click the checkbox for the ‘foreign service’ to which I want to post, and (e) push the review to that service.

My ideal behaviour: I’d LOVE GoodReads if they could enable the following scenario:
  • I write a review on GoodReads via the iPhone app
  • I switch the “shelf” from “currently-reading” to “read”
  • GoodReads publishes the review automatically (with no further actions on my part) to all previously-configured social platforms: Blogger, Facebook, Twitter (and in the near future, Google+)
Who do I have to get drunk to make this happen?