Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

eu-central-1, cant connect #54

Open
zoutepopcorn opened this issue Jan 19, 2015 · 4 comments
Open

eu-central-1, cant connect #54

zoutepopcorn opened this issue Jan 19, 2015 · 4 comments

Comments

@zoutepopcorn
Copy link

I cant connect to the eu-central-1. BUT: eu-west-1 is working fine.

I get the error:
{ [Error: PutItem [400]: The security token included in the request is invalid]
statusCode: 400,
requestId: 'XXX************************************XXXXX',
code: 'UnrecognizedClientException',
data:
{ __type: 'com.amazon.coral.service#UnrecognizedClientException',
message: 'The security token included in the request is invalid' } }

@waldher
Copy link

waldher commented Jan 28, 2015

Can confirm. I am having this problem as well. Could this be because eu-central-1 requires S3 Signature Version 4?

This is happening even with an IAM policy like this:

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Action": [
        "dynamodb:*",
        "cloudwatch:DeleteAlarms",
        "cloudwatch:DescribeAlarmHistory",
        "cloudwatch:DescribeAlarms",
        "cloudwatch:DescribeAlarmsForMetric",
        "cloudwatch:GetMetricStatistics",
        "cloudwatch:ListMetrics",
        "cloudwatch:PutMetricAlarm",
        "datapipeline:ActivatePipeline",
        "datapipeline:CreatePipeline",
        "datapipeline:DeletePipeline",
        "datapipeline:DescribeObjects",
        "datapipeline:DescribePipelines",
        "datapipeline:GetPipelineDefinition",
        "datapipeline:ListPipelines",
        "datapipeline:PutPipelineDefinition",
        "datapipeline:QueryObjects",
        "iam:ListRoles",
        "sns:CreateTopic",
        "sns:ListSubscriptionsByTopic",
        "sns:ListTopics",
        "sns:Subscribe",
        "sns:Unsubscribe"
      ],
      "Effect": "Allow",
      "Resource": "*"
    }
  ]
}

@tnolet
Copy link

tnolet commented Aug 17, 2016

Same issue here. Happening with an IAM policy of full Admin access, so certainly not an IAM issue.

@mda590
Copy link

mda590 commented Oct 21, 2016

@tnolet @zoutepopcorn @waldher Did any of you find a resolution to this? I am facing this issue with the new us-east-2 (Ohio) region. I noticed the DynamoDB API version was on the old version, so I tried to change that to the newer version, but that didn't fix it.

I'm running out of ideas.

@zoutepopcorn
Copy link
Author

@mda590 I dont know, switch to another server or try to contact aws.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants