How to skip the current 'Relay_Master_Log_File' in AWS MYSQL RDS?
Replication Lag is usually measured by finding the difference between the following


TIMESTAMP#1 at (Relay_Master_Log_File,Exec_Master_Log_Pos)
TIMESTAMP#2 at (Master_Log_File,Read_Master_Log_Pos)


From what I am seeing in the SHOW SLAVE STATUS\G


you are 98230 seconds (27 hours 17 minutes 10 seconds) behind
you have 329 binlogs (278337 - 278008) to process after mysql-bin-changelog.278337
The sum of all your binlogs is 354792434 (338M)


If the Seconds_Behind_Master is steadily increasing by one every second, you will have to wait it out and let replication catch up. This is a strange indication that you are running some terrible query that is making the number of binlogs waiting to be processed increase. You could see that query by running show processlist; and look for the SQL thread (where the user is system user) with the same number for Time as the Seconds_Behind_Master.

If you cannot wait for the catch up of replication, you just need to spin up another read-only slave and drop this very latent slave.