AWS CloudFormation and Elastic Transcoder - amazon-web-services

Does AWS CloudFormation allow creating templated for AWS Elastic Transcoder?
PS: I tried creating a DataPipeline, but no that is not the same as Transcoder pipeline

Not yet. The following page shows all available resource types for AWS Cloudformation:
http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-template-resource-type-ref.html

You could use a python lambda function wrapped in a custom resource. With Lambda support in custom resources, services/features not currently supported can be accommodated in the template.
This github project shows how
https://github.com/mazerte/aws-cloudformation-elastic-transcoder-pipeline

Related

What is the underlying mechanism that Terraform’s AWS Provider uses to provision resources in AWS?

Does it use AWS CloudFormation, the AWS CLI, or does it do something else like directly make AWS API calls without going through the CLI?
No, it not using the AWS CLI or cloud formation.
AWS terraform use the AWS SDK and here you can see the complete list of dependency for the AWS Terraform provider.
It also uses aws-sdk-go https://github.com/aws/aws-sdk-go
https://github.com/hashicorp/terraform-provider-aws

What AWS services use AWS lambda behind the scenes?

We were in the process of setting up AWS Config Rules and came across a bug in one of the AWS managed rules. During our conversation with the AWS support person, he has revealed that the AWS Config Rules are processed by AWS Lambda functions behind the scenes.
I am curious to know what other AWS services use AWS Lambda behind the scenes. For example, AWS Systems Manager documents.
Thanks for your time.
Not exhaustive list, but here are some more examples:
AWS::Include Transform which is a macro hosted by AWS CloudFormation, to insert boilerplate content into your templates.
AWS::Serverless Transform which is a macro hosted by AWS CloudFormation, takes an entire template written in the AWS Serverless Application Model (AWS SAM) syntax and transforms and expands it into a compliant AWS CloudFormation template
Secret Manager and its password rotation: If you use your secret for one of the supported Amazon RDS databases, then Secrets Manager provides the Lambda function for you. And Secrets Manager automatically customizes the function to meet the requirements of the specified database.

Using CloudFormation to configure Amazon Cognito Domain

I am using AWS Amplify in a React Native App. I set up my userpool with a domain via the console (https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-pools-assign-domain-prefix.html), but have to manually remove and re-install it every time I make a chance to the backend\auth\poolname-cloudformation-template.yml.
Is there a CloudFormation setting that would allow me to set it up through there?
Thanks!
This has been added to CloudFormation:
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-cognito-userpooldomain.html
Unfortunately, there is no Cloud Formation setting that allows to create an Amazon Cognito Domain. One work around for this is to create a Custom Cloud Formation resource backed by a Lambda and then creating the domain in Lambda through Boto 3.

Export existing AWS Lambda and API Gateway to Cloudformation template

How to export existing configured and tested infrastructure (including AWS Lambda functions, API Gateways, ElastiCache clusters, Cloudwatch rules) to Cloudformation template?
I know about Cloudformer tool, but it supports limited number of AWS services (Amazon VPC, DynamoDB, etc) and don't supports some of services which we use. Which tools and approaches can I use in my case for generating Cloudformation template?
Partial solution: there is ability to export Lambda function to AWS SAM file
and then
We will get YAML file which describes your Lambda function as 'AWS::Serverless::Function'. But there are few things - we can't export Lambda aliases with such approach. Also that doesn't help with API Gateway exporting.
CloudFormer was built for this, however, I agree with #MaiKaY that you should rewrite everything. CloudFormer will create hard-links with IDs, where you have to replace these with references, add parameters and/or mappings. It can help you get started, so you know what you need in the template.

How to create OpsWorks users using CloudFormation?

I am trying to create a CloudFormation template that deploys my OpsWorks stack and layers and some other AWS resources. I would like to manage the users of my OpsWorks instances using the Permissions feature they offer.
I have been able to manage those users using the UI and the CLI, however I cannot find anywhere how to that with CloudFormation. I have been reading through the documentation and it seems there is no resource specified for it. Does CloudFormation not have access to all resources in the AWS APIs?
CloudFormation doesn't support OpsWorks user. But it's still possible, you can use CloudFormation custom resource to create opsworks user: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/template-custom-resources.html