Amazon AppFlow Jira Cloud connector fails with 410 Gone (needs migration to /rest/api/3/search/jql)

The issue you're experiencing with the Amazon AppFlow Jira Cloud connector is related to Atlassian's API changes. Based on the information available, Amazon AppFlow uses the Jira REST API to transfer data objects from Jira Cloud. When Atlassian makes changes to their API endpoints, such as migrating from an older search API to the new /rest/api/3/search/jql endpoint, this can cause compatibility issues with the connector.

Currently, there is no specific information about an update timeline for the Amazon AppFlow Jira Cloud connector to address this particular API change.

As a potential workaround, you might want to check if:

1. Your OAuth 2.0 integration app in the Atlassian Developer console has all the necessary permissions and is properly configured
2. Your connector profile settings are up to date

However, if the connector is specifically using the deprecated API endpoint that has been removed by Atlassian, these steps may not resolve the issue. In this case, you would need to wait for AWS to update the connector to use the new API endpoint.

For critical workflows, you might need to consider alternative integration methods until the connector is updated to support the new Jira Cloud API endpoint.
Sources
Jira Cloud connector for Amazon AppFlow - Amazon AppFlow