- Le plus récent
- Le plus de votes
- La plupart des commentaires
Hi there, Thank you for sharing the link and more information and i see exactly what you see. My recommendation is to use steps defined in https://docs.aws.amazon.com/systems-manager/latest/userguide/quick-setup-config.html to setup config recording across multiple regions and accounts. And then use https://aws.amazon.com/blogs/mt/org-aggregator-delegated-admin/ blog to Set up an organization-wide aggregator in AWS Config using a delegated administrator account. This should help with your use case.
Please let us know how it goes after following these steps. If this resolves your problem, please accept the answer.
Thanks, Yogesh
Here is the link https://docs.aws.amazon.com/organizations/latest/userguide/orgs_integrate_services.html
I get the same message prompt when I attempt to enable Trusted access from AWS Organizations.
I dont know how to enable this from AWS Service like Config. If I try to override the message and still enable the Trusted access from AWS Organizations, then any rule built on master account is not getting replicated to member accounts.
This is the exact message from AWS Organizations console-
We recommend that you enable trusted access by using the Amazon Config console. Enabling trusted access through the Amazon Config console enables that service to complete additional setup tasks that might be required.
Then below this, there is a checkbox to bypass this message--- Show the option to enable trusted access for Amazon Config without performing additional setup tasks.
Has anybody else seen this issue? I tried everything but unable to get this work
Contenus pertinents
- demandé il y a un an
- demandé il y a 2 mois
AWS OFFICIELA mis à jour il y a 2 ans- AWS OFFICIELA mis à jour il y a 3 ans
- AWS OFFICIELA mis à jour il y a 4 ans
Hi there, can you share the link to the documentation and the note which says "AWS recommend to enable trusted service from AWS Config service and not from AWS Organizations"