Setting up

Submit an RFC to create an RDS stack using Deployment | Advanced stack components | RDS database stack | Create (ct-2z60dyvto9g6c). Do not use the target DB name (RDSDBName parameter) in the creation request, the target DB will be created during the import. Make sure to allow enough space (RDSAllocatedStorage parameter). For details on doing this, see the AMS Change Management Guide RDS DB Stack | Create.

Submit an RFC to create the transit S3 bucket (if does not exist already) using Deployment | Advanced stack components | S3 storage | Create (ct-1a68ck03fn98r). For details on doing this, see the AMS Change Management Guide S3 Storage | Create.

Submit a Management | Other | Other | Update (ct-1e1xtak34nx76) RFC to implement the customer_rds_s3_role with these details:

In the console:

With an ImportDbParams.json file for the CLI:

{
       "Comment": "{"Transit S3 bucket name":"BUCKET_NAME"}",
       "Priority": "High"
     }
}

Submit a Management | Other | Other | Update RFC requesting AMS to set the SQLSERVER_BACKUP_RESTORE option to the RDS created in step 1 (use the stack ID from the step 1 output, and the customer_rds_s3_role IAM role in this request, in this request).

Submit an RFC to create an EC2 instance (you can use any existing EC2 or on-premise workstation/instances), and install Microsoft SQL Management Studio on the instance.