aws backup 'network failure"

Create a new role and try change the job role. This might work...

When encountering a network failure during AWS Backup setup for your EC2 instance, there are several potential causes and solutions to consider:

1. Insufficient Network Bandwidth: If you're backing up on-premises VMs or large EC2 instances, network congestion can cause backup failures. AWS Backup recommends a minimum bandwidth of 1000 Mbps for upload bandwidth to handle data transfers properly.

2. Security Group Configuration: Verify that your security groups allow the necessary traffic for AWS Backup. For Backup Gateway endpoints, the following TCP ports must be allowed:

• TCP 443 (HTTPS)
• TCP 1026
• TCP 1027
• TCP 1028
• TCP 1031
• TCP 2222

3. Network Connectivity: Ensure proper connectivity between your EC2 instance and AWS Backup services. If you're using VPC endpoints for AWS Backup, confirm they're correctly configured with the service name com.amazonaws.[region].backup.

4. Instance Network Settings: Check that your EC2 instance's network settings are properly configured, especially if you're using EC2 Instance Connect or other connectivity methods.

5. VPC Configuration: Verify that your VPC and subnet configurations allow proper internet connectivity or have the appropriate VPC endpoints configured.

If the issue persists after checking these items, you might want to:

• Retry the backup job after confirming bandwidth availability
• Check AWS Service Health Dashboard for any service disruptions
• Review any EventBridge events related to your backup job for specific error messages that might provide more details about the failure

For EC2 instances connected to AWS Directory Service, also ensure that the network configuration allows communication between the Directory Service and your EC2 instance.
Sources
Troubleshoot VM issues - AWS Backup
EC2 instance failed to connet | AWS re:Post
AWS Backup network - AWS Backup