2 Respostas
- Mais recentes
- Mais votos
- Mais comentários
0
Hi there, I'm sorry to hear you're running into these issues. The exception that is raised indeed indicates an issue with the IAM permissions. Can you double check that
- your user has the IAM policy AmazonBraketFullAccess (arn:aws:iam::aws:policy/AmazonBraketFullAccess) attached
- [if you use Braket notebooks] your notebook has an IAM role starting with AmazonBraketServiceSageMakerNotebook attached (alternatively, you can automatically create a new role when you create the notebook)
- [if you use Hybrid Jobs] each job has the IAM role AmazonBraketJobsExecutionRole attached.
You can find more information here: https://docs.aws.amazon.com/braket/latest/developerguide/braket-manage-access.html
Please keep us posted if this works.
respondido há um mês
0
Hey All,
If you are still experiencing this permissions issue, the following three steps will help you create a ticket to our support team. They will be able to get this resolved for you.
- Login to your AWS Management Console
- Once logged in, create a case by visiting the Support Center (https://support.console.aws.amazon.com/support/home)
- When prompted for the details, use the following routing path
respondido há um mês
Conteúdo relevante
AWS OFICIALAtualizada há 2 anos
Code-snipet- # This cell should take about 5 mins job = AwsQuantumJob.create( device=Devices.Amazon.SV1, source_module="algorithm_script.py", wait_until_complete=True, )
I am still getting the error message, AccessDeniedException: An error occurred (AccessDeniedException) when calling the CreateJob operation: This account is not authorized to use this resource. In order to access additional resources, please contact customer support. I have tried creating new users, but no use. Tried running from AWS CLI from my local drive with api call, still gives the same error. My user already has the following roles and policies assigned - AdministratorAccess, AmazonAPIGatewayAdministrator, AmazonBraketFullAccess, AmazonBraketJobsExecutionPolicy, AmazonS3FullAccess. Gives the same error even when running from the root account.
Thanks for the additional detail. The best next step is to cut a ticket (see Zia's instructions in the other answer) so our support team can take a closer look.