Managing Application Lifecycle using Jira and Bitbucket Cloud and AWS Tooling
1 like7,454 views
The document discusses managing application lifecycle using Jira, Bitbucket Cloud, and AWS tools, emphasizing the importance of Enterprise Service Management (ESM) in enhancing customer experience through collaboration and streamlined processes. It outlines solutions such as Atlassian Connector and Bitbucket Pipes to integrate AWS services for continuous delivery and deployment, facilitating better tracking of issues and releases. The presentation concludes with a call to action for engaging in workshops and discussions regarding the content presented.
![AWS Fargate
Deploy Pipe
Setup
Task Definition
Create a task definition
{
"family": "sample-application",
"networkMode": "awsvpc",
"containerDefinitions": [
{
"name": "sample-application",
"image": "${ECR_REPOSITORY_REF}",
"portMappings": [
{
"protocol": "tcp",
"containerPort": 80,
"hostPort": 80 } ],
"logConfiguration":
{
"logDriver": "awslogs",
"options":
…
task-definition.json:](https://image.slidesharecdn.com/1030-1110admin-bs6-yerasrissiv1-190411222828/85/Managing-Application-Lifecycle-using-Jira-and-Bitbucket-Cloud-and-AWS-Tooling-19-320.jpg)
![- step:
name: deploy services to stg
script:
-pipe: aws-labs/aws-fargate-deploy:0.2.0
variables:
AWS_ACCESS_KEY_ID: ‘${AWS_ACCESS_KEY_ID}’
AWS_SECRET_ACCESS_KEY: ‘${AWS_SECRET_ACCESS_KEY}’
AWS_ACCOUNT_ID: ‘${AWS_ACCOUNT_ID}’
AWS_DEFAULT_REGION: ‘us-east-1’
ECS_SERVICE_NAME: ‘sample-app’
ECR_REPOSITORY_URI: ‘${AWS_REGISTRY_URL}’
ECS_CLUSTER_NAME: ‘default’
VPC_SUBNETS: ‘’subnet-12345677’, ‘subnet-12345678’’
AWS_SECURITY_GROUPS: ‘sg-012b1ade1234578c’
AWS_ELB_TARGET_GROUP_ARN: ‘${AWS_ELB_TARGET_GROUP_ARN}
ECS_CONTAINER_PORT: ‘80’
ECS_CONTAINER_NAME: ‘sample-app’
DESIRED_COUNT: ‘1’
DEBUG: ‘true’
CURRENT PIPE
- step:
name: deploy services to stg
image: atlassian/pipelines-awscli:latest
deployment: test
script:
- export ECS_TASK_NAME="${BITBUCKET_REPO_SLUG}"
# register the ECS task definition and capture the version
- export TASK_VERSION=$(aws ecs register-task-definition
--family "${ECS_TASK_NAME}"
--networkMode "awsvpc”
--requires-compatibilities “fargate”
--container-definitions ‘[{
"name":"app",
"image":"'"${IMAGE_NAME}”’”,
"memory":1024,
}]’ | jq --raw-output '.taskDefinition.revision’)
- echo "Registered ECS Task Definition: " $TASK_VERSION
# ECS variables
- export ECS_CLUSTER_NAME="${BITBUCKET_REPO_OWNER}"
- export ECS_SERVICE_NAME="${BITBUCKET_REPO_SLUG}"
…](https://image.slidesharecdn.com/1030-1110admin-bs6-yerasrissiv1-190411222828/85/Managing-Application-Lifecycle-using-Jira-and-Bitbucket-Cloud-and-AWS-Tooling-21-320.jpg)
Managing Application Lifecycle using Jira and Bitbucket Cloud and AWS Tooling
- 1. Managing Application Lifecycle using Jira and Bitbucket Cloud and AWS Tooling CURTIS RISSI | SENIOR SOLUTIONS ARCHITECT | AMAZON WEB SERVICES JAY YERAS | SPECIALIST SOLUTIONS ARCHITECT | AMAZON WEB SERVICS
- 3. Problem Space Why is Enterprise Service Management (ESM) so important?
- 4. Cloud is the new normal
- 5. It’s all about the Customer! Delighting customers through swift actionable and informed responses is critical to your business.
- 7. Steps to successful adoption Change behaviors Remove hierarchy Define processes All parts of the organization need to learn to work together to deliver customer delight. Hierarchical structures result in barriers to collaboration. Create broad clear guidelines across the entire organization that extend beyond specific departmental perspectives.
- 8. Tracking Issues If you're release process exist entirely in Atlassian products like Bitbucket Cloud, Bamboo and Jira, this is straight forward process. But what if parts of it exists or is executed in other services or platforms, such as AWS CodeBuild or AWS CodePipeline?
- 10. Atlassian Connector Integration to AWS CodePipeline and AWS CodeBuild
- 11. AWS Cloud getCommit function AWS CodeBuild AWS CodeCommit AWS CodePipeline VPC Public Subnet Availability zone 1 Atlassian Connect App getState function AWS Fargate Network Load Balancer Event (event-based) Amazon CloudWatch AWS Lambda Certificate AWS Certificate Manager AWS Secrets Manager RegistryImage Task Service Amazon EC2 Container Registry Request token Return token Git push Build and store artifacts Issue certificate Listener: tcp 443 Deploynewimage QueryCode*APIs POST
- 13. AWS Cloud Amazon ECR Lambda functions Registry Image Task Service AWS Cloud9 AWS CodeBuild AWS CodeCommit AWS CodePipeline AWS CLI AWS CloudFormation1 2 3 4 Git Users AWS Samples Git Repository Fork Clone AWS Fargate Fully managed Docker container registry Managed service for running containers Fully managed continuous delivery service Serverless compute service AWS Lambda
- 15. Bitbucket Pipes Integration to AWS Fargate
- 16. We have a few goals for creating our Pipe Increase Quality Simplify the deployment process to provide consistency and reduce regressions. Aid Reuse Pipes simplify and abstract complexity out of each stage of your pipeline. Use Best Practices Pipes enable you to leverage the collective best practices of the community.
- 17. AWS Fargate Deploy Pipe Setup Prerequisites Complete your prerequisites In order to get started, you’ll need to ensure you have done the following: Created an AWS Account Created an Amazon ECR repository Uploaded your applications docker image to your repository 1 2 3 A complete list of prerequisites (including optional tasks) can be found in the pipes readme.
- 18. AWS Fargate Deploy Pipe Setup Variables Setup your repository variables
- 19. AWS Fargate Deploy Pipe Setup Task Definition Create a task definition { "family": "sample-application", "networkMode": "awsvpc", "containerDefinitions": [ { "name": "sample-application", "image": "${ECR_REPOSITORY_REF}", "portMappings": [ { "protocol": "tcp", "containerPort": 80, "hostPort": 80 } ], "logConfiguration": { "logDriver": "awslogs", "options": … task-definition.json:
- 20. AWS Fargate Deploy Pipe Setup Pipe Setup Setup the pipe For this, we just need to add the pipe configuration to a step within our bitbucket-pipeline.yml file. - step: name: deploy services to stg script: -pipe: aws-labs/aws-fargate-deploy:0.2.0 variables: AWS_ACCESS_KEY_ID: ‘${AWS_ACCESS_KEY_ID}’ AWS_SECRET_ACCESS_KEY: ‘${AWS_SECRET_ACCESS_KEY}’ AWS_ACCOUNT_ID: ‘${AWS_ACCOUNT_ID}’ AWS_DEFAULT_REGION: ‘us-east-1’ ECS_SERVICE_NAME: ‘sample-app’ ECR_REPOSITORY_URI: ‘${AWS_REGISTRY_URL}’ ECS_CLUSTER_NAME: ‘default’ VPC_SUBNETS: ‘’subnet-12345677’, ‘subnet-12345678’’ AWS_SECURITY_GROUPS: ‘sg-012b1ade1234578c’ AWS_ELB_TARGET_GROUP_ARN: ‘${AWS_ELB_TARGET_GROUP_ARN}’ ECS_CONTAINER_PORT: ‘80’ ECS_CONTAINER_NAME: ‘sample-app’ DESIRED_COUNT: ‘1’ DEBUG: ‘true’
- 21. - step: name: deploy services to stg script: -pipe: aws-labs/aws-fargate-deploy:0.2.0 variables: AWS_ACCESS_KEY_ID: ‘${AWS_ACCESS_KEY_ID}’ AWS_SECRET_ACCESS_KEY: ‘${AWS_SECRET_ACCESS_KEY}’ AWS_ACCOUNT_ID: ‘${AWS_ACCOUNT_ID}’ AWS_DEFAULT_REGION: ‘us-east-1’ ECS_SERVICE_NAME: ‘sample-app’ ECR_REPOSITORY_URI: ‘${AWS_REGISTRY_URL}’ ECS_CLUSTER_NAME: ‘default’ VPC_SUBNETS: ‘’subnet-12345677’, ‘subnet-12345678’’ AWS_SECURITY_GROUPS: ‘sg-012b1ade1234578c’ AWS_ELB_TARGET_GROUP_ARN: ‘${AWS_ELB_TARGET_GROUP_ARN} ECS_CONTAINER_PORT: ‘80’ ECS_CONTAINER_NAME: ‘sample-app’ DESIRED_COUNT: ‘1’ DEBUG: ‘true’ CURRENT PIPE - step: name: deploy services to stg image: atlassian/pipelines-awscli:latest deployment: test script: - export ECS_TASK_NAME="${BITBUCKET_REPO_SLUG}" # register the ECS task definition and capture the version - export TASK_VERSION=$(aws ecs register-task-definition --family "${ECS_TASK_NAME}" --networkMode "awsvpc” --requires-compatibilities “fargate” --container-definitions ‘[{ "name":"app", "image":"'"${IMAGE_NAME}”’”, "memory":1024, }]’ | jq --raw-output '.taskDefinition.revision’) - echo "Registered ECS Task Definition: " $TASK_VERSION # ECS variables - export ECS_CLUSTER_NAME="${BITBUCKET_REPO_OWNER}" - export ECS_SERVICE_NAME="${BITBUCKET_REPO_SLUG}" …
- 22. Use Best Practices Pipes enable the community to drive a higher bar for testing and deployment through collective best practices.
- 23. Jira Integration As this pipe runs from within Bitbucket Pipelines, support for tracking issues and releases in Jira works as you’d expect.
- 24. Agenda Wrap Up
- 25. What we learned Customer First Transparency Cross-team collaboration Value of Jira Powerful integrations
- 26. Call to Action!
- 27. We are here or YOU! Take the free workshop Attend our Theater Talks Chat with us https://atlassian.awsworkshop.io We invite you to attend our two theater talks. Feel free to stop by our lounge and come talk/connect with us. We want to meet you!
- 28. Agenda Q&A
- 30. Thank you! CURTIS RISSI | SENIOR SOLUTIONS ARCHITECT | AMAZON WEB SERVICES JAY YERAS | SPECIALIST SOLUTIONS ARCHITECT | AMAZON WEB SERVICS