Hi Ranjeet,
As noted in these instructions, if your data and journal files are on a single EC2 volume (i.e. the default install) you can take a consistent backup using the standard ec2-create-snapshot without pausing your database writes.
If you are using MongoDB 3.0 with the WiredTiger storage engine, there is an important caveat that hasn't been added to the EC2 instructions yet: using db.fsyncLock() for backups is not currently supported for the WiredTiger storage engine as there is no guarantee the data files will not change. The documentation for filesystem/snapshot backups is currently being updated with more specific instructions for WiredTiger:
DOCS-5710.
There's also an open improvement (currently targeted for the MongoDB 3.2 production release) that you can watch/upvote:
SERVER-18899.
Regards,
Stephen