When Redefining a gateway, I get a conflictexception error

The issue you're experiencing is not uncommon when working with AWS IoT Core and gateways. Even after deleting a gateway from IoT Core, there can sometimes be lingering records or conflicts that prevent immediate re-provisioning.

In situations like this, there are a few things to consider:

1. Cross-region conflicts: Sometimes, the conflict may be due to a record existing in a different AWS region. It's worth checking other regions where you might have previously provisioned the gateway to ensure it's not causing a conflict.

2. Idempotency window: AWS often uses a 10-minute idempotency window for certain operations. This means that if you try to recreate a resource with the same parameters within 10 minutes of deleting it, you might encounter conflicts. You could try waiting for a short period before attempting to redefine the gateway.

3. Cached information: Your third-party tool might be caching some information about the gateway. Try clearing any cached data or restarting the tool before attempting to redefine the gateway.

4. AWS backend synchronization: Sometimes, there can be a delay in AWS's backend systems fully processing the deletion. This could cause the system to think the gateway still exists even though it's no longer visible in the IoT Core console.

If the problem persists after considering these points, you may need to contact AWS support for further assistance. They can check for any hidden conflicts or lingering records in the backend that might be causing this issue.
Sources
LoraWAN Gateway EUI exists error | AWS re:Post