In this post I show you how to set up HTTPS for an application (REST API) running on AWS Elastic Beanstalk. This post is the last in a serie of three. As described in my previous two post I have performed the first two steps to obtain a SSL certificate for my subdomain and I am ready to use it now in the third and last step:
Recently AWS made the ‘Certificate Manager‘ service available in the Europe region. With this service you will be able to use SSL certificate (for free) with your applications hosted on AWS. The big advantage compared to the solution I described here is that this way I don’t have to put the certificate in my source code or have to copy it to my application. As I described in my previous post I want my Elastic Beanstalk application only to be available via HTTPS. To get this in place I need to take the following steps:
In a previous post I wrote about how to run a Spring Boot application on AWS by using Elastic Beanstalk. I also described earlier how to make your Spring Boot application making use of HTTPS instead of HTTP in combination with BoxFuse. I ended up in that solution to include the necessary SSL certificate in my application sources. Another way to accomplish the SSL connection would be to have the Elastic Load Balancer (ELB) in the Beanstalk Application terminate the SSL for us and let the Spring Boot application just communicate over HTTP with the ELB. This set up might be a very handy (perhaps minimal but sufficient) way to add security to the communication level of the API/web application.
To accomplish this set up I need to take several steps of which I will describe the first one in this post. The steps to perform are:
As said before in this post I will only show how to assign a subdomain to the Beanstalk instance. In my situation the parent domain is registered elsewhere (a provider other than AWS). The parent domain that I have registered is ‘palmapps.nl’. The sub-domain I want to register is ‘test.palmapps.nl’.
Continue reading
In my previous post I showed how to run a Spring Boot application on AWS using AWS Elastic Beanstalk. In that post I mention that it is possible to bypass the default Nginx instance on the EC2 instance and have the Elastic Load Balancer communicating with a custom port on your EC2 instance(s) directly. In this post I show how to achieve that. Continue reading
Although I previously wrote how easy it is to get your Spring Boot application up and running on AWS by using Boxfuse I think it is good idea to have notion of some alternative ways to achieve the same. One of these alternatives is by using AWS Elastic Beanstalk. In this post I will describe the basic configuration to get your Spring Boot application running in the cloud on AWS. After the Elastic Beanstalk is created you will have at least one EC2 instance running on AWS with an Elastic Load Balancer in front of it. Also an Auto Scaling Group is provided and of course some Security Groups. When put in a diagram it looks like this (by the way, the database part will not be used in the example of this post):
I assume you already have an account for AWS. If not, go get your free subscription for the first year (mind the conditions to make sure it stays free). Continue reading
For my current project I will have a REST API set up with Spring Boot (most likely running with BoxFuse). To be able to use the API endpoint the application will check that the incoming request has a valid JWT token provided earlier (by an API service that I trust).
To implement this functionality I want to make use of Spring Security as it fits nicely with Spring Boot. When googling for information about this combination I ran into this site that describes the background information quite nicely but didn’t give me all the necessary sources to get it running. So after some more investigating and trial & error I finally came to a working solution. Note that in my situation I only needed to validate an incoming token, I don’t need to create or supply new tokens. Continue reading
In my last post I showed how easy it was to get your REST API based on Spring Boot framework up and running on AWS with the help of Boxfuse. The next step is making use of SSL for the communication with the API. By using SSL we make sure our data is save during the transport between our REST API server and the API client. To setup SSL for the Spring Boot application you have to perform the following two steps:
A few days ago I started building an iOS app that would be using a REST API to retrieve and store data. This REST API would be a server application that I also have to build. Since I am familiair with Java and Spring I decided to use Spring Boot as framework. To be able to use it with my iPhone it would be nice if I could run it on a server instead of my own development PC, so for this I choose AWS since I know how to use that. The only thing I hadn’t figured out yet was what would be the easiest way to get my Spring Boot application running on an AWS EC2 instance… Continue reading
After submitting my first app for the iPhone to the store I decided it was time to create an app for the Apple Watch. I already had the idea about the game I wanted to create for it but mostly it would be a great exercise for me to see what it takes to built such an app. The game might be known as ‘Simon Says‘.
At first the development of the WatchKit based app went well. Because the layout of the watch and available components are limited compared to the iPhone/iPad it makes creating the screens relatively easy. Since the screen of the watch is small only a few elements can be shown on them. Continue reading
As I mentioned before I am working my way through Coursera’s specialization track ‘iOS App Development with Swift‘ that is given by the university of Toronto. Today I heard I accomplished the third part of the total of four.
I am not sure if I will take the last module as it consists of building a complete app ready to go in the App Store. And as you might already have read: been there, done that🙂
Now it’s time to quite studying and start acting!
