-
Notifications
You must be signed in to change notification settings - Fork 16
Region af-south-1 is NOT supported #17
Description
Describe the bug
when copy S3 objects from af-south-1, error happens.
To Reproduce
- create data replication hub in ap-southeast-1 region
- create data replication task, from af-south-1 to ZHY cn-northwest-1
Expected behavior
Support af-south-1 and me-south-1
Screenshots
==== CloudWatch Log ====
INFO:JobSender> Start comparing...
Traceback (most recent call last):
File "job_sender.py", line 105, in
find_and_send_jobs(src_client, des_client, sqs_queue_name,
File "job_sender.py", line 32, in find_and_send_jobs
job_sender.send_jobs(include_version)
File "/app/migration_lib/job.py", line 122, in send_jobs
self._get_delta_and_send(include_version)
File "/app/migration_lib/job.py", line 83, in _get_delta_and_send
src_file_set = self._get_source_set(src_list_gen, include_version)
File "/app/migration_lib/job.py", line 38, in _get_source_set
src_list = next(src_list_gen)
File "/app/migration_lib/client.py", line 218, in _list_objects_without_version
response = self._list_objects_func(**list_kwargs)
File "/app/migration_lib/client.py", line 202, in _list_objects_func
return self._client.list_objects_v2(**kwargs)
File "/usr/local/lib/python3.8/site-packages/botocore/client.py", line 357, in _api_call
return self._make_api_call(operation_name, kwargs)
File "/usr/local/lib/python3.8/site-packages/botocore/client.py", line 676, in _make_api_call
raise error_class(parsed_response, operation_name)
botocore.exceptions.ClientError: An error occurred (IllegalLocationConstraintException) when calling the ListObjectsV2 operation: The af-south-1 location constraint is incompatible for the region specific endpoint this request was sent to.
Please complete the following information about the solution:
- Version: [e.g. v1.0.0]
- Region: [af-south-1]
- Was the solution modified from the version published on this repository?
- If the answer to the previous question was yes, are the changes available on GitHub?
- Have you checked your service quotas for the sevices this solution uses?
- Were there any errors in the CloudWatch Logs?
Additional context
Add any other context about the problem here.