Category: Cloud

Service Role for CodeBuild


Do you notice anything that is not right in the following CloudFormation template? ... Resources: CodeBuildServiceRole: # IAM role for the codebuild project. Type: AWS::IAM::Role Properties: RoleName: !Sub ${ProjectName}-CodeBuild-ServiceRole Path: /team-abc/ AssumeRolePolicyDocument: Version: "2012-10-17" Statement: - Action: ['sts:AssumeRole'] Effect: Allow Principal: Service: ['codebuild.amazonaws.com'] Policies: - PolicyName: !Sub ${ProjectName}-CodeBuild-Policy PolicyDocument: Version: "2012-10-17" Statement: - Action: # … Continue reading Service Role for CodeBuild →

`aws s3 sync` lessons learned


As mentioned in my earlier posts, we use aws s3 sync to migrate a large number of files from on-premise to AWS. Here are a few things that I learned: The AWS credential can be renewed by an external process for a long running AWS CLI process. (Renew AWS credential for a long run AWS … Continue reading `aws s3 sync` lessons learned →

Renew AWS credential for a long run AWS CLI process


We use aws s3 sync to synchronise a big mount of files (800,000+ objects) from on-premise to AWS S3 bucket. Due to security restrictions, the Maximum CLI/API session duration is configured for 1 hour. So it is most likely the credential will expire before the sync job is completed. There are generally two places to … Continue reading Renew AWS credential for a long run AWS CLI process →

Setup a Rolling Update Toggle for AWS Auto Scaling Group


Rolling update (handled by UpdatePolicy attribute) is a great feature in AWS Auto Scaling Group. With this feature, we are able to making changes without downtime. For example, replace existing instances one by one. By design, NOT every change of the Auto Scaling Group can trigger a rolling update. Only the changes made to LaunchConfigurationName, … Continue reading Setup a Rolling Update Toggle for AWS Auto Scaling Group →

Stale node ids should automatically be removed in Jira Data Center


Finally finally ... Atlassian takes action on this one since reported 5 years ago. As stated in the 8.10.x release notes, Jira 8.10.0 and later now is able to remove stale node automatically. We've introduced automation to your cluster maintenance. Now, you do not have to remove the offline nodes from your cluster manually, or … Continue reading Stale node ids should automatically be removed in Jira Data Center →