AWS Codebuild can work inside or outside a VPC now, it used to be outside VPC only. If your VPC requires a proxy to access Internet, then you need to set it up properly in the Codebuild project, otherwise you may notice that the project is unable to output logs to CloudWatch (Here let's assume … Continue reading AWS CodeBuild has no CloudWatch logs
Month: February 2020
Use AWS Secret Manager to handle credentials
AWS Secret Manager is a great solution for secret management. It is similar to HarshiCorp Vault, but with better integrations with other AWS services, e.g. IAM, RDS, Redshift, DocumentDB. As illustrated above, I created a database in RDS and a credential in Secret Manager, then attached the credential to the database for dynamic reference. The … Continue reading Use AWS Secret Manager to handle credentials
/etc/sysconfig/clock is removed after yum update in Amazon Linux 2
Simple version: If you follow AWS guide Setting the Time for Your Linux Instance to use /etc/sysconfig/clock to configure the timezone in Amazon Linux 2, you may not be able to find it after a yum update. So the suggested way to adjust time is to use timedatectl. For example: sudo timedatectl set-timezone Australia/Sydney Detailed … Continue reading /etc/sysconfig/clock is removed after yum update in Amazon Linux 2
Migrate Confluence Data to AWS
Continue with my previous blog Customised Quick Start of Confluence Data Center on AWS. Now I have both my on-premise Confluence and AWS Confluence up and running. The next step is to migrate all existing data into AWS. Due to the large size of data, the migration should be an on-going process till the final … Continue reading Migrate Confluence Data to AWS
Refresh failure com.atlassian.jira.plugin.devstatus.provider.DataProviderRefreshFailure: Data Provider refresh failed with error code 400 and message – HTTP status 400
Have you seen this error in your Jira log? If so, then you are in the right place to solve it 🙂 2019-10-10 02:03:34,970 Caesium-1-4 ERROR ServiceRunner [c.a.j.p.devstatus.provider.DefaultDevSummaryPollService] Refresh failurecom.atlassian.jira.plugin.devstatus.provider.DataProviderRefreshFailure: Data Provider refresh failed with error code 400 and message - HTTP status 400 ] at com.atlassian.jira.plugin.devstatus.provider.DefaultCachingProviderHelper.refreshProvider(DefaultCachingProviderHelper.java:79) at com.atlassian.jira.plugin.devstatus.provider.DefaultDevSummaryPollService.handlePollingSuccess(DefaultDevSummaryPollService.java:69) at com.atlassian.jira.plugin.devstatus.provider.DefaultDevSummaryPollService.lambda$performPull$1(DefaultDevSummaryPollService.java:51) at com.atlassian.jira.plugin.devstatus.provider.source.applink.PollResult$PollResultSuccess.fold(PollResult.java:51) at com.atlassian.jira.plugin.devstatus.provider.DefaultDevSummaryPollService.performPull(DefaultDevSummaryPollService.java:47) … Continue reading Refresh failure com.atlassian.jira.plugin.devstatus.provider.DataProviderRefreshFailure: Data Provider refresh failed with error code 400 and message – HTTP status 400
Jackie Chen's IT Workshop 