Cross Account Resource Access - Invalid Principal in Policy

Keeping accounts decoupled is important in cross account scenarios. Setting permissions in the wrong way can lead to unwanted behavior. Better avoid setting a principal in a resource policy to a specific ARN as it may lead to ‘Invalid Principal’-errors. Using conditions provides you a more reliable and least privileged architecture.

zum Artikel gehen

Serverless Cross-Account Microservices

When setting up a microservice architecture, each individual service is often owned and managed by a different team. To achieve a higher level of resource isolation, and allow for more granular security and cost management, each service team usually deplo

zum Artikel gehen

S3 Cross Account Adventures

Update October 2020 AWS has finally added a feature to solve our problem, now all that’s missing is CloudFormation support :-) Amazon S3 Object Ownership is available to enable bucket owners to automatically assume ownership of objects uploaded to t

zum Artikel gehen

Bridging the terraform - CloudFormation gap

CloudFormation does not cover all AWS Resource types. Terraform does a better job in covering resource types just in time. So if you want to use a resource type which CloudFormation does not support yet, but you want to use CloudFormation, you have to bui

zum Artikel gehen

AWS Organizations Mail bei Umstellung auf All Features

AWS Organizations ist ja nun seit Ende Februar verfügbar. (siehe auch hier im AWS Blog) Wenn man einen bestehenden Consolidated Billing “Master Account” umstellen möchte auf “All Features” … damit ist gemeint auch die Möglic

zum Artikel gehen

Cross Account Kafka Streaming: Part 1

When discussing high performant real-time event streaming, Apache Kafka is a tool that immediately comes to mind. Optimized for ingesting and transforming real-time streaming data in a reliable and scalable manner, a great number of companies today rely o

zum Artikel gehen