Amazon Route 53 is AWS’s highly available and scalable cloud Domain Name System (DNS) web service. The design gives developers and businesses an extremely reliable and cost-effective way to route end users to Internet applications. However, many companies will already have hosted their DNS with another party before starting AWS. In this post, we are walking through what you need to do to use Route53 while keeping your current DNS provider.

This post is a part of the NBTL.blog which contains tutorials and blog posts on all cloud providers’ services. …

Are you including external libraries in your Python Lambda with AWS CDK? You’ll be looking to install your dependencies from your requirements.txt. How do you make sure these external libraries are available at runtime for your execution? By using @aws-cdk/AWS-lambda-python.

What can you expect?
We’ll walk through what the requirements.txt is, what the CDK construct AWS-lambda-python is and do a complete 5 step example on how you can use it at the end of this post.

This level 100 post is part of the University Series of the NBTL blog. You can find the original post here.

What is the requirements.txt?

If this isn’t…

AWS EventBridge is an architecture changing tool, and it will transform the way you think about serverless development. It helps you build event-driven applications at scale across AWS, existing systems or SaaS apps. It shifts you’re thinking on how distributed systems work from a pipeline towards an event-based model. If you haven’t read up on what Amazon EventBridge is or what it does, we’ve written a whole post about it here detailing the service.

At the end of this post section

Once you’ve finished this post, you’ll have created an Amazon EventBridge setup that triggers a Lambda based on a specific event. …

Event-based processing

So what does that mean, shifting from a pipeline towards an event-based model? On an abstract level, it is not that complicated.

You’re probably used to seeing diagrams like these. A couple of microservices hang around and rely on each other. You depend on requests to kick your business logic, and it sort of works. However, the pain comes when you’re rapidly developing, and you’re consumers are no longer able to catch up with you. The backlog is building, and backwards compatibility is now a thing you’re developers are mentioning in their 1–1’s with their managers. At the same time…

In this post we are using AWS CDK to build a system that scales up and down based on the amount of messages in the SQS queue. It allows users to do REST-API calls to an Amazon API Gateway endpoint from their applications or computers. This will add a new item to the SQS queue. In turn, this will trigger your task on ECS. After you’re task is finished it will delete the item from the SQS queue which will automatically scale down you’re ECS cluster and task.

Voila, a low cost autoscaling solution for your high intensity compute jobs.

🎓 At the end of this post

…

In this beginner friendly tutorial we are building an Hello World React application that we will deploy to AWS (and the internet) using AWS Amplify. By leveraging AWS Amplify we are allowing ourselves to by-pass the hardships of manually configuring default important web application tools. It doesn’t only allow us to host our web application, but also makes it easy to use tools like storage, databases or API’s. We will only do the deployment in this post, but will build on it for later series.

At the end of the post

• You will have created a new React project
• You will have initialised AWS Amplify
• You…

Whenever you start a new application, you want to focus on the things that matter for you’re business case. In the example of this application, you want to focus on how you’re application looks and feels when people add new habits. You do not want to focus on whatever back-end operation powers that look and feel. Because, harshly put, for 99/100 users it does not matter how you do it.

We will be leveraging AppSync with AWS Amplify to power our application. …

This is by far, consistently, historically, the best step in starting a new project. It’s the moment you set up you’re Github repository and create your project. You’re starting. I’m a runner myself, and although people will make fun of this analogy, it’s the first 2 kilometres of a run. You’re happy you are out there, and there’s no slowing you down.

This is a marathon

If you’re just getting on this train, this is part three of this publication. You can find part one here and part two here.

Baby steps: Github who?

To make sure we’re not skipping any steps. So far…