Deploy the Infrastructure
You will create two Amazon S3 buckets in two different AWS regions. The Ohio region (also known as us-east-2) will be referred to throughout this lab as the east S3 bucket, and Oregon (also known as us-west-2) will be referred to as the west S3 bucket.
1.1 Log into the AWS console
If you are attending an in-person workshop and were provided with an AWS account by the instructor:
Click here for instructions to access your assigned AWS account:
Go to https://dashboard.eventengine.run/login
Enter the 16 character hashcode you were provided and click “Proceed”

Sign-in using either an Amazon.com retail account or a One-Time Password (OTP) that will be emailed to you.

[optional] assign a name to your account (this is referred to as “Team name”)
- click “Set Team Name”
- Enter a name and click “Set Team Name”
Click “AWS Console”

Get and store your AWS credentials
Access the AWS console
- Click “Open AWS Console”.
- The AWS Console will open and you can continue the lab.
If you are using your own AWS account:
Click here for instructions to use your own AWS account:
- Sign in to the AWS Management Console as an IAM user who has PowerUserAccess or AdministratorAccess permissions, to ensure successful execution of this lab.
You will deploy the infrastructure for two Amazon S3 buckets. Since these will be in two different regions, you will need to create an AWS CloudFormation stack in each region. You will use the same CloudFormation template for both regions.
You must use the same NamingPrefix parameter for both CloudFormation templates in both regions, or replication will fail!
1.2.1 Deploy east S3 bucket
- It is recommended that you deploy the east s3 bucket in the Ohio region. This region is also known as us-east-2.
- Use the drop-down to select this region

- If you choose to use a different region, you will need to ensure future steps are consistent with your region choice.
- On the AWS Console go to the CloudFormation console
- Select Stacks
- Create a CloudFormation stack (with new resources) using the CloudFormation Template file and the Upload a template file option.
- For Stack name use
S3-CRR-lab-east
- Under Parameters enter a NamingPrefix
- This will be used to name your S3 buckets
- Must be string consisting of lowercase letters, numbers, periods (.), and dashes (-) between five and 40 characters
- This will be part of your Amazon S3 bucket name, which must be unique across all of S3.
- Record this value in an accessible place – you will need it again later in the lab.
- Click Next on the following pages until the page that requires you to acknowledge IAM resouces
- At the bottom of the page, select I acknowledge that AWS CloudFormation might create IAM resources with custom names
- Click Create stack
- You can go ahead and create the west bucket before this CloudFormation stack completes
Troubleshooting: If your CloudFormation stack deployment fails with the error <bucket name> already exists
- You did not pick a unique enough NamingPrefix
- Delete the failed stack
- Start over and choose a more unique NamingPrefix
- Amazon S3 bucket names share a global name space across all of AWS (including all AWS regions)
1.2.2 Deploy west S3 bucket
It is recommended that you deploy the west s3 bucket in the Oregon region for this lab. This region is also known as us-west-2.
- Use the drop-down to select this region

- If you choose to use a different region, you will need to ensure future steps are consistent with your region choice.
On the AWS Console go to the CloudFormation console
Select Stacks
Create a CloudFormation stack (with new resources) using the same CloudFormation Template file as before, and the Upload a template file option.
For Stack name use S3-CRR-lab-west
Under Parameters enter a NamingPrefix
- You must use the same value as you did previously
Click Next on the following pages until the page that requires you to acknowledge IAM resouces
At the bottom of the page, select I acknowledge that AWS CloudFormation might create IAM resources with custom names
Click Create stack
- Go back to the Ohio AWS Region and wait for the CloudFormation stack you created there to complete
- Click on the Outputs tab and record the Value of the S3 bucket name in an accessible location as east bucket
- Go to the the Oregon AWS Region and do the same thing, copying that S3 bucket name down as west bucket
- Go to the Amazon S3 console and verify that both buckets were created.
- Although S3 buckets are specific to an AWS region, the Amazon S3 console shows all buckets from all AWS Regions
- The two S3 buckets you will work with begin with
<your_naming_prefix>-crrlab
- Note the regions for the two S3 buckets your created
- There are also two new
logging
buckets – you will not need to do any actions with these.
- Click on either the east region or west region bucket, and note the following
- This bucket is empty - We will be adding objects to the bucket soon
- Click on Properties and note what properties are Enabled
Click here to learn why are these properties enabled
Versioning is Enabled:
For S3 Replication, both source and destination buckets MUST have versioning enabled
Default encryption is Enabled:
In our exercise we are demonstrating replication of encrypted objects.
It is a best practice to encrypt your data at rest.
Object-level logging is Enabled:
This logging will be used later in the lab.
It is used to better understand replication operations AWS takes on your behalf.