Which solution will meet these requirements?
Use AWS Organizations to set up the infrastructure. Use AWS Config to track changes.
Use AWS CloudFormation to set up the infrastructure. Use AWS Config to track changes.
Use AWS Organizations to set up the infrastructure. Use AWS Service Catalog to track changes.
Use AWS CloudFormation to set up the infrastructure. Use AWS Service Catalog to track changes.
Explanations:
AWS Organizations helps manage multiple AWS accounts, but it does not track infrastructure changes. AWS Config is useful for tracking changes but is not directly tied to the infrastructure setup in this scenario.
AWS CloudFormation allows for infrastructure automation and enables the tracking of changes through AWS Config, which monitors resource configurations and changes. This meets the requirement of securing and auditing incremental changes.
AWS Organizations helps manage accounts but does not directly track infrastructure changes. AWS Service Catalog is for managing approved services and configurations, not for tracking infrastructure changes.
AWS CloudFormation helps automate infrastructure setup, but AWS Service Catalog is not designed to track incremental changes to infrastructure. It is used to manage predefined sets of resources.
I surmise that the answer is:
Use AWS CloudFormation to set up the infrastructure. Use AWS Config to track changes.