aws-well-architected-labs icon indicating copy to clipboard operation
aws-well-architected-labs copied to clipboard

Level 300_optimization_data_collection core infra fails with glue permissions error

Open jmstone617 opened this issue 2 years ago • 2 comments

I'm following the guide here and when deploying the stack for data retrieval in the optimization account, the nested stacks fail with an error like

Account {optimization acct number} is denied access. (Service: AWSGlue; Status Code: 400; Error Code: AccessDeniedException; Request ID: {slug}; Proxy: null)

I was able to successfully deploy the stacks in the Management Account in the prior steps, so not sure if there's a missing permission or something else I failed to do in another set of pre-reqs. I don't know why Glue within the optimization account would have permissions denied since I am using an account with permissions to manage Glue.

jmstone617 avatar Oct 03 '22 19:10 jmstone617

Hello Which nested falls? Please double check your parameters and make sure you use cost account Id and managed account id correctly.

iakov-aws avatar Oct 03 '22 20:10 iakov-aws

They all fail. This template only asks for management account Id which I’ve confirmed is correct. I’m executing it in the optimization collection account using an admin role.

On Oct 3, 2022 at 2:31 PM -0600, Iakov GAN @.***>, wrote:

Hello Which nested falls? Please double check your parameters and make sure you use cost account Id and managed account id correctly. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>

jmstone617 avatar Oct 04 '22 01:10 jmstone617