Explanation:
The correct answer is A. This approach leverages CloudFormation's DefinitionSubstitutions property for the AWS::StepFunctions::StateMachine resource, allowing for the dynamic insertion of the API Gateway endpoint. This method is cost-effective because it utilizes native CloudFormation capabilities without requiring additional services or resources. Options B, C, and D involve storing the API endpoint in separate services (environment variables, Secrets Manager, or AppConfig), which adds unnecessary complexity and costs.
Ultimate access to all questions.
Which AWS CloudFormation configuration is the most cost-effective method for a state machine to reference an API Gateway endpoint post-deployment?
A
Using DefinitionSubstitutions for the AWS::StepFunctions::StateMachine to include the API endpoint.
B
Storing the API endpoint in an environment variable associated with the AWS::StepFunctions::StateMachine.
C
Utilizing AWS::SecretsManager::Secret to store and reference the API endpoint for the state machine.
D
Storing the API endpoint in an AWS::AppConfig::ConfigurationProfile for state machine reference.
No comments yet.