-
Notifications
You must be signed in to change notification settings - Fork 5
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
Feature/skinny eliza/feb10 #18
base: feature/tine-devops-variables
Are you sure you want to change the base?
Feature/skinny eliza/feb10 #18
Conversation
|
|
|
chore: commit d.a.t.a env configurations
Update readme to clarify difference between eliza-starter and eliza repos
docs: add note about 0x prefix needed for evm private key
chore: client/FAQ/Character file Docs update
chore: update change log
…e-storage fix: Store stringKnowledge in knowledge when ragKnowledge is enabled (elizaOS#3434)
docs: fix incorrect image paths in Korean documentation
2b31fbe
to
df0562c
Compare
easy to fix |
|
[Container] 2025/02/16 17:24:31.738691 Phase context status code: Decrypted Variables Error Message: AccessDeniedException: User: arn:aws:sts::767503528736:assumed-role/github-runner-codebuild-eliza-build/AWSCodeBuild-6b1a8659-f132-4c5c-87d6-0315f3bc2677 is not authorized to perform: ssm:GetParameters on resource: arn:aws:ssm:us-east-2:767503528736:parameter/tine_agent_2_agent_image because no identity-based policy allows the ssm:GetParameters action This response might contain information related to security, a nuanced topic. You should verify the response using informed human judgement. Visit Security in Amazon Q Developer for more details. Based on the error message you're encountering, it appears that your CodeBuild project is trying to access a parameter in AWS Systems Manager Parameter Store, but the IAM role associated with your build doesn't have the necessary permissions. Let's address this issue step by step:
If you continue to experience issues after implementing these changes, please review your CodeBuild project configuration and ensure that it's using the correct IAM role. If problems persist, consider checking AWS CloudTrail logs for more detailed information about the access attempts. |
generated from aws for the new role
|
rebase