Using Your AWS Credentials

After generating the required AWS credentials, you will need to enter them into the CloudEndure User ConsoleCloudEndure SaaS User Interface. A web-based UI for setting up, managing, and monitoring the Migration and Disaster Recovery solutions..

Using your AWS credentials

1. Sign into the CloudEndure Console.
2. Select the project to which you want to assign your AWS credentials from the Projects dropdown menu.
   
   
3. Navigate to Setup & Info from the main left-hand navigational menu.Within Setup & Info, navigate to the AWS CREDENTIALS tab, and scroll to Staging Area Account Credentials.
   
   The AWS CREDENTIALS page enables you to set up your replication Staging AreaA part of the Target location; includes the Replication Servers’ subnet, IPs, and the Replication Servers and their disks. on AWS and manage and monitor resources on your AWS TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery). infrastructure.
4. Enter the corresponding credentials that you obtained in the previous Generating the Required AWS Credentials section into the corresponding fields:
   • AWS Access Key ID
   • AWS Secret Access Key
     

   Note: Reminder, your AWS Access Key ID and AWS Secret Access Key can be found within the Download.csv file you downloaded after setting up your AWS credentials in the previous section.

5. After you entered your AWS credentials, click the Save button at the bottom right of the page.
   
   Your AWS credentials are now saved in your CloudEndure ProjectA Project is the basic organizational unit for running a CloudEndure solution..
   

Note: Click the EDIT button if you need to edit your Credentials.

Note: If the AWS credentials you entered do not exist or invalid in any way, or if the IAM policy you created and attached to the user does not contain the required permissions, you will get the following error message:

In this case, you can should attempt the following troubleshooting steps:

• Verify that the IAM policy you created is identical to the CloudEndure pre-defined policy. Limiting the permissions of this policy may prevent the management and monitoring of AWS resources, which are required for the CloudEndure solution (as illustrated in the Creating a Policy for CloudEndure section.)
• Verify that you provided the IAM user with a Programmatic access type (as illustrated in the Creating a New IAM User and Generating AWS Credentials section.)
• Verify that you attached to the IAM user the correct policy (as illustrated in the Creating a New IAM User and Generating AWS Credentials section.)
• Retry the steps in the Generating the Required AWS Credentials section with the most up-to-date credentials within the AWS console.

Using different Target Account Credentials

CloudEndure allows you to host your Replication ServersThe CloudEndure Machine to which Staging Disks are attached and to which data is replicated; launched on the Target location. in the Staging AreaA part of the Target location; includes the Replication Servers’ subnet, IPs, and the Replication Servers and their disks. in one AWS AccountThe entity that signed up with CloudEndure. while launchingAfter the replication to the Staging area, launching is the process of setting up the Replication Servers, for Testing or Cutover and Recovery purposes. your replicated SourceThe location of the Source machine; Currently either a specific Region or Other Infrastructure. machines (which will become TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery). machines after launch) in a separate TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery). AWS AccountThe entity that signed up with CloudEndure..

This functionality is valuable if you have more than 300 servers and are being limited by the 300 installed servers per AWS AccountThe entity that signed up with CloudEndure. per AWS RegionA Region denotes a geographical area (US east, EU west, etc.). Each Region has multiple, isolated locations known as Zones. Zones are isolated from one another, but Zones within the same Region are connected through low-latency links. Cloud Regions exist in AWS, Microsoft Azure, and GCP. limit.

Important! When activating this feature you will only be able to select Other Infrastructure as your SourceThe location of the Source machine; Currently either a specific Region or Other Infrastructure. under the Replication Settings tab, and you will not be able to select a specific AWS SourceThe location of the Source machine; Currently either a specific Region or Other Infrastructure. RegionA Region denotes a geographical area (US east, EU west, etc.). Each Region has multiple, isolated locations known as Zones. Zones are isolated from one another, but Zones within the same Region are connected through low-latency links. Cloud Regions exist in AWS, Microsoft Azure, and GCP..

Important! Your TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery). machines can only be launched in the same RegionA Region denotes a geographical area (US east, EU west, etc.). Each Region has multiple, isolated locations known as Zones. Zones are isolated from one another, but Zones within the same Region are connected through low-latency links. Cloud Regions exist in AWS, Microsoft Azure, and GCP. used for the Replication ServersThe CloudEndure Machine to which Staging Disks are attached and to which data is replicated; launched on the Target location. as defined under the Replication Settings.

Important! For this feature to work, you will need to modify the CloudEndure IAM Policy for the TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery). AWS AccountThe entity that signed up with CloudEndure.. Use the regular CloudEndure IAM Policy, and add the following line in between "ec2:DeleteSnapshot", and "ec2:ModifyVolumeAttribute",:

"ec2:ModifySnapshotAttribute",

Note: Customers that wish to enable Volume Encryption must share the share the KMS encryption key from the Target AWS Account with all Staging AWS Accounts. The default key cannot be shared. Learn more here.

Note: The Target AWS Account will use the same Blueprint settings as those defined in the Project.

To use a different AWS AccountThe entity that signed up with CloudEndure. to host your TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery). machines, scroll down to the Target Account Credentials section on the AWS CREDENTIALS tab.

Click the EDIT button.

Check the Use different Target Account Credentials box.

The AWS Access Key ID and AWS Secret Access Key fields will appear. Generate these credentials within your TargetThe location where the Replication Server will be located and where Target machines will be created (as a result of Test, Cutover or Recovery). AWS AccountThe entity that signed up with CloudEndure. by following the instructions in the Generating the Required AWS Credentials section and click SAVE.