Question

A developer is building a serverless application with AWS SAM. The SAM template declares a parameter named Stage that controls resource naming and environment-specific settings. The developer wants to build the application, package artifacts, and deploy to a test environment in one workflow, while persisting deployment settings (stack name, S3 bucket, region, and the Stage=test parameter value) so subsequent deployments do not require re-entering them interactively. Which approach accomplishes this with the least ongoing effort?

Accepted Answer

Run 'sam build' followed by 'sam deploy --guided' once to answer the prompts and save answers to samconfig.toml, then use 'sam deploy' for later deployments.

Answer

Run 'sam local invoke' to test, then manually upload the packaged template to S3 and create the stack with 'aws cloudformation create-stack' each time.

Answer

Run 'sam package' and store the parameter values as environment variables, passing them via '--parameter-overrides' on every 'sam deploy' invocation.

Answer

Hard-code the Stage value directly in the template's Resources section so no parameters are needed, then run 'sam deploy' without arguments.