Who is listed as the abuse contact for my IP address after I import it with BYOIP?

Hi pablothethird,

Please go through below steps I hope it will help to solve your issue.

When you import an IP range into AWS using the BYOIP (Bring Your Own IP) process, the IP range remains associated with your organization's details in the Regional Internet Registry (RIR) databases. The ownership and responsibility for the IP range, including the abuse contact information, remain with you.

Here’s what happens regarding abuse contact information after importing an IP range into AWS:

• WHOIS Information: The WHOIS database will continue to reflect your organization's information as the owner of the IP range, including the abuse contact details that you have registered with the RIR.

• AWS's Role: Although AWS will advertise the routes to your IP range via their Autonomous System Number (ASN), AWS does not change the WHOIS registration details. AWS will not replace your abuse contact information with their own.

• Abuse Handling: You will remain responsible for handling any abuse reports related to your IP range. Requests and reports regarding abuse sent to the abuse contact listed in WHOIS will come directly to you or your designated abuse contact.

Conclusion: After importing your IP range to AWS using BYOIP, you will continue to be the listed abuse contact in the WHOIS database, and you will be responsible for handling any abuse requests. AWS’s involvement is limited to route advertisement and does not extend to changing ownership or contact details in the WHOIS records.

Hi pablothethird,

Please try this solution.

To manage abuse contact responsibilities after importing an IP range into AWS using BYOIP, ensure that your contact information with the Regional Internet Registry (RIR) is accurate and up-to-date. Designate a specific team or individual to monitor and respond to abuse complaints, using a dedicated email address Implement a monitoring system to detect unusual traffic patterns and set up alerts for potential abuse. Develop a clear response plan for handling different types of abuse and use a ticketing system to track and manage complaints. Regularly review and update your security measures, such as firewalls and rate limiting, to protect against misuse. Communicate your acceptable use policies to any users of the IP range and provide a clear contact point for reporting abuse. This approach ensures that you can manage and address abuse incidents effectively while maintaining the reputation of your IP range.

https://repost.aws/knowledge-center/aws-abuse-report

https://repost.aws/knowledge-center/report-aws-abuse