AWS IAM policies must be created first to describe the exact permissions necessary for asset discovery and replication. If not all regions are going to be migrated, then consider limiting the access with condition keys and specify only those that are going to be migrated.
After creating policies, they need to be attached to a user and that user needs to have an access key created for the service to use. See AWS Managing access keys for IAM users.
The following table lists the IAM AWS policies created for each AWS service. These policies contain the corresponding IAM permissions as described in the table.
AWS Cost Explorer and Amazon CloudWatch are only required if cost estimation and sizing recommendations are intended to be used as part of a migration plan.
An Amazon CloudWatch agent needs to be configured on each instance to collect more precise and advanced performance metrics.
For AWS source environments, discovery and replication tasks are performed by different serivce components. Discovery tasks are run by the Oracle Cloud Migrations discovery service and replication tasks are run by the Hydration agents. Access to credentials is validated using IAM policies at the begining of each discovery or replication operation. See AWS Service Policies for more information.