DEV Community

Martin Muller 🇩🇪🇧🇷🇵🇹 for AWS Community Builders

Posted on • Originally published at

Make your AWS Prod environment super with Superwerker

Hi everyone.

I want to make my senjuns project production-ready. So far I had only deployed it in my developer AWS account. My developer account has no AWS services configured that are needed for a reasonable production environment. These are for example AWS SSO, ControlTower, SecurityHub and some more. The Superwerker CFN Template came in handy. It allowed me to configure a new AWS account with many great AWS services for production use. In the following sections, I would like to go into what Superwerker is exactly and how I used it.

What is Superwerker?

Superwerker is an open-source AWS CloudFormation solution that simplifies the setup of an AWS account. It follows best practices for security and efficiency. It was/is developed and maintained by AWS Advanced Partners kreuzwerker and superluminar. It even has its own landing page with great content like a short video and more. Hard to believe this is a free product.

The Superwerker deployment has a lot of cool features which are all explained very well in the docs here. I really like that it uses Architectural Decision Records to describe each feature. Below I explain the features in my own words.


Backup enables the AWS Backup Service and by default, a backup is created every day. It creates backups of databases that are also supported by AWS Backup.


Budget helps to keep track of the costs in AWS and gives a warning in time if there are more costs than usual. It does this by calculating the average of the last three months and if this is exceeded, a warning comes. A really cool idea in my opinion.

Control Tower

Control Tower simplifies managing multiple AWS accounts with AWS SSO. For me, this is the main reason why I use Superwerker. So I can access my different AWS accounts like build, dev and prod very easily. I also like the fact that with AWS SSO I can simply copy the AWS account credentials and use them for the AWS CLI.


GuardDuty is an AWS service for finding potential security threats.

Living Documentation

Living Documentation is a pretty cool feature that generates documentation via the AWS CloudWatch Dashboard. This then provides information on, for example, how to do an SSO setup with external identity providers like Google and much more. Extremely cool is how this documentation also updates itself when certain configurations have already been made. That's why it's called Living Documentation.


Superwerker creates OpsItems in OpsCenter when emails are sent from the RootMail feature. With the Notifications feature emails are sent to the specified addresses. This way the user does not have to manually log into the AWS Console and check OpsCenter. Through email, one thus also has a centralized collection point for multiple accounts.


RootMail creates the uniformed email addresses for the audit and log archive accounts created by Control Tower. For this purpose, a separate Hosted Zone is created, for example aws.mycompany.test with Route53, and the required settings are made with AWS SES to receive the emails.

Security Hub

The Security Hub feature enables AWS Security Hub for all accounts. The user needs to log into the audited account to view the aggregated Security Hub view.

In the next section, I would like to share more about my Experience with Superwerker.

Superwerker Experience

You can find the instructions for running Superwerker here. For me, the installation went quite smoothly. However, the RootMail nested stack was an exception. I had previously imported my domain and associated Hosted Zone from another AWS account. However, I did not properly configure the name servers from the domain in the designated Hosted Zone. By debugging the Superwerker Lambdas, I noticed this error.

So if you also get the following error logs in the RootMailReady Lambda, you just need to check if you have configured your domain and Hosted Zone properly.

    "level": "info",
    "msg": "verification not yet successful",
    "res": {
        "VerificationAttributes": {
            "": {
                "VerificationStatus": "Pending",
Enter fullscreen mode Exit fullscreen mode
    "level": "info",
    "msg": "DKIM verification not yet successful",
    "res": {
        "DkimAttributes": {
            "": {
                "DkimEnabled": true,
                "DkimVerificationStatus": "Pending",
Enter fullscreen mode Exit fullscreen mode

If anyone encounters the same or similar problem, I have created a pull request with troubleshooting information.


Superwerker is a great CloudFormation QuickStart to set up an AWS production environment professionally and easily. Many improvements and new features are already planned in the Superwerker Backlog. The Superwerker community is still looking for active support in implementing new features and improvements. I am very excited to continue using the Superwerker deployment in my current project.

Thanks to the DeepL translater (free version) for helping with translating to english and saving me tons of time :).

I love to work on Open Source projects. A lot of my stuff you can already use on . If you like my work there and my blog posts, please consider supporting me on:

Buy me a Ko-Fi


Buy me a Ko-Fi

And don't forget to visit my site

Top comments (0)