In this blog, I will explain how I passed the AWS Certified Developer – Associate exam. This might help you in your journey to pass the exam. Enjoy! 1. Why? First of all, why did I want to pass the exam? It all started when I wrote a blog how to create a deployment pipeline in AWS. CI/CD tooling is one of my interests and I wanted to know how this was done in the cloud. Before that, I also experimented with some of the Google Cloud services. So, I got this idea that I wanted to learn more about one of these cloud offerings. After some investigation, it was clear to me that AWS is still the major cloud vendor although Google Cloud and Azure are on the rise. However, I made the decision that it was wise to learn more about AWS services. Note, that I did not have any hands-on experience in cloud development before and certainly not with AWS. 2. Which Course? I wanted to learn by means of a course and searched for the best AWS Certified Developer – Associate courses. Quickly it appeared to me that the Ultimate AWS Certified Solutions Architect Associate 2022 by Stephane Maarek was the one I had to follow. At that time, it was the 2021 version though, but I will elaborate more on the timeline and time spent later on. The course covers most of the topics you need to know for the exam and you will have a good base of knowledge about 30 AWS services. The course is a mixture of explaining the services and hands-on exercises. It also comes with approximately 850 slides which you can use for studying and with one practice exam. The hands-on exercises are not documented and Stephane executes them very quickly. I used to execute the identical steps he was doing in my AWS account, but this meant that I had to play the video for some seconds, stop it, execute in in my environment, continue the video, stop it, etc. In the meanwhile, I also made notes in order that I was able to execute the exercise again when I wanted to without watching the video again. The course is regularly updated. This is a good thing, because the course is continuously improving and in line with what you need to know for the exam. I encountered one major update where some chapters were shifted. That was a bit confusing at first. Most of the time, only minor updates are done. 3. Hands-on After taking the course, I realized that I also needed some hands-on experience with AWS services. So, I made a list of topics which I wanted to explore more and I wrote nine blogs about it. My initial list was longer, but due to available time, I had to cut it off. How to Create an AWS EC2 VM How to Create an AWS ALB and ASG How to Deploy a Spring Boot App on AWS ECS Cluster How to Deploy a Spring Boot App on AWS Fargate How to Create an AWS CloudFormation Fargate Template AWS Lambda Versions and Aliases Explained By Example How to Secure AWS API Gateway With Cognito User Pool An Introduction to AWS Serverless Application Model An Introduction to AWS Step Functions Writing these blogs really helped me in understanding these topics much better. Also, while studying, I noticed that I did not have to put much effort in these topics anymore. 4. Timeline How much effort did it took me? To be honest, more than I initially expected. I started in March 2021 and my initial plan was to take the exam the latest in December 2021. In the end, I passed the exam in July 2022. In the paragraphs below, I will try to quantify this a bit more. Finishing the course took me about 60 hours in the period of time between March and April 2021. I was granted to spend this time during working hours. The duration of the course in Udemy indicates that it contains 27 hours of video, but as already said before, Stephane executes the hands-on exercises very quickly. Taking notes and trying to execute the same steps as he does, took me more than double the time of the length of the videos. In the meanwhile, I also tried to recap the slides of videos I had seen. But remember, these are 850 slides. It took me initially 10 to 12 hours. After the course, I started to write some blogs. I wrote nine blogs and for each blog it takes me between 8 to 16 hours to finish it. Approximately it took me 9 times 12 hours (as an average), which is 108 hours. I wrote the last blog in March 2022. I did not hurry with this. I wrote the blogs in the period of time between June 2021 and March 2022. In the meanwhile, due to some personal circumstances, I had to put the AWS exam on hold for awhile in order to give some priority to my personal life. This was solved somewhere mid June and I made up my mind to start studying again for the AWS exam. My goal was to take the exam before I would go on holiday end of July 2022. I recapped the slides 4 times, each time it took on average 10 hours. The course contains a practice exam which ressembles the real exam quite well. Taking the exam took me about an hour. After the exam, you can see how you score on certain topics and the answers are extensively documented. Checking the answers costed me between 30 and 60 minutes. I wanted to practice more exams and therefore I used the Practice Exams | AWS Certified Developer Associate 2022 by Stephane Maarek and Abhishek Singh. Practicing these exams gave me good feedback on which topics I knew and which ones needed more attention. I also started to read some topics in the AWS documentation in order to understand them better. I passed the first two exams with a score in the seventies, the others (after studying the slides again and reading some extra documentation) between 80% and 90%. For the last exams, there was not one topic with a bad score. That was the moment I knew I was ready for the exam. To conclude with, it took me about 250 hours to prepare for the exam. 5. Exam I scheduled the online exam at PSI. The exam took me about 2 hours to finish. The questions were more elaborate than the practice exams. There is just more text to read and you need to read the text carefully in order to be able to pick the correct answer. When you think more than one answer is correct, you probably missed something in the text. Do keep in mind that you will get some questions which are not covered in the course. In my case, there were three to four questions which did not ring a bell. Sometimes you will be able to guess the answer, sometimes you will not have a clue. So ensure you have passed the practice exams with a decent margin above the required 720 passing score. I was hoping to get the result immediately, but that was not the case. I received the good news the day after I took the exam :-) 6. Costs The course, practice exams and the exam itself are not free. Sometimes you can get a discount at Udemy. The course for example is about 125 euro, but I could purchase it for 12 euro. Nonetheless, when you need to pay the full price, the total amount you need to spend is a bit less than 400 euro. The AWS account itself is free. Almost all hands-on exercises can be executed within the free tier. 7. Conclusion Some words of wisdom to conclude with. I underestimated the time it would cost me to prepare for this exam. The AWS services are not extremely difficult to understand, it is the amount of services you need to know which makes it difficult. This was definitely one of the more challenging exams I took during my professional life.

In this article, explore more about the integration between MicroStream, Jakarta EE, and MicroProfile, thanks to CDI.

Microservices architecture has established itself as a quasi-standard and is deployed in many projects. How do they influence the lifecycle of an application?

In these example scenarios, learn more about acceptance tests in Java, and why you should learn them right now.

This open-source platform solves the long-running process problem in a modern microservices environment by replacing Sagas with workflows.

In part 2 of an experiment with FerretDB and CockroachDB, restore a MongoDB collection into CockroachDB via FerretDB, and expand on previous learnings.

14 First Principles to Help Your Scrum Team Succeed

Learn how to connect a self-hosted SuperTokens core to a MySQL or PostgreSQL database with or without Docker.

Are you thinking about adapting a microservices architecture? Here are three steps to prepare your code base.

Many alternatives are available to access a pod from outside the cluster. The Gateway API is the new kid on the block and the subject of this post.

Running a database server is an expensive undertaking requiring a lot of effort. Managed cloud database services offer several options, but which one is best?

Modern web applications increasingly need to handle realtime data with an event-driven architecture. Serverless WebSockets are the solution.

Fact: the state of pull requests is broken and we finally have the data to prove it. In this interview, learn about a proposed solution: continuous merge.

We will take a Kubernetes feature and break its implementation to understand how it interacts with Kubernetes system components.

Want to know about microservices and how they can be implemented with node.js? Go through and know everything about microservices in detail.

A Routine Exercise or Mission-critical for a Team’s Success?

When you want to experiment with Ansible, you will need to setup a test environment. In this blog, you will create a test environment containing one controller and two target machines. This will give you a good setup for experimenting with Ansible without breaking a real machine. 1. Introduction With Ansible, you can automate repetitive IT tasks and because it is automated, it will also prevent you from making mistakes. Especially when you have to configure several similar environments. The other main advantage is that the configuration is maintained in files and therefore extremely suitable for adding the configuration to version control (e.g. Git). However, in every learning path you need to be able to experiment in order to make mistakes and to learn. In this blog, you will setup an Ansible controller machine and two target machines running in VirtualBox. The Ansible Controller will be the machine where to run the Ansible playbooks from and the target machines will be where tasks can be executed. The test setup looks as follows. The sources for this post are available at GitHub. 2. Setup Ansible Controller The machines will be created as Virtual Machines (VMs) and as virtualization platform you will use VirtualBox. Install VirtualBox on your host machine when it is not yet installed. You can create a machine from scratch and install an operating system (OS) yourself, but for testing purposes, it is easier to retrieve an already installed image from osboxes.org. Navigate to VM IMAGES – VirtualBox Images and choose for Ubuntu, the OS you will use for setting up the environment. Download the Ubuntu 20.04.4 Focal Fossa version. After downloading the file, unzip it. Create in VirtualBox a new machine via Machine – New… Fill in the following and click the Next button: Name: Controller Type: Linux Version: Ubuntu (64-bit) Set the memory size to 4 GB and click the Next button. Choose for Use an existing virtual hard disk file and select the .vdi file you downloaded and unzipped. Click the Create button. Select the VM in VirtualBox and click the Settings button. Navigate to Network in the left menu and change in the Adapter_1 tab Attached to into Bridged Adapter. Click the OK button. Start the VM and login with username osboxes and password osboxes.org. After successful login, verify whether you have internet connection (just try to search something in the browser in the VM). Run the software updates in Ubuntu and also update libraries in a terminal window. Shell $ sudo apt-get upgrade Retrieve the IP address of the VM. You can do so by hovering over the network icon at the right bottom of the VM or by executing the following command in a terminal window. Shell $ ip a Install openssh-server in order to be able to connect via SSH from your host to the VM. Shell $ sudo apt install openssh-server As a last step, try to connect from your host to the VM via a terminal window, and replace the IP address with the IP address of your Controller VM. Shell $ ssh [email protected] Shutdown the VM. 3. Create Target Machines In this section the two target machines will be created. In VirtualBox, right-click the Ansible Controller and choose Clone… Fill in the following and click the Next button: Name: Target1 MAC Address Policy: Generate new MAC addresses for all network adapters Choose for Linked clone (you can also choose for a full clone, but when it is only for testing purposes, there is no harm for chosing a linked clone). Click the Clone button. Again, log in to the VM, retrieve the IP address and try to SSH to the VM from your host. Lastly, create in a similar way a Target2 machine. 4. Install Ansible The controller needs an Ansible installation in order to be able to run playbooks from the Ansible controller. Several options are available for installing Ansible, these can be found in the documentation. The steps below were successfully executed inside the controller VM. The third command did not really execute successfully or it took too long. Nevertheless, the installation seems to be successful. Shell $ sudo apt update $ sudo apt install software-properties-common $ sudo add-apt-repository --yes --update ppa:ansible/ansible $ sudo apt install ansible Verify whether the Ansible installation was successful. Shell $ ansible --version ansible [core 2.12.4] config file = /etc/ansible/ansible.cfg configured module search path = ['/home/osboxes/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules'] ansible python module location = /home/osboxes/.local/lib/python3.8/site-packages/ansible ansible collection location = /home/osboxes/.ansible/collections:/usr/share/ansible/collections executable location = /usr/bin/ansible python version = 3.8.10 (default, Mar 15 2022, 12:22:08) [GCC 9.4.0] jinja version = 3.1.1 libyaml = True 5. IDE Configuration Although it is perfectly possible to create Ansible files with a text editor, it is easier and better to use an IDE for this. When you are developing with Java, you probably already have IntelliJ installed onto your host machine and with the help of some plugins, creating Ansible scripts will make your life a lot easier. Install via File – Settings… – Plugins the Ansible plugin (for autocompletion during development of Ansible scripts) and the yamllint plugin (for verifying your yaml syntax). In order to be able to use the yamllint plugin, you also need to install yamllint itself. See the yamllint documentation how to do this. You also need to enable yamllint in IntelliJ. Navigate to File – Settings… and search for yamllint. Enable yamllint and click the OK button. Create a new empty project MyAnsiblePlanet via File – New – Project… and click the Finish button. The project files are located on your host machine, you now have to find a way to sync them to the controller. This can be done with the help of the rsync command. In the project directory a file transferdata.sh is available with the rsync command to copy the project files to the controller. Do not forget to change the IP address of the controller when it is different than the one in the script. Shell rsync -avz . [email protected]:MyAnsiblePlanet Execute the script (do not forget to start the controller). Login via SSH to the controller and verify whether the files are correctly synced. 6. Conclusion In this post, you created an Ansible controller VM and two target VMs. You also setup your IDE and you have a way to sync your local project files to the Ansible controller machine. You are now all setup for experimenting with Ansible.

The article includes detailed step-by-step instructions along with helpful screenshots to help users connect Azure Data Factory (ADF) with Azure DevOps.

This article explains how we used GitHub PRs in a trunk-based, continuous deployment development team.

Moving to SaaS software is a huge step to take, and it requires deep analysis and proper process setup. This post intends to guide you on how to move to SaaS.