Security Token Error (switching DB from Redshift to Athena)


We are currently running all our dashboards and reports, off Redshift DB ( via We have done a DB upgrade, and would like to switch our DB to Athena (we are decoing Panoply). Our Athena DB has all the same tables/fields.

Our goal is to just switch the underlying DB (vs full rebuild) because we have a lot of visualizations and dashboards, and we want to avoid the manual work of recreating them all by hand.

However when we change the DB we get this error:

[Simba)[AthenaJDBC)(100071) An error has been thrown from the AWS Athena client. Thc security token included in the request is invalid. [Execution ID not available]

FYI our current ‘working’ database we are trying to replace is:

Thank you in advance!

"browser-info": {
"language": "en-US",
"platform": "Win32",
"userAgent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/ Safari/537.36",
"vendor": "Google Inc."
"system-info": {
"file.encoding": "UTF-8",
"": "OpenJDK Runtime Environment",
"java.runtime.version": "11.0.20+8",
"java.vendor": "Eclipse Adoptium",
"java.vendor.url": "",
"java.version": "11.0.20",
"": "OpenJDK 64-Bit Server VM",
"java.vm.version": "11.0.20+8",
"": "Linux",
"os.version": "4.14.275-142.503.amzn1.x86_64",
"user.language": "en",
"user.timezone": "GMT"
"metabase-info": {
"databases": [
"hosting-env": "unknown",
"application-database": "mysql",
"application-database-details": {
"database": {
"name": "MySQL",
"version": "8.0.28"
"jdbc-driver": {
"name": "MariaDB Connector/J",
"version": "2.7.6"
"run-mode": "prod",
"version": {
"date": "2023-07-28",
"tag": "v0.46.6.4",
"branch": "release-x.46.6.x",
"hash": "7c60aca"
"settings": {
"report-timezone": "US/Eastern"

Can you connect to Athena from another sql client?

Hi @Luiggi thanks, yes, we use this athena all day, it even works in this metabase we separately added it and tested it (not as a replace) to ensure it works.

Hi just to confirm, we still have this problem here. That comment was just to demonstrate that our Athena is fine, the problem is with changing the underlying database.

hi @flamber it would be greatly appreciated to hear if you think you or someone else knowledgeable on this will be able opine on this topic. We are stuck, if we are unable to get help on this we need to move on some other solution. Thank you