Which solution will meet these requirements?
Use the AWS SAM CLI to package and deploy the SAM application to the pre-production AWS account. Specify the debug parameter.
Use the AWS SAM CLI to package and create a change set against the pre-production AWS account. Execute the change set in a new AWS account designated for a development environment.
Use the AWS SAM CLI to package and deploy the SAM application to a new AWS account designated for a development environment.
Update the CloudFormation stack in the pre-production account. Add a separate stage that points to a new AWS account designated for a development environment.
Explanations:
Using the AWS SAM CLI to package and deploy directly to the pre-production account would impact the existing application, as changes would be applied to the current stack.
Creating a change set against the pre-production account would still involve making changes to that account, potentially affecting the running application. Executing the change set in a new AWS account designated for development is not feasible since the change set needs to be associated with the existing stack in the pre-production account.
Packaging and deploying the SAM application to a new AWS account designated for a development environment allows the developer to test the changes without impacting the existing pre-production application. This is the safest option for a one-time deploy of changes for testing.
Updating the CloudFormation stack in the pre-production account would affect the currently running application. Even if a separate stage is created, the action still applies to the existing stack, which the developer wants to avoid.
I reckon the answer is:
Use the AWS SAM CLI to package and deploy the SAM application to a new AWS account designated for a development environment.
From what I’ve seen, the answer is:
Use the AWS SAM CLI to package and deploy the SAM application to a new AWS account designated for a development environment.