Securing Static Website In a previous blog, I wrote about setting up this website. It is a simple static site with a basic architecture as shown below: The teachmyselfcloud domain is registered with Route 53. This automatically creates a hosted zone, with a NS record and a start of authority SOA record. I created an alias A record that points to the CloudFront distribution, that sits in front of the S3 bucket that holds the individual objects.

AWS Organizations Terminology and Concepts Organization An organization is the entity that you create to consolidate your AWS accounts Root The root is the parent container that is automatically created when you create an organization. Currently, you can only have one root. Organizational Unit (OU) An organizational unit is a container for accounts within a root. You can create a hierarchy by creating an OU within an existing OU. You can then add AWS accounts to an OU.

Identity and Access Management (IAM) AWS Identity and Access Management (IAM) enables you to manage access to AWS services and resources securely. IAM is global, and this means when you create users, groups and roles, they will be accessible in any region. User An IAM user is an entity that you create in AWS. The IAM user represents the person or services who uses the IAM user to interact with AWS.

Creating AWS Accounts Best practices when using AWS at an enterprise level are to use a multi-account strategy, which helps provide isolation, greater control and limited blast radius. This is highlighted in the AWS Landing Zone. In order to play around with new services like AWS Organizations and fully understand cross-account access and implications, I have set up 3 separate AWS accounts Set up AWS CLI I find it easier to use the AWS Command Line Interface (CLI) to call the APIs of AWS services directly.