Bucket Not Found and Key Missing Errors in Custom Build Process about enhanced-document-understanding-on-aws HOT 6 CLOSED

@JuarezCulau , sorry to hear you are facing issues when trying to deploy. Have you tried the first option: using cdk deploy to see if it works?.

For option 2, Creating a custom build, are you deploying in the same account/ region where the buckets have been created. If it is cross-account, I think making the buckets public read might solve the problem.

from enhanced-document-understanding-on-aws.

@knihit Thank you for your suggestions. Using cdk deploy works great if it's not a custom build. If I use cdk deploy with a custom build, I encounter a different error during deployment. Instead of not finding a key file in the bucket, I receive an access denied error to the bucket. I have the necessary permissions to access and retrieve data from the buckets. Additionally, I noticed a warning during deployment that I believe might be related to this issue. It essentially states that the current credentials could not be used to assume a file-publishing-role but proceeds anyway.

Regarding the account/region, it’s the same. I may have misunderstood something in the build process. Are the steps I mentioned in the "To Reproduce" topic correct?

from enhanced-document-understanding-on-aws.

@JuarezCulau , I am not sure why you say its not a custom build. You can still customize the code and perform cdk deploy. Do you have a requirement to distribute it to another team. If you are deploying in your AWS account, IMO, the cdk deploy option should work for you. Unless you require to distribute artifacts to others, you dont have to use option 2.

For the error you mentioned access denied error to the bucket, have you run cdk bootstrap. When it states current credentials could not be used to assume a file-publishing-role can you provide details on what role you are currently using. Are you using a higher privilege role to deploy. If its your own account, I would suggest assuming an Adminstrator role to deploy the template. You can also specify cdk deploy --role-arn arn:aws:iam::01234567890:role/<role-with-adminstrator-access> to supply CloudFormation with an elevated role.

Me and my team uses cdk deploy during our development and we make modifications and keep deploying updates. I have not seen this error before with cdk deploy. Hence my hunch is that is probably due to the IAM policies that are associated with the user/ role you are using. Those don't have sufficient permissions.

from enhanced-document-understanding-on-aws.

Thanks for the information, I managed to make it work now.

from enhanced-document-understanding-on-aws.

@JuarezCulau thank you for letting us know. Just so that our team builds on troubleshooting guide, if you are comfortable sharing the root cause and final resolution which made it work.

from enhanced-document-understanding-on-aws.

@knihit It is actually very simple, I just didn’t know I had to bootstrap before deploying in CDK. Thanks for the info. I still can’t use the second option to use CloudFormation templates, but there is no need for me anymore since deploying with CDK is working.

from enhanced-document-understanding-on-aws.