Automate the posts on Twitter using a AWS Lambda function and PowerShell [English]

A few months ago, I started learning about Amazon Web Services (AWS) because I had the necessity to expand my knowledge of cloud services offers. In addition to this, I follow Amazon´s technical blog and I read about the support for PowerShell Core 6 (I worked a lot with serverless, using Azure Functions) so for that, serverless has a place in my heart nowadays. Well, with the above, I´ll share how to work with AWS, in particular with the serverless solution called Lambda with PowerShell Core.

How will I explain that in detail? By sharing with you an excellent example: A way to send automated blog post on Twitter without “human” interaction.

Setting up a development environment

Before we get started developing PowerShell Core based Lambda functions, let’s set up our dev environment.

First, I recommend you to use Visual Studio Code, because the ISE (Integrated Scripting Environment) doesn’t support PowerShell Core. But, you need to configure a few things before start coding…

Installing PowerShell Extension

Launch the Visual Studio Code app by typing code in your PowerShell session and pressing Ctrl+P to launch Quick Open. In Quick Open, type ext install powershell and hit Enter. The Extensions view opens on the side bar, select the PowerShell extension from Microsoft. So then, click the Install button on PowerShell, after the setup, you´ll see the Install button to Reload. Click that.

After Visual Studio Code has reloaded, you are ready for editing PowerShell files :)

Using PowerShell Core version

Because the objective is to use PowerShell Core, we need to add a new variable to your profile settings file.

Open VSCode and click File, after that click on Preferences and the last step is to select Settings.

Find up in the right corner, a button with two curly brackets ({ and }). Two editor panes will appear. In the right-most pane (user settings), insert the setting bellow:

  "powershell.powerShellExePath": "c:/Program Files/PowerShell/6/pwsh.exe"

The number 6 represents the version of PowerShell (core). Save the settings file and restart VSCode.

Install the .NET Core SDK

Next, we need to install the .NET Core 2.2 SDK, because the Lambda support for PowerShell uses the same .NET Core. The .NET Core SDK is used by PowerShell publishing cmdlets for Lambda to create the Lambda deployment package.

You can find the .NET Core 2.2 SDK here.

Install the PowerShell module AWSLambdaPSCore

The last component we need for the development environment is the AWSLambdaPSCore module, that you can install from the PowerShell Gallery directly, using the following command:

  Install-Module AWSLambdaPSCore -Scope CurrentUser

Additionally, we need to install the AWSPowerShell.NetCore module, for work with other AWS Services.

  Install-Module AWSPowerShell.NetCore

Well, after all changes we’ll continue on the next post, configuring the files on the blog and the AWS S3 service for storing the records (published posts).

Prepare the blog for collecting the data

After all the steps required to set the dev environment, we are ready to start working with the next section: collecting the data. As the section title indicates, the main purpose of this post is sharing how to modify the blog adding a new file to join all the posts info and creating another file that save all the published Tweets.

All posts

First we need to improve the blog, adding a new file called entries.html that centralize all the entries with a specific format (JSON). Store it in the root directory.

The file will show all the posts published, as shown in the image:

entries.html file

History file

We need to have a file that work as history record to save all the previous Tweets published because I don’t like repeating the same post 2 times in a row, for example. The first step is defining what type of info the file will save, for example, the date of the last published tweet and a list of previously published posts, like this:

    "lastTweetedDate": "",
    "tweetedPosts": []

AWS S3 bucket

You need to create a AWS S3 bucket and upload the history file, because you need to access this file each time that the Lambda function run.

Before running any command associated to AWS, I´ll explain a way to set the access to the cloud services from the console. Using the commands provided from Amazon, you have a pair of parameters to set the info related to your credentials:

  • AccessKey
  • SecretAccessKey

How to obtain those values? You need to login to the AWS console ( Under your profile name, select the option: My security credentials. Select the section Access keys (access key ID and secret access key) and click over the button Create New Access Key. The last step is downloading the file with the info or select the Show Access Key option to copy/paste to a secure site (I´ll explain how to use Environment Variables with Lambda to store securely that info).

Now, you can use the following command (you must have installed the AWSPowerShell.NetCore module, previously commented):

  New-S3Bucket -BucketName '\<bucketName\>' -AccessKey '\<accessKey\>' -SecretAccessKey '\<secretAccessKey\>' -PublicReadOnly

Perfect! The following step is upload the history file to the new S3 bucket, using the command:

  Write-S3Object -BucketName $bucketName -File C:\history.json -AccessKey $accessKey -SecretAccessKey $secretAccessKey

Note: I replaced the values with variables (strings) to simplify the syntax.

Well, The last configuration step over the files is grant the public access (read), inside the overview tab, select the button Make public:

Create the Lambda function to publish on Twitter

So, now we need to create the Lambda Function, running the following commmand:

  New-AWSPowerShellLambda -ScriptName "TwitterBlog" -Template Basic

After that, edit the function file running the commands below:

  cd .\TwitterBlog\
  code .\TwitterBlog.ps1

And add the next code to the function file (TwitterBlog.ps1):

  # Define variables and extra info
  $bucketName = "" #Add the Bucket name
  $historyFile = "https://s3.\<AWSregion\>$bucketName/history.json" #Add the correct region
  $blogFeed = "" #Change the URL with the correct file

  # Load history file and blog entries
  $history = Invoke-WebRequest -Uri $historyFile | ConvertFrom-Json
  $feed = Invoke-RestMethod -Uri $blogFeed

  # Get a post from the list of available posts that we haven't already tweeted
  $tweetedUrls = $history.tweetedPosts | Select-Object -ExpandProperty url
  $postsToPublish = $feed.posts.Where({$_.url -notin $tweetedUrls})
  $post = $postsToPublish | Get-Random

  # Hashtags
  $hashtags = ""
  $post.tags | Foreach-Object {
      $hashtags += (' #' + ($_ -replace ' ', ''))
  $hashtags = $hashtags.Trim()

  #Tweet info
  $title = $post.title
  $link = ""+$post.url
  $body = "Blog post: $title`n$link`n$hashtags"

  # Set your OAuth variables and such
  $message = [System.Uri]::EscapeDataString($body)
  $oauth_consumer_key = $env:twitterConsumerKey
  $oauth_consumer_secret = $env:twitterConsumerSecret
  $oauth_token = $env:twitterToken
  $oauth_token_secret = $env:twitterTokenSecret
  $random = New-Object -type Random
  $oauth_nonce = $random.Next()
  $culture = New-Object System.Globalization.CultureInfo("en-US")
  $ts = [System.DateTime]::UtcNow - [System.DateTime]::ParseExact("01/01/1970", "dd/MM/yyyy", $null)
  $oauth_timestamp = [System.Convert]::ToInt64($ts.TotalSeconds).ToString()
  # Build base signature
  $signature = "POST&"
  $signature += [System.Uri]::EscapeDataString("") + "&"
  $signature += [System.Uri]::EscapeDataString("oauth_consumer_key=" + $oauth_consumer_key + "&")
  $signature += [System.Uri]::EscapeDataString("oauth_nonce=" + $oauth_nonce + "&")
  $signature += [System.Uri]::EscapeDataString("oauth_signature_method=HMAC-SHA1&")
  $signature += [System.Uri]::EscapeDataString("oauth_timestamp=" + $oauth_timestamp + "&")
  $signature += [System.Uri]::EscapeDataString("oauth_token=" + $oauth_token + "&")
  $signature += [System.Uri]::EscapeDataString("oauth_version=1.0&")
  $signature += [System.Uri]::EscapeDataString("status=" + $message)
  $signature_key = [System.Uri]::EscapeDataString($oauth_consumer_secret) + "&" + [System.Uri]::EscapeDataString($oauth_token_secret)
  # Convert via SHA1
  $hmacsha1 = new-object System.Security.Cryptography.HMACSHA1
  $hmacsha1.Key = [System.Text.Encoding]::ASCII.GetBytes($signature_key)
  $oauth_signature = [System.Convert]::ToBase64String($hmacsha1.ComputeHash([System.Text.Encoding]::ASCII.GetBytes($signature)))
  # Build OAuth Header
  $oauth_authorization = 'OAuth '
  $oauth_authorization += 'oauth_consumer_key="' + [System.Uri]::EscapeDataString($oauth_consumer_key) + '", '
  $oauth_authorization += 'oauth_nonce="' + [System.Uri]::EscapeDataString($oauth_nonce) + '", '
  $oauth_authorization += 'oauth_signature="' + [System.Uri]::EscapeDataString($oauth_signature) + '", '
  $oauth_authorization += 'oauth_signature_method="HMAC-SHA1", '
  $oauth_authorization += 'oauth_timestamp="' + [System.Uri]::EscapeDataString($oauth_timestamp) + '", '
  $oauth_authorization += 'oauth_token="' + [System.Uri]::EscapeDataString($oauth_token) + '", '
  $oauth_authorization += 'oauth_version="1.0"'
  # Build body
  $post_body = [System.Text.Encoding]::ASCII.GetBytes("status=" + $message)
  # Set basic information for Invoke-RestMethod
  $headers = @{"Authorization" = $oauth_authorization}
  $contenttype = "application/x-www-form-urlencoded"

  #Post a Tweet
  $tweet = Invoke-RestMethod -Method Post -Uri "" -Headers $headers -ContentType $contenttype -Body $post_body
  $tweetJson = $tweet | ConvertTo-Json
  Write-Output "Tweet sent:`n$tweetJson"

  #Save teh info to the history
  $date = (Get-Date).ToUniversalTime().ToString('u')
  $tweetedPost = @{
    url = $post.url
    tweetDate = $date
  $history.lastTweetedDate = $date
  $history.tweetedPosts += $tweetedPost
  Write-S3Object -BucketName $bucketName -Key history.json -AccessKey $env:accessKey -SecretAccessKey $env:secretAccessKey -Content ($history | ConvertTo-Json) -PublicReadOnly

If you pay attention, I defined some environment variables. These are for hiding information about private keys and secrets from AWS access and Twitter API.

Note: To obtain the Twitter’s keys and secrets, access to:

You can read the next document to learn how to use environment variables on AWS services:

Publish the Lambda function

To publish the Lambda function, you can run the command:

  Publish-AWSPowerShellLambda -ScriptPath .\TwitterBlog.ps1 -Name "TwitterBlog" -Region <region>

You need to define a role following the instructions. Only need AWSLambdaEdgeExecutionRole permission.


If you had problems executing the previous command, the alternative way to publish the function is execute the command New-AWSPowerShellLambdaPackage with the following syntax:

  New-AWSPowerShellLambdaPackage -ScriptPath .\TwitterBlog.ps1 -OutputPackage

And upload the file on the AWS Lambda console, specifying the LambdaHandler (appearing on the output from the above command) on the Function Code section.

After that, click on the Save button.

New-AWSPowerShellLambdaPackage example

Trigger: CloudWatch Events

The last step is coming: the function exist and the necessary files too. Let’s set up the CloudWatch schedule event to trigger the Lambda function. To do that, go to the configuration section in the Lambda console and select CloudWatch Events in the configure triggers section.

AWS Lambda function with CloudWatch Events

This opens a new Configure trigger panel to set up the schedule event. We’ll need to set the following fields.

Select the Create a new rule option and define a unique name to identify this rule. Set to Scheduled expression the rule type. The expression identifies the frequency to run the script (this can be expressed in either a Cron expression or a Rate expression). To see our new PowerShell based Lambda function in action, let’s set this value to rate(5 minutes) to have it run every 5 minutes.

And voilà! After a few minutes you can see a tweet published from AWS Lambda function using PowerShell Core.

Tweeet example using AWS Lambda function and PowerShell Core

Little tips…

A short list to check on your blog before start using that!

  1. Fix all the tags: Bacause every tweet use each tag as hashtag, you need to correct every tag to share specific information about your post.
  2. Fix the titles: You must correct all the URLs: If a URL is too long you can set a new URL and redirect from the old with the redirect_from plugin from Jekyll. Another approach is adding a service like to generate a short URL.
  3. Update the content: If you start publishing old posts, you need to work to update all the content of your posts.

Happy scripting!