Posts

When setting up access to your AWS accounts governed by AWS Control Tower, you have two options: Allow Control Tower to configure account access with IAM Identity Center. Configure IAM Identity Center or another access method yourself. If you decide to let Control Tower manage account access with IAM Identity Center, the setup process can be straightforward or complex, depending on your Control Tower configuration.

More than one and half year ago AWS announced the launch of the AWS Parameters and Secrets Lambda Extension. This extension allows you to retrieve secrets and parameters from AWS Secrets Manager and AWS Systems Manager, respectively, without using the APIs. By doing so, you can avoid the associated costs and the need to manage the caching of values manually.

Recently I began tagging resources in my primary AWS account. I use this account as a playground where I can experiment with services and occasionally host side projects. As I’ve recently hosted new projects, I figured it was time to have a better understanding of costs, hence the decision to implement tagging.

Why # The release of applications through lightweight containers has practical advantages, as the images contain all the dependencies necessary for the correct functioning of the application. However, the benefits of containerization can be lost if these images are too large and therefore require several minutes for the application to start.

If you work with AWS, you must have used AWS credentials at least once to run commands through the AWS CLI, CDK CLI, or SAM CLI. When developing in a Dev Container, you don’t have access to your local file system. So, if you try to run an AWS command in the Dev Container, you will encounter some sort of “missing credentials” error.

Some weeks ago, I spoked about the benefits of using Dev Containers in Open Source projects. In the article, I also provided a definition of a Dev Container and described the benefits of using them. You can find it here. Today I would like to do something more practical and share with you a minimum configuration to setup Dev Containers for your Hugo website.

During my first two weeks at Cloud Enablers I have started to look into Development Containers, among other things. Development (or, in their short form, Dev) Containers are containers used for software development purposes. They are containers enriched with all the content and metadata necessary to be able to code inside them.

In the previous article of this series, we delved into the Reliability pillar structure, describing the Design Principles and the structure of the best practices. If you missed it or need a recap, you can find it here or access it through the dropdown menu at the beginning of the page.

In the introduction article of this series, I have described the AWS Well-architected Framework structure and how to use it to evaluate your architectures. I have also briefly introduced the Reliability Pillar and listed the 13 questions we will examine in this series. Before we get started with the questions, let’s delve into the Reliability Pillar structure.

If you work with AWS you are likely familiar with the AWS Well-Architected Framework and understand how crucial it is to periodically evaluate your system using this framework to ensure its stability and efficiency. For those who may not be familiar, the AWS Well-Architected Framework provides a set of design principles, best practices and questions that help you to evaluate architectures.