- 最新
- 最多得票
- 最多評論
Humm - seems like I was too impatient - as of this morning my time a set of configuration records have been delivered including changes from 12 hours ago- it seems it just took time for the AWS Config service to be fully active.
You can check cloudtrail events for accessdenied messages.
You will not necessarily see S3 data event failures. What you could see is KMS denied errors.
Can you provide a copy of your s3 policy, service linked role and Kms policy to clarify it’s accurate?
Thank you for the follow up.
Here is a snapshot of the AWS Config set up:
Here is the Cloudtrail log showing I created a new EC2 instance and not showing any errors:
And here is the AWS COnfig dashboard showing that it "saw" the events associated with the launching of the EC2 instance and indicating it had no errors in transmitting the information at that time:
Any suggestions?
相關內容
- 已提問 7 個月前
- AWS 官方已更新 1 年前
- AWS 官方已更新 3 年前
- AWS 官方已更新 3 年前
- AWS 官方已更新 3 年前