instructure / instructure/dockerfiles
kinsalate getRecords is giving error "An error occurred (UnrecognizedClientException) when calling the GetRecords operation: The security token included in the request is invalid."
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 58
- Forks
- 35
- PR merge metrics
- No merged PRs in 30d
Description
steps to reproduce -
I've started the below docker-compose -
- I'm sucessfullay able to create Stream
AWS_ACCESS_KEY_ID=x AWS_SECRET_ACCESS_KEY=x aws kinesis create-stream --endpoint-url https://localhost:4567 --stream-name my-local-stream --shard-count 6 --no-verify-ssl --region us-west-2 - Able to list stream successfully
AWS_ACCESS_KEY_ID=x AWS_SECRET_ACCESS_KEY=x aws kinesis list-streams --endpoint-url https://localhost:4567 --shard-count 6 --no-verify-ssl --region us-west-2 - Able to put records successfully
AWS_ACCESS_KEY_ID=x AWS_SECRET_ACCESS_KEY=x aws kinesis put-record --stream-name my-local-stream --data 'RGF0YT1qb3NlfDEyCg==' --partition-key 'PartitionKey=partitionkey1' --endpoint-url https://localhost:4567 --no-verify-ssl --region us-west-2
AWS_ACCESS_KEY_ID=x AWS_SECRET_ACCESS_KEY=x aws kinesis put-record --stream-name my-local-stream --data 'RGF0YT1qb3NlfDEz' --partition-key 'PartitionKey=partitionkey1' --endpoint-url https://localhost:4567 --no-verify-ssl --region us-west-2
AWS_ACCESS_KEY_ID=x AWS_SECRET_ACCESS_KEY=x aws kinesis put-record --stream-name my-local-stream --data 'RGF0YT1qb3NlfDE0' --partition-key 'PartitionKey=partitionkey2' --endpoint-url https://localhost:4567 --no-verify-ssl --region us-west-2
-
Able to list shards
AWS_ACCESS_KEY_ID=x AWS_SECRET_ACCESS_KEY=x aws kinesis list-shards --stream-name my-local-stream --endpoint-url https://localhost:4567 --no-verify-ssl --region us-west-2 -
Able to get-shard-iterator
AWS_ACCESS_KEY_ID=x AWS_SECRET_ACCESS_KEY=x aws kinesis get-shard-iterator --stream-name my-local-stream --endpoint-url https://localhost:4567 --shard-id shardId-000000000000 --shard-iterator-type LATEST --no-verify-ssl --region us-west-2
- But getrecords is failing with error using the command
AWS_ACCESS_KEY_ID=x AWS_SECRET_ACCESS_KEY=x aws kinesis get-records --shard-iterator AAAAAAAAAAHhRrrEzLbhbcycTaMQr2iQH60Tg9tYdn0O48pVojEYJaoVhgzvg/2RqTIsh3Mkivheu8Wh2/KpwIAMO0AzhoiN+QMaAGTgeSnL+YooQoHP/lzaSFhfLDmAE+2b+7BoWCiykcQSsrwnTSpcdh83Jcpx3RDTXqZyGPq3jTa6eGj+U2QEvmH7bixbSnAby0bV1tTLI4nRFfebox9MlY+3mFF4 --no-verify-ssl --region us-west-2
I deleted my local aws configuration and reconfigured it and I tried most options like adding session token and security token but nothing works :(
Any idea how to may this work?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked docker-compose.yml and compare the working create-stream, put-record, and get-shard-iterator commands with the failing get-records command. Reproduce the setup using the exact AWS CLI commands and determine why the shard iterator is rejected; done means documenting or implementing a working get-records path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, docker, docker-compose, shell
- Domain
- cloud, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100