1 Answer
- Newest
- Most votes
- Most comments
0
Hi, as this agent was working previously can you look into any network changes that may have occurred that could have affected communication from this agent. Some areas to look into.
- Hypervisor networking health where the VM is hosted.
- Verify with the networking team that port 443 is still allowed.
- Verify that if using a new or existing private DataSync endpoint within the same VPC, that Private DNS names is disabled for the VPC endpoint.
https://docs.aws.amazon.com/datasync/latest/userguide/datasync-in-vpc.html
Create a VPC endpoint for the DataSync service.
To do this, open the Amazon VPC console at https://console.aws.amazon.com/vpc/, and choose Endpoints from the navigation pane at left. Choose Create endpoint.
For Service category, choose AWS services. For Service Name, choose DataSync in your AWS Region (for example, com.amazonaws.us-east-1.datasync). Then choose the VPC and security group that you chose in steps 1 and 3. Make sure that you clear the Enable Private DNS Name check box.
answered a year ago
Relevant content
- asked 3 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 3 years ago