-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
how to create cloudwatch log messages to the streams using troposphere #2054
Comments
The only 2 AWS resources are log group and log stream. |
Ok thank you.We don’t have any option in troposphere to publish them?
Thanks,
Kala
…On Fri, Jun 10, 2022 at 5:01 PM John Preston ***@***.***> wrote:
The only 2 AWS resources are log group and log stream.
To publish messages to cloudwatch you will need to publish these yourself
/ via a service publishing to a log stream.
—
Reply to this email directly, view it on GitHub
<#2054 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMYSXCRPJTDREOVHVXV4C53VOO3NLANCNFSM5YO5MUXQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Can we use boto3 inside troposphere to generate messages in log group
Need suggestion and sample how to use boto code in troposphere.
Thanks,
Kala
On Sat, Jun 11, 2022 at 8:30 AM KALAVATHI YALAMANCHALI <
***@***.***> wrote:
…
Ok thank you.We don’t have any option in troposphere to publish them?
Thanks,
Kala
On Fri, Jun 10, 2022 at 5:01 PM John Preston ***@***.***>
wrote:
> The only 2 AWS resources are log group and log stream.
> To publish messages to cloudwatch you will need to publish these yourself
> / via a service publishing to a log stream.
>
> —
> Reply to this email directly, view it on GitHub
> <#2054 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AMYSXCRPJTDREOVHVXV4C53VOO3NLANCNFSM5YO5MUXQ>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
By a Custom Cloudformation object, and using an IAM role, you can create CloudFormation resources that execute any kind of supported Lambda function code to do what CloudFormation cannot do natively. For example, if you wanted to populate an S3 bucket with folders in CloudFormation, you would need to use a Custom CloudFormation object for this, because this action is not supported natively. The lambda will ingest the attributes from the custom object as variables, and you will write the code in the lambda to use it. I cannot share the code we use in my org, but below is a rough outline of what you need to do. You will need to tailor the IAM permissions and Lambda code to do what you need to do (note: there are placeholder vars in the below snippets).
|
No description provided.
The text was updated successfully, but these errors were encountered: