When running copy to S3 on version 3.1 it might raise the following warning.
This warning can be caused by permission issues, communication or lack of EBS Direct API endpoint in target region.
In version 3.1 we have started to use the new EBS Direct API for copy to S3 related operations, this new API let us read the blocks directly from the snapshot and help us reduce cost & time for copy process.
When the copy process starts the server make a call to target region to check if the EBS Direct API is accessible, if it is not then it will raise a warning and fallback to 3.0.x way of copy to S3 (using volumes instead of reading blocks from snapshots).
If the API is available for the region, then you need to check that you have the latest permission updated for the N2WS server role.
You can find latest permissions attached here:
- What are the required minimal AWS permissions/roles for CPM operation?
You can also Check permissions in the UI:
If it is available and you updated the json permissions, then you can connect to the N2WS server via ssh(user is cpmuser & your private key) to test the connection manually.
If you don't know how to connect via SSH, You can see information from AWS on how to connect by clicking on the instance and then connect:
Once connected, you can test connectivity/permissions by running this command:
- aws ebs list-snapshot-blocks
--snapshot-id snap-05cddc7aa3c379497 --region us-east-1
Note: You need to replace us-east-1 with the relevant region, the region to choose is the one where the snapshot to copy is located
Note: If you run the command with snapshot id that does not exist, then the expected result is ‘snapshot not found’ - meaning command was able to reach the endpoint and had permission.
If it fails, it might timeout or give you permission issue:
You need to make sure that the API endpoint in the target region is accessible from N2WS server and that there is no permission issue.