From the EC2 dashboard, click the yellow Launch Instance button to start the EC2 instance deployment workflow.

In Step 1, select "Red Hat Enterprise Linux 8 (HVM), SSD Volume Type - ami-0b0af3577fe5e3532 (64-bit x86) / ami-01fc429821bf1f4b4 (64-bit Arm)."

In Step 2, select an m5 instance type with the appropriate CPU and memory allocation based on your Oracle database workload. Click "Next: Configure Instance Details."

In Step 3, choose the VPC and subnet where the instance should be placed and enable public IP assignment. Click "Next: Add Storage."

In Step 4, allocate enough space for the root disk. You may need the space to add a swap. By default, EC2 instance assign zero swap space, which is not optimal for running Oracle.

In Step 5, add a tag for instance identification if needed.

In Step 6, select an existing security group or create a new one with the desired inbound and outbound policy for the instance.

In Step 7, review the instance configuration summary, and click Launch to start instance deployment. You are prompted to create a key pair or select a key pair for access to the instance.

Log into EC2 instance using an SSH key pair. Make changes to your key name and instance IP address as appropriate.

ssh -i ora-db1v2.pem ec2-user@54.80.114.77

From the FSx console, click Create File System to start the FSx provision workflow.

Select Amazon FSx ONTAP. Then click Next.

Select Standard Create and, in File System Details, name your file system, Multi-AZ HA. Based on your database workload, choose either Automatic or User-Provisioned IOPS up to 80,000 SSD IOPS. FSx storage comes with up to 2TiB NVMe caching at the backend that can deliver even higher measured IOPS.

In the Network & Security section, select the VPC, security group, and subnets. These should be created before FSx deployment. Based on the role of the FSx cluster (primary or standby), place the FSx storage nodes in the appropriate zones.

In the Security & Encryption section, accept the default, and enter the fsxadmin password.

Enter the SVM name and the vsadmin password.

Leave the volume configuration blank; you do not need to create a volume at this point.

Review the Summary page, and click Create File System to complete FSx file system provision.

By default, an EC2 instance uses an SSH key pair for access authentication. From Ansible controller automation root directories /home/ec2-user/na_oracle19c_deploy, and /home/ec2-user/na_rds_fsx_oranfs_config, make a copy of the SSH key accesststkey.pem for the Oracle host deployed in the step "Creating and connecting to an EC2 instance for hosting Oracle database."

Log into the EC2 instance DB host as ec2-user, and install the python3 library.

sudo yum install python3

Create a 16G swap space from the root disk drive. By default, an EC2 instance creates zero swap space. Follow this AWS documentation: How do I allocate memory to work as swap space in an Amazon EC2 instance by using a swap file?.

Return to the Ansible controller (cd /home/ec2-user/na_rds_fsx_oranfs_config), and execute the preclone playbook with the appropriate requirements and linux_config tags.

ansible-playbook -i hosts rds_preclone_config.yml -u ec2-user --private-key accesststkey.pem -e @vars/fsx_vars.yml -t requirements_config

ansible-playbook -i hosts rds_preclone_config.yml -u ec2-user --private-key accesststkey.pem -e @vars/fsx_vars.yml -t linux_config

Switch to the /home/ec2-user/na_oracle19c_deploy-master directory, read the README file, and populate the global vars.yml file with the relevant global parameters.

Populate the host_name.yml file with the relevant parameters in the host_vars directory.

Execute the playbook for Linux, and press Enter when prompted for the vsadmin password.

ansible-playbook -i hosts all_playbook.yml -u ec2-user --private-key accesststkey.pem -t linux_config -e @vars/vars.yml

Execute the playbook for Oracle, and press enter when prompted for the vsadmin password.

ansible-playbook -i hosts all_playbook.yml -u ec2-user --private-key accesststkey.pem -t oracle_config -e @vars/vars.yml

After automated SnapCenter installation, log into SnapCenter as an administrative user for the Window host on which the SnapCenter server is installed.

From the left-side menu, click Settings, and then Credential and New to add ec2-user credentials for SnapCenter plugin installation.

Reset the ec2-user password and enable password SSH authentication by editing the /etc/ssh/sshd_config file on the EC2 instance host.

Verify that the "Use sudo privileges" checkbox is selected. You just reset the ec2-user password in the previous step.

Add the SnapCenter server name and the IP address to the EC2 instance host file for name resolution.

[ec2-user@ip-10-0-0-151 ~]$ sudo vi /etc/hosts
[ec2-user@ip-10-0-0-151 ~]$ cat /etc/hosts
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
10.0.1.233  rdscustomvalsc.rdscustomval.com rdscustomvalsc

On the SnapCenter server Windows host, add the EC2 instance host IP address to the Windows host file C:\Windows\System32\drivers\etc\hosts.

10.0.0.151		ip-10-0-0-151.ec2.internal

In the left-side menu, select Hosts > Managed Hosts, and then click Add to add the EC2 instance host to SnapCenter.