Create Cloudformation templates

You should find all necessary reference if you search google for the following individually AWS::Glue::Table AWS::KinesisFirehose::DeliveryStream We are specifically looking for a CloudFormation template that defines the resources we need. The primary reason for this is repeatability, so you or I can create / restore resources if things should change or disaster strikes. Essentially CloudFormation performs the same actions internally that we would perform on the UI. The only difference really is that we only specify the resource we want, not the path to creation. And we have a concrete record of the resource configuration. (edited) Try these links: [login to view URL] [login to view URL] Need a developer who can create as following. # Athena/Firehose Cloudformation Templates Create Cloudformation templates that will generate the following assets as described. Assets belong to a specific business object. In this case, we are focusing on an "Impression". Data will flow from Kinesis Firehose to an S3 location, where the Athena table will point. ### Create Athena table - Partitions will be based on Kinesis Firehose's default output format, YYYY/MM/dd/HH - Use the following schema: "Impression" | field name | type | | ----------------- | --------------------------------------- | | publicationId | int | | publisherId | int | | placementId | int | | itemIndex | int | | advertiserId | int | | campaignId | int | | orderId | int | | creativeId | int | | emailAddressMd5 | string | | emailDomain | string | | decisionTimestamp | unix timestamp (int) | | timestamp | unix timestamp (int) | | ingestdatetime | string (this will be the partition key) | ### Create corresponding AWS Kinesis Firehoses. - Firehose should convert JSON to Parquet. - Create Glue definitions as needed. - Firehose should deliver data to an S3 location, using the default partitions - Should be written as a single Cloudformation template with multiple resources - Template should be parameterized with options for multiple environments. In this case we have 2 environments `Dev` and `Prod`. Any mappings should use the provided environments and proper casing. - The only required parameter shall be `Environment` and again the allowed values are `Dev` & `Prod`. - Please use YML - Finally the template should output the kinesis firehose endpoint url.