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

AWS Cloud Formation failing with 403 s3 forbidden error #35

Open
maheshcheetirala opened this issue Jul 8, 2021 · 6 comments
Open

AWS Cloud Formation failing with 403 s3 forbidden error #35

maheshcheetirala opened this issue Jul 8, 2021 · 6 comments

Comments

@maheshcheetirala
Copy link

maheshcheetirala commented Jul 8, 2021

Hello Developers,
After creating the initial template and launching a project with sage maker studio project launch is failing saying cloud formation failed when i saw the error it says 403 forbidden s3 error I have given full s3 access and admin access to the role but still same issue, changed the s3 bucket name all possible solutions. Even tested in different vpc all those giving same error. can someone please run the template from your end and help us with possible solution. Role is given admin access as well.

@brightsparc
Copy link
Contributor

Hi @maheshcheetirala, I assume you are referring to the stack with the SC- prefix that is created by SageMaker Studio with a new project.

  • Can you confirm which region you are running the stack in - US East (N. Virginia) us-east-1?
  • Can you also confirm you provided a valid email address for notifications?

@maheshcheetirala
Copy link
Author

maheshcheetirala commented Jul 13, 2021 via email

@brightsparc
Copy link
Contributor

Hi @maheshcheetirala are you getting this error when using the bash command? I have tested Launch Stack to create a new CFN in us-east-1 and I had no issues. Please provide some more detail with specific error message that are you seeing so I can debug further.

@maheshcheetirala
Copy link
Author

maheshcheetirala commented Jul 16, 2021 via email

@samadwar
Copy link

I had same issue, check that your IAM role have CloudFormation in it's trust policy

@durgasury
Copy link

If people are still facing this issue -
the "Launch Stack" button refers to a template that is missing this line that gives the ServiceCatalogLaunch role access to the bucket with seed code.

To resolve, either pull the template from the repo to create the stack, or if you already have the stack created, go to the AmazonSageMakerServiceCatalogProductsLaunchRole role in your IAM, and give it permissions to the s3 bucket amazon-sagemaker-safe-deployment-pipeline*.

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