Skip to content
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

AWS::Logs::LogGroup GovCloud #403

Closed
bgardner-noggin opened this issue Mar 1, 2020 · 8 comments
Closed

AWS::Logs::LogGroup GovCloud #403

bgardner-noggin opened this issue Mar 1, 2020 · 8 comments
Labels
regional parity Coverage isn't available in all regions a service is

Comments

@bgardner-noggin
Copy link

1. AWS::Logs::LogGroup

2. Scope of request

Should be able to use AWS::Logs::LogGroup in GovCloud regions

3. Expected behavior

In GovCloud, using this resource type errors with "resource type not available"

6. Category (required) - Will help with tagging and be easier to find by other users to +1

  1. Management (CloudTrail, Config...)
@PatMyron PatMyron added the regional parity Coverage isn't available in all regions a service is label Mar 2, 2020
@PatMyron
Copy link
Contributor

PatMyron commented Mar 2, 2020

minimal AWS::Logs::LogGroup template for testing:

Resources:
  LogGroup:
    Type: AWS::Logs::LogGroup

@PatMyron
Copy link
Contributor

PatMyron commented Mar 2, 2020

@bgardner-noggin we were able to successfully create AWS::Logs::LogGroup in both us-gov-east-1 or us-gov-west-1. Which GovCloud region(s) were you experiencing this in? Are you still experiencing this? Are you using anything to deploy your CloudFormation template that might be throwing this error before calling CloudFormation itself? Could you share template snippets to reproduce?

@bgardner-noggin
Copy link
Author

I was using the registry to detect types.

aws cloudformation --region us-gov-west-1 describe-type --type RESOURCE --type-name AWS::Logs::LogGroup

fails in both us-gov-west-1 and us-gov-east-1 with the message

An error occurred (TypeNotFoundException) when calling the DescribeType operation: The Resource Type 'AWS::Logs::LogGroup' cannot be found.

I've since discovered the registry is not accurate and cannot be relied upon. eg in ap-southeast-2, the "AWS::EC2::VPCEndpointConnectionNotification" is listed as not available, yet works fine in a cloudformation template

@PatMyron
Copy link
Contributor

PatMyron commented Mar 3, 2020

@bgardner-noggin Ah, that makes more sense. Thanks for the details

Might be the same underlying issue as resource types that are lagging in CloudFormation Resource Specifications

This should diminish over time as resource types are migrated to natively use the CloudFormation Registry. There are some resource types left still using older frameworks

@cmckni3
Copy link

cmckni3 commented May 26, 2020

Ran into this issue back in December as well. AWS::Logs::LogGroup does not appear in the CloudFormation Registry on GovCloud but does actually work in CloudFormation templates (with caveats).


LogGroupName results in an invalid template error

Template contains errors.: Invalid template resource property 'LogGroupName'


RetentionInDays results in an invalid template error.

Template contains errors.: Invalid template resource property 'RetentionInDays'


https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-logs-loggroup.html

I have been using a custom resource since then due to these limitations.

@manoj-bandara
Copy link

I am getting errors for LogGroupName and RetentionInDelays. When can we get a fix

@rgd11
Copy link

rgd11 commented Dec 31, 2021

AWS::Logs::LogGroup is missing the following properties in the GovCloud spec (https://s3.us-gov-west-1.amazonaws.com/cfn-resource-specifications-us-gov-west-1-prod/latest/CloudFormationResourceSpecification.json):

  • KmsKeyId
  • Tags

@jej2003
Copy link

jej2003 commented Jun 28, 2022

Is there a cadence that details when these updates get pushed to GovCloud?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
regional parity Coverage isn't available in all regions a service is
Projects
None yet
Development

No branches or pull requests

7 participants