Contact Details

No response

What happened?

Update Container Runtime Logic, Pending Fix Week of November 8, 2021.

Version

0.0.1

Relevant Log Output

No response

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

Contact Details

What happened?

I have provisioned the infra and added a couple of devices running ubuntu linux servers. Added the device to dynamoDB using Ottr API and the below payload

data = { "system_name": "d5.xxxx-prod.com", "common_name": "d5.xxxx-prod.com", "certificate_authority": "lets_encrypt", "data_center": "AWS", "device_model": "linux", "host_platform": "Ubuntu", "ip_address": "10.1.60.173", "os_version": "18.04", }

Cloudwatch event trigger scans the DynamoDB using the lambda, the output of which is attached to the report. After that there is no trigger of step function and creation of the certificate? Are the network devices the only supported use case or Ottr also manages Ubuntu/Linux certificates?

Version

v0.0.1

Relevant Log Output

timestamp,message
1637999047236,"START RequestId: 27429d6c-6e01-478d-95c2-a92cae8afc2b Version: $LATEST
"
1637999049733,"[INFO]	2021-11-27 07:44:09,733.733Z	27429d6c-6e01-478d-95c2-a92cae8afc2b	Scanned Table: {'Items': [
    {'origin': 'API', 'os_version': '18.04', 'device_model': 'linux', 'ip_address': '10.1.50.139', 'subject_alternative_name': ['d1.xxxx-prod.com'], 'common_name': 'd1.xxxx-prod.com', 'host_platform': 'Ubuntu', 'certificate_expiration': 'None', 'system_name': 'd1.xxx-prod.com', 'certificate_authority': 'lets_encrypt', 'data_center': 'AWS', 'certificate_validation': 'True'}, {
           {'origin': 'API', 'os_version': '18.04', 'device_model': 'linux', 'ip_address': '10.1.60.173', 'subject_alternative_name': ['d5.xxxx-prod.com'], 'common_name': 'd5.xxxx-prod.com', 'host_platform': 'Ubuntu', 'certificate_expiration': '2021-11-29T01:00:00', 'system_name': 'd5.xxxx-prod.com', 'certificate_authority': 'lets_encrypt', 'data_center': 'AWS', 'certificate_validation': 'True'}], 
           'Count': 3, 'ScannedCount': 3, 'ResponseMetadata': {'RequestId': 'RMSH4SHEHI2N9HVSBTSG1F1DM7VV4KQNSO5AEMVJF66Q9ASUAAJG', 'HTTPStatusCode': 200, 'HTTPHeaders': {'server': 'Server', 'date': 'Sat, 27 Nov 2021 07:44:09 GMT', 'content-type': 'application/x-amz-json-1.0', 'content-length': '1390', 'connection': 'keep-alive', 'x-amzn-requestid': 'RMSH4SHEHI2N9HVSBTSG1F1DM7VV4KQNSO5AEMVJF66Q9ASUAAJG', 'x-amz-crc32': '4200178217'}, 'RetryAttempts': 0}}
"
1637999049733,"[INFO]	2021-11-27 07:44:09,733.733Z	27429d6c-6e01-478d-95c2-a92cae8afc2b	Rotate Certificates: []
"
1637999049761,"END RequestId: 27429d6c-6e01-478d-95c2-a92cae8afc2b
"

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

Contact Details

No response

Background

Currently there's a heavy manual effort to configure the infrastructure especially around the API.

Description

Add a target in the Makefile to automate the configuration component in the infrastructure.

Alternative Solution

No response

Additional Context

Target Completion: Week of November 22, 2021

Code of Conduct

• [X] I agree to follow this project's Code of Conduct