This command is useful for discovering when a change was made and by whom.
If you include --file, --user, or --date, the revision number is suppressed unless you also include --number.
So the change sets "outgoing" from the stream to the snapshot wouldn't be the list you're looking for.
Since your change doesn't exist in the stream, it won't show up as outgoing in the report.
When the update set is completed, you can transfer the update set to another instance according to your test process. Note: Properties that are tagged as Private are excluded from update sets.
AWS Cloud Formation doesn't make changes until you execute the change set.
The archive type is automatically detected based on file extension (to override, use -t/--type). Each member added to an archive file has a directory prefix prepended.
Use -p/--prefix to specify a format string for the prefix.
Because AWS Cloud Formation doesn't know the database was deleted, it assumes that the database instance still exists and attempts to roll back to it, causing the update rollback to fail.
See also: AWS API Documentation Request Syntax Creates a list of changes that will be applied to a stack so that you can review the changes before executing them.