Thanks for your comment. An alias must be (re-created) when there are changes that require preparing, so the agent resource and the null resource for preparing action group changes should be added to depends_on for the alias resource. Furthermore, the alias must be re-created upon changes to the above. So you may need to use the replace_triggered_by meta-argument to force re-creation based on changes to the agent and the null resource's ID. I've not yet tried this myself but see if this works.

Thanks for your message. You are right that off-hour ingestion is more of a blanket statement, as it really depends on the usage pattern, the type of data, and the complexity of the ingestion pipeline. It's more of an art than a rule, and I've not seen AWS reference that provides substantial guidance yet. So far I've worked on a few RAG system (not exclusively on AWS) with relatively static data which can afford scheduled ingestion. But I've not had the opportunity to work on one with real-time ingestion requirements just yet. I know of the Bedrock KB streaming data ingestion feature that was announced in re:Invent 2024, but have not had a chance to experiment with it. Would be interesting to see how this changes things.

Hello, thanks for your message. I don't have plan to add support for return control yet, but I've opened an issue in GitHub to track it. I will however add support for guardrail in the coming days if you are also interested.

Hi Alden Quimby , thanks for your message. If you have an organization that wasn't created as part of Control Tower, you can follow the Organization Based Aggregation example in https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/config_configuration_aggregator#organization-based-aggregation to set it up. The AWS blog post https://aws.amazon.com/blogs/mt/aws-organizations-aws-config-and-terraform/ also provides more information on this topic. Hope this helps.

Thanks for your comment! This new argument is only part of the solution, as changes to action groups still requires a PrepareAgent call. There is also a similar case with knowledge base attachments. Nonetheless it's a good idea to add the argument so there's one less dependency - I'll update the blog post and code example soon. Hopefully I can get to adding similar arguments to the action group and KB resources, unless there are takers :)