I recently posted an article on how to get set up with Datadog’s AWS Integration and successfully received metrics. Today I’ll be working on forwarding over my CloudWatch logs to Datadog.

All of the documentation for this set up is located in the following places:

• https://app.datadoghq.com/logs/onboarding/cloud
• https://docs.datadoghq.com/logs/guide/send-aws-services-logs-with-the-datadog-kinesis-firehose-destination/?tab=kinesisfirehosedeliverystream
• https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs//SubscriptionFilters.html#DestinationKinesisExample

To start, I’ll check to see if any logs exist already.

I start on the Datadog Quick Start page.

I hover over Logs and click Search.

You too can use Datadog to monitor your applications!

The following is my step-by-step experience following the Datadog documentation on how to set up an AWS integration. I recommend reading their docs for the latest up-to-date information, but thought it was worthwhile to share my successful installation!

First I navigated to https://app.datadoghq.com/

Next, I hovered over Integrations on the left and selected “Integrations”.

Tired of stopping and rerunning your Spring Boot MVC project every time you make changes? Skip the entire rebuild with Spring Developer tools!

With a combination of adding spring-boot-devtools, configuring IntelliJ correctly, and installing a browser extension, working on MVC projects has never been easier.

For reference, here is the Spring Docs on enabling the automatic restart. Below is my experience setting it up and trying it out!

Here are 10 Steps to enabling auto-reload for Spring Boot in IntelliJ:

Step 1: Open IntelliJ and Import your Project

For the purpose of this demo, I am importing one of the Spring Guides projects found in Github here. …

Welcome to the Cloud Tidbits publication! This article will demonstrate how to use Terraform v0.12+ to create EFS and mount it to your subnet. A follow-up article will demonstrate how to access the file system from lambda.

Start by ensuring the client machine (i.e., MacBook) is prepared to create AWS resources with Terraform. Review the following article and continue below.

Next, create a new repository and scaffold out the files needed. My repository looks like this. Don’t worry about the terraform.tfstate right now, but create the rest of the files with the simple one-liner below the tree.

Here’s the…

Prerequisite: Python3 installed. Open up your terminal and verify that python is installed:

$ python --versionPython 3.7.8

If python is not recognized, install python from python.org.

Install django like so:

python -m pip install Django

Start a basic django project:

django-admin startproject mysite

Or, if django-admin doesn’t work, you can use:

python -m django startproject mysite

Next I’m going to install postgres on macos — https://www.postgresql.org/download/macosx/ there are a few options, but today I’m installing Postgres.app.

Download PostgresApp from https://postgresapp.com/downloads.html:

Drop it into your applications:

Yikes, you’ve set up Amazon Cognito for your awesome new website and now you see this error:

You have chosen to have Cognito send emails on your behalf. Best practices suggest that customers send emails through Amazon SES for production User Pools due to a daily email limit. Learn more about email best practices.

A quick search will let you know that the hard limit is 50 emails. “Crap”, you’re thinking. I don’t know how to fix this.

Well you’re in luck, cause it’s pretty easy, and here’s how to do it!

Part 1: Verify an Email Address in SES

Step 1: Log in to the AWS Console…

As an AWS believer (thus far), I have been saddened by the latest issues I’ve run into when attempting to deploy an Angular application on a static S3 website. I’ve been hosting my personal website (built with React) on S3 with success, and because I’ve recently been diversifying my front-end knowledge by learning Angular, the next logical move was to deploy an Angular site to S3 to the world to see.

I downloaded the Angular CLI, built a (sweet) application, and tried to upload it to S3 — but got the white screen of death! …