What should the developer do to make the new methods available?

By:
On:
In: DVA-C01
Tagged:
With: 0 Comments
A company has a web application that contains an Amazon API Gateway REST API.A developer has created an AWS CloudFormation template for the initial deployment of the application.The developer has deployed the application successfully as part of an AWS CodePipeline continuous integration and continuous delivery (CI/CD) process.All resources and methods are available through the deployed stage endpoint.The CloudFormation template contains the following resource types:• AWS::ApiGateway::RestApi• AWS::ApiGateway::Resource• AWS::ApiGateway::Method• AWS::ApiGateway::Stage• AWS::ApiGateway::DeploymentThe developer adds a new resource to the REST API with additional methods and redeploys the template.CloudFormation reports that the deployment is successful and that the stack is in the UPDATE_COMPLETE state.However, calls to all new methods are returning 404 (Not Found) errors.

What should the developer do to make the new methods available?

Specify the disable-rollback option during the update-stack operation.

Unset the CloudFormation stack failure options.

Add an AWS CodeBuild stage to CodePipeline to run the aws apigateway create-deployment AWS CLI command.

Add an action to CodePipeline to run the aws cloudfront create-invalidation AWS CLI command.

Explanations:

The disable-rollback option is used to prevent CloudFormation from rolling back the stack when an error occurs during the stack update. It does not address the issue of missing methods in the API Gateway after deployment.

Unsetting the stack failure options is not relevant to the issue at hand. The problem is related to the deployment of new resources and methods, not stack failures.

When using CloudFormation to deploy API Gateway, the deployment does not automatically trigger a new deployment of the API if new resources and methods are added. The aws apigateway create-deployment command ensures a new deployment is created for the updated API, making the new methods available.

The aws cloudfront create-invalidation command is used to invalidate cached CloudFront content, not related to API Gateway deployment or method availability. It does not solve the issue of new methods not being available in the API.

Leave a Reply

Your email address will not be published. Required fields are marked *

two × 5 =