<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Robert Alexander</title>
    <description>The latest articles on DEV Community by Robert Alexander (@ralexanderphi).</description>
    <link>https://dev.to/ralexanderphi</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F249062%2F9b9c00a2-417e-458a-accc-9d59f71861b7.jpeg</url>
      <title>DEV Community: Robert Alexander</title>
      <link>https://dev.to/ralexanderphi</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/ralexanderphi"/>
    <language>en</language>
    <item>
      <title>A mobile alternative to ChatOps</title>
      <dc:creator>Robert Alexander</dc:creator>
      <pubDate>Wed, 25 Dec 2019 16:33:09 +0000</pubDate>
      <link>https://dev.to/ralexanderphi/a-mobile-alternative-to-chatops-3km3</link>
      <guid>https://dev.to/ralexanderphi/a-mobile-alternative-to-chatops-3km3</guid>
      <description>&lt;p&gt;At my last job we considered implementing ChatOps in our Slack to make deploying, and managing our service lightweight but we ran into some concerns that stalled the effort.&lt;/p&gt;

&lt;p&gt;ChatOps promises to let you perform operations from your mobile devices, making Ops task quick and easy to perform even on the go.&lt;/p&gt;

&lt;p&gt;In this post I discuss an idea that gains some of the benefits, while avoiding some of the challenges of ChatOps.&lt;/p&gt;

&lt;h2&gt;
  
  
  Security of Slack ChatOps
&lt;/h2&gt;

&lt;p&gt;Your chat system isn't a strong security boundary. A ChatOps bot will need to implement security including whitelisting users who can perform actions and determine which actions each user can perform.&lt;/p&gt;

&lt;p&gt;This is redundant as these users probably also have IAM credentials with groups or roles for managing their access, meaning you now have two different authorization systems to manage.&lt;/p&gt;

&lt;h2&gt;
  
  
  Overhead of Setting up ChatOps
&lt;/h2&gt;

&lt;p&gt;We created AWS Lambda functions so engineers could manage the service from the AWS command line by just invoking a function. Adding ChatOps that re-used these functions would be another layer, which depending on how we chose to implement it could be time consuming and distract from core development efforts.&lt;/p&gt;

&lt;h2&gt;
  
  
  An Alternative
&lt;/h2&gt;

&lt;p&gt;What if engineers could invoke Lambda functions directly from an Android app using their existing IAM credentials?&lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.com/ralexander-phi/android-aws-lambda-runner"&gt;AWS Lambda Invoker&lt;/a&gt; is an open source Android App that does exactly that.&lt;/p&gt;

&lt;p&gt;The app comes with a mobile friendly, native JSON editor that aims to reduce the burden of writing JSON function inputs.&lt;/p&gt;

&lt;p&gt;Tweak your Lambda function to log invocations to Slack, and you have a similar audit trail to ChatOps with much lower setup overhead.&lt;/p&gt;

&lt;p&gt;The AWS Console app for Android doesn't support running Lambda functions, so this tool is also a general extension to the AWS experience on Android.&lt;/p&gt;

&lt;p&gt;Try it out:&lt;br&gt;
&lt;a href="https://play.google.com/store/apps/details?id=com.alexsci.android.lambdarunner"&gt;https://play.google.com/store/apps/details?id=com.alexsci.android.lambdarunner&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Learn more here:&lt;br&gt;
&lt;a href="https://alexsci.com/android-apps/aws-lambda-invoker/getting-started.html"&gt;Getting Started&lt;/a&gt;&lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
