<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Daniel Conde on Medium]]></title>
        <description><![CDATA[Stories by Daniel Conde on Medium]]></description>
        <link>https://medium.com/@danielconde9?source=rss-d6927da06a80------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Fv4n45BqzKTA846V-bpLAw.jpeg</url>
            <title>Stories by Daniel Conde on Medium</title>
            <link>https://medium.com/@danielconde9?source=rss-d6927da06a80------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 13:54:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@danielconde9/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Using Alexa to trigger builds in TeamCity]]></title>
            <link>https://medium.com/@danielconde9/using-alexa-to-trigger-builds-in-teamcity-830abbbe745d?source=rss-d6927da06a80------2</link>
            <guid isPermaLink="false">https://medium.com/p/830abbbe745d</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[teamcity]]></category>
            <category><![CDATA[alexa-skills]]></category>
            <dc:creator><![CDATA[Daniel Conde]]></dc:creator>
            <pubDate>Sun, 10 Jun 2018 00:00:00 GMT</pubDate>
            <atom:updated>2018-06-10T01:13:17.956Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/756/0*gBeF0FYkbGSbKxN5.jpg" /></figure><p>That’s right, wouldn’t be cool if you could trigger your builds from Alexa? Well, you can now, at least if you’re using TeamCity.</p><p><strong>What you’ll need:</strong></p><p><strong>Go</strong> (https://golang.org/dl/)</p><p><strong>ASK CLI</strong> (https://www.npmjs.com/package/ask-cli)</p><p><strong>ngrok</strong> (https://ngrok.com/download)</p><p>Make sure you install and setup all of that before what comes next.</p><p><strong>Let’s have a look at the following diagram:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*F0dacPmd-IVwsjvf.png" /></figure><p>Note how we’re not using the typical Alexa Skill deployment approach backed by an AWS Lambda. Instead, we’re hosting a local skill server which will be publicly visible on the internet via ngrok. But why!!? Well, the reason is simple, my TeamCity Server is hosted on a private network, neither addressable on the Internet or hosted in a VPC in AWS, so AWS Lambda wasn’t an option. I guess there could be other options to expose your local TeamCity Server, but I just wanted to try this approach instead.</p><p><strong>Okay … how do I set it all up!?</strong></p><p>Ngrok will expose our local skill server to the Internet. Open a terminal and run ngrok http 3000, take a note of the HTTPS Forwarding URL:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/611/0*FmXB2dNbwnFFZCZr.png" /></figure><p>Keep ngrok running, we’ll comeback to it later.</p><p>Next, pull and install the local skill server:</p><p>go get github.com/danielcondemarin/ci-commander/alexa-teamcity</p><p>Open another terminal and go to the project src (Pro Tip: Use tmux):</p><p>cd $GOPATH/src/github.com/danielcondemarin/ci-commander/alexa-teamcity/</p><p>Edit the file skill.json and add your ngrok HTTPS Forwarding URL to apis.custom.endpoint.uri (Leave /echo/teamcity in the path!). Mine looked like:</p><pre>&quot;apis&quot;: {</pre><pre>  &quot;custom&quot;: {</pre><pre>    &quot;endpoint&quot;: {</pre><pre>      &quot;sslCertificateType&quot;: &quot;Wildcard&quot;,</pre><pre>      &quot;uri&quot;: &quot;https://12db3c1b.ngrok.io/echo/teamcity&quot;</pre><pre>    },</pre><pre>   &quot;interfaces&quot;: []</pre><pre>  }</pre><pre>}</pre><p>It’s time now to add your build types to the interaction model. We need this so Alexa can identify them in the user utterances. For example:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/822/0*oRqDcQqOwegX8PzJ.png" /></figure><p>Open models/en-GB.json, go to types[].values[] and add your builds with its synonyms. If you have one of those strange build ids with underscores etc. you can set the “value” with the original build id, then synonyms can be easier to pronounce. For example, this is what my config looks like:</p><pre>&quot;types&quot;: [</pre><pre>  {</pre><pre>   &quot;values&quot;: [</pre><pre>     {</pre><pre>      &quot;name&quot;: {</pre><pre>        &quot;value&quot;: &quot;SuperPoo_Build&quot;,</pre><pre>        &quot;synonyms&quot;: [&quot;superpoo&quot;, &quot;poo&quot;]</pre><pre>      }</pre><pre>    }</pre><pre>  ],</pre><pre>  &quot;name&quot;: &quot;BuildType&quot;</pre><p>We’re nearly there now! If you haven’t already, run ask init and setup your profile etc.</p><p>Then, make sure you’re in the directory alexa-teamcity and deploy the skill interaction model:</p><p>ask deploy</p><p>Lastly, grab the alexa skill_id form the file .ask/config and spin up the local skill server. Make sure you replace the env variables with your own values:</p><p>ALEXA_APP_ID=&quot;amzn1.ask.skill.xxxx-xxx&quot; TEAMCITY_URL=&quot;http://127.0.0.1:8111&quot; TEAMCITY_USER=&quot;user&quot; TEAMCITY_PASS=&quot;pwd&quot; $GOPATH/bin/alexa-teamcity</p><p>If you’ve reached this point without issues, here is a quick demo of what you should be able to do!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F274291984%3Fapp_id%3D122963&amp;dntp=1&amp;url=https%3A%2F%2Fvimeo.com%2F274291984&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F706295141_1280.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="1920" height="1110" frameborder="0" scrolling="no"><a href="https://medium.com/media/8cca6cf2998378a2b8ffde24e2955fbb/href">https://medium.com/media/8cca6cf2998378a2b8ffde24e2955fbb/href</a></iframe><p><strong>Final Notes</strong></p><p>Apart from the learning involved in setting it all up, there is no reason why you couldn’t use this with an amazon echo and bring your CI to a whole new level of fun in the office!</p><p><em>Originally published at </em><a href="https://www.devpanda.me/2018/06/10/Using-Alexa-to-trigger-builds-in-TeamCity/"><em>www.devpanda.me</em></a><em> on June 10, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=830abbbe745d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Alexa Go Local!]]></title>
            <link>https://medium.com/@danielconde9/alexa-go-local-a3311ffe634d?source=rss-d6927da06a80------2</link>
            <guid isPermaLink="false">https://medium.com/p/a3311ffe634d</guid>
            <category><![CDATA[golang]]></category>
            <category><![CDATA[alexa]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[alexa-skills]]></category>
            <dc:creator><![CDATA[Daniel Conde]]></dc:creator>
            <pubDate>Sat, 26 May 2018 00:00:00 GMT</pubDate>
            <atom:updated>2018-05-26T16:25:55.795Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-hdzueePk843OcE6hVn3zA.png" /></figure><p>In the last few days, I’ve been exploring the world of Alexa Development. One of the challenges I’ve found, is that it wasn’t immediately obvious how to run and test your skill locally.</p><p>In this post, I’ll show you how to spin up a skill on localhost, and test it from the alexa developer portal. Ah! you’ve guessed right, we’ll be using Golang!</p><p>First, you need to setup your local skill server, think of it as a Lambda function you’ll host on your machine, therefore much easier to test. Luckily there is a great <a href="https://github.com/mikeflynn/go-alexa/tree/master/skillserver">go pkg</a> out there already for this.</p><p>Let’s create our project and call it <em>Greeter</em>, make sure you replace <em>github.com/danielcondemarin</em> with your own namespace!</p><pre>cd $GOPATH/src/github.com/danielcondemarin/<br>mkdir greeter &amp;&amp; cd “$_”<br>touch main.go</pre><p>Now <em>go get</em> the skill server pkg:</p><pre>go get github.com/mikeflynn/go-alexa/skillserver</pre><p>In your favourite editor, change <em>main.go</em> to:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/36844e3aeaed1e376786ecd6497eadc2/href">https://medium.com/media/36844e3aeaed1e376786ecd6497eadc2/href</a></iframe><p>Now head onto the <a href="https://developer.amazon.com/alexa">developer portal</a> and create the skill:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/539/0*Wbl4GWRBgle0sag9.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Ky6GQ1a5V8YjQeG5.png" /></figure><p>After creating the skill, take a step back, copy the Skill ID on the main dashboard and set <strong>AppID</strong> in <strong>main.go</strong>.</p><p>You can now build the go skill server, and run it. By default will be hosted on <a href="http://localhost:3000/">http://localhost:3000</a></p><p>Next, set an invocation name, just <em>greeter</em> will do. We will also need an <em>intent</em> and <em>intent slot</em> for the person name we want to greet!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6ssSq6FXiTXVQI_z.png" /></figure><p>Notice the name’s slotType is already provided by Amazon, <strong>AMAZON.GB_FIRST_NAME</strong>. You will also want to set the slot required to fulfill the intent, to do that just click on the slot and enable the first toggle. Provide a prompt for the user to fill the slot too.</p><p>Next up, the Skill Endpoint, but before we configure that, go and download <a href="https://ngrok.com/download">ngrok</a>. If you don’t know what ngrok is, it’s basically a way for you to expose on the public internet a local port or service in your machine.</p><p>Run ngrok and set it to forward to port 3000 over http:</p><pre>./ngrok http 3000</pre><p>Copy the HTTPS URL, not HTTP! as Amazon requires a secure connection, go to the developer portal and on the Endpoint section select an HTTPS endpoint and paste the ngrok URL plus the path <strong>/echo/greeter</strong> (Mine was <a href="https://aa60ae80.ngrok.io/echo/greeter">https://aa60ae80.ngrok.io/echo/greeter</a>). Make sure you select <em>“My development endpoint is a subdomain of a domain that has a wildcard certificate …”</em>.</p><p>Click Save Model, Build Model, and we are good to test!</p><p>Here is a screenshot with a few utterances I tried:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/440/0*VUDpyhshiEsWl6xU.png" /></figure><p>That’s the end of the blog post, hope you’ve enjoyed it and feel free to comment below if you have any questions!</p><p><em>Originally published at </em><a href="https://www.devpanda.me/2018/05/26/Alexa-Go-Local/"><em>www.devpanda.me</em></a><em> on May 26, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a3311ffe634d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AWS Route53 — A form of Access Control using Geolocation Routing]]></title>
            <link>https://medium.com/@danielconde9/aws-route53-dns-whitelisting-using-geolocation-routing-36e097a83cce?source=rss-d6927da06a80------2</link>
            <guid isPermaLink="false">https://medium.com/p/36e097a83cce</guid>
            <category><![CDATA[dns]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[route-53]]></category>
            <category><![CDATA[geolocation]]></category>
            <dc:creator><![CDATA[Daniel Conde]]></dc:creator>
            <pubDate>Sat, 07 Oct 2017 00:00:00 GMT</pubDate>
            <atom:updated>2018-05-20T08:52:44.598Z</atom:updated>
            <content:encoded><![CDATA[<p>Assumptions: Basic knowledge of AWS Route53</p><p>DNS can be a powerful tool, more so if you are using AWS Route53 as your provider.</p><p>In this post I will focus on how to use Route53’s <a href="http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy.html#routing-policy-geo">Geolocation routing</a> as a whitelist / blacklist of users originating from around the world.</p><p>So, let’s assume you only want users from the United Kingdom to access your website. This could be because all your customer base and operations are UK based, or maybe your application was DDoS’ed from various countries around the world, and you want to make sure any DNS query issued from this malicious Origin / IP is null routed.</p><p>First, let’s go to Route53 and create our first record set :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/428/0*JJPBmPnkB_YOA9Ic.png" /></figure><p>Please note this will be our default route, which will resolve to the IP Address <a href="https://en.wikipedia.org/wiki/Null_route">0.0.0.0</a>. So, whenever a user attempts to reach your website domain (i.e. mywebsite.somedomain.co.uk) Route53 will resolve that DNS Query to 0.0.0.0, then your machine will attempt to reach the website via the IP 0.0.0.0 which obviously doesn’t exist and will fail.</p><p>Let’s setup now the record for users originating from the UK and assume our webserver will be hosted on a server with IP 54.12.12.12 :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/427/0*_EB0X-RhyqI6C0ql.png" /></figure><p>That should be it, the A records just created along with the domain NS records should be listed in your website Hosted Zone like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1q6VzdJWk0gmuxDN.png" /></figure><p>But how do we test this is working correctly? It should be easy be using dig via your terminal. Just grab one of the nameservers for your domain, listed above, and run the following command :</p><p>./bin/dig/dig @your-nameserver mywebsite.somedomain.co.uk +client=45.63.111.158/24</p><p>Caveat : You will need a <a href="https://www.gsic.uva.es/~jnisigl/dig-edns-client-subnet.html">patched version</a> of dig in order to use the +client option. This option allows you to tell the nameserver the user ip address, which then it uses to return an IP Address from your records, based on the estimated geolocation of the IP Address you passed. This mainly works thanks to the <a href="https://tools.ietf.org/html/rfc7871">client subnet in DNS queries</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*XAFfYzLE_isykOpb.png" /></figure><p>I used the IP Address 45.63.111.158 which is from an American DNS Server I’ve found here <a href="https://public-dns.info/">https://public-dns.info/</a>. Make sure you look again for a different IP since this might change.</p><p>Now, for the UK:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0wj-0vrZA47CrUYg.png" /></figure><p>That’s about it really, hope you found it interesting and give some real use to it.</p><p><em>Originally published at </em><a href="https://www.devpanda.me/2017/10/07/DNS-Blacklist-of-locations-countries-using-AWS-Route53/"><em>www.devpanda.me</em></a><em> on October 7, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=36e097a83cce" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>