Amazon CloudFormation templates are widely used in the AWS cloud for environment creation by the IT and application teams. We have been helping enterprises with Amazon CFT based automation for years and following are some of the best practices to follow while creating Amazon CFT Templates Practice #1: Version your CloudFormation templates Practice #2: Use input parameters Practice #3: AMI ID should be a parameter in inputs section Practice #4: Mention the AMI mappings Practice #5: Use WaitConditionHandle, WaitCondition, DependsOn wherever applicable Practice #6: Tag the resources properly Practice #7: Understand your Resources Practice #8: Create your Security groups using CFT Practice #9: Include the Output Section.
by Vikram Pillai Introduction Does your organization have more than one Amazon Web Services account? Do you have standalone accounts that are not linked to a consolidated billing account? Or more than one consolidated billing account? If so, you are not alone. Due to the incremental and distributed adoption of AWS across enterprises, many IT departments are struggling with AWS account complexity that is impeding them from taking back control of the cost and usage of their cloud infrastructure.
Art of Architecting scalable ElastiCache Redis Tier using twemproxy to support billions of messages per day. the ElastiCache Redis tier was designed with Partitions( shards) to scale out as the customer grows the ElastiCache Redis tier was designed with Replica Slaves for HA and read scaling as the read volumes grow.In this article i am going to share my experience on designing large scale Redis tiers supporting billions of messages per day on AWS, step by step guide on how to deploy the same, what are the Implications you face at scale ? Best Practices to be adopted while designing sharded+replicated Redis Tiers etc.