Endpoint policies for gateway endpoints


The Cloud Conformity VPC Endpoint Exposed check brought my attention to this one, as I think they have a bug in this check: https://www.cloudconformity.com/knowledge-base/aws/VPC/endpoint-exposed.html There are two types of VPC endpoint: Interface and Gateway (S3, DynamoDB). What are suggested in the above link only applies to the Interface endpoint, but not the Gateway endpoint. As … Continue reading Endpoint policies for gateway endpoints

Confluence system plugins that do not support cluster environment


If you are doing the following Confluence migration, you have to be aware of that some system plugins do not support cluster environment. Confluence server to Confluence data center clusterConfluence data centre non-clustered (single node) to Confluence data centre clustered (multiple nodes) A simple example is the 'Confluence Usage Stats' which provides the macros like … Continue reading Confluence system plugins that do not support cluster environment

Use Git Workflow to Manage Multiple AWS Environments


Managing multiple AWS environments (sandbox/dev/uat/stage/prod) is challenging, as it is hard to keep track of the current status of each environment. For example, user A deploys his feature branch into dev to test his code, then later user B deploys his hotfix branch into dev to test his code. This can cause many issues: User … Continue reading Use Git Workflow to Manage Multiple AWS Environments

Automate Atlassian Add-on Management Part Two


Continue with Part One, let me list some requirements that I would like to keep in the scope: Must Have Plugins metadata (application, version, desired_state...) is source controlled.Can query plugins information (version, license, expiry date...) from servers.Can query plugins information from Atlassian Market place.Can enable/disable plugins.Can install/uninstall plugins.Can update plugins.Can check compatibility. Should Have Can … Continue reading Automate Atlassian Add-on Management Part Two